Discord
Chat room
Where readers ask about the guides, and where new features get discussed first.
- Ask about anything in the 400+ guides
- Other readers can see the answer too
- Corrections to a guide go to GitHub, as issues
Both are free, and neither needs a subscription. Ask about a guide in the Discord. When a guide is wrong, open an issue in the public GitHub repository. When the author confirms it, the guide is corrected and its date changes.
Opening an issue needs a GitHub account.
Discord answers questions. GitHub records corrections.
Chat room
Where readers ask about the guides, and where new features get discussed first.
Public repository
The public companion repository, where corrections to a guide are filed as issues.
A billing, access or download problem belongs in neither place. Write to support@developertoolkit.ai, or see all three addresses.
The Improve this page button fills in the title. Five lines in the body give the author what is needed to re-check a claim against the same two primary sources the guide was written from.
Title, filled in by the button
/en/codex/<guide>/
Why each field is there
Why we askThe address is already in the title. The date tells the author which version of the page you read.
codex --approval-mode never to skip approval prompts.” Why we askThe exact words can be searched for. A paraphrase cannot.
Why we askA flag can exist in one release and be gone in the next, so the tool and its version come with the report.
--ask-for-approval (-a), with the values on-request and never. Why we askSay what you believe is right. If you are not sure, say that too.
codex --help on the same version, pasted below this line. Why we askA pasted line or a link to the vendor’s docs lets the author re-check against the same source.
You can see the result on the page itself.
Step 1
From the Improve this page button beside any guide, on a wide screen. The page’s address is already in the title.
Step 2
Against the two primary sources the guides are written from: the installed tool’s --help and the vendor’s live docs.
Step 3
The correction goes into the guide. A claim that something does not exist names the version it was checked on.
Step 4
The page shows a new last-updated date, so you can see your report landed.
Last updated <date you read>
Last updated <day of the fix>
Something else? Write to hello@developertoolkit.ai.
No. The Discord and the GitHub repository are both open without one. The Ladder and Start here sections are free. The other guides, the Setup Pack and the seven books are part of the plans, and every plan starts with a 7-day free trial.
Ask in the Discord first. If it turns out to be a bug in a guide or a missing page, open a GitHub issue. File corrections there, as issues.
A command, flag, setting or model name that does not work on the version you run. A number with no publisher or date. A broken link or a missing page.
Yes. Put the corrected line in the issue, with the --help output or docs link that proves it.
To the Discord. It is where new features get discussed first and where requests are collected.
Write to support@developertoolkit.ai. The Contact page lists what to include.
Free · 25 questions · ~8 minutes
Your place on the ladder (Levels 1–4) and the one move that takes you to the next rung.
The 400+ guides, the Setup Pack and all seven books open with the 7-day trial, and the Discord is where you ask about them.
Then $19.99 a month or $99.99 a year. Cancel from your account page. 30-day refund on a first purchase.