Codex CLI Commands and Session Management Reference

Codex CLI is updated quickly, and articles cannot replace the help text of the current binary. First confirm the subcommand with top-level help, then run --help on the specific subcommand.

Strict configuration mode is suitable for discovering invalid or misspelled configuration fields, but you should first verify the impact of the upgrade in a non-production workspace.

Running codex without a subcommand opens the interactive interface. -C sets the working root, -m selects a model temporarily and -i attaches images; these flags apply only to the current invocation.

Additional writable directories must be provided explicitly via --add-dir; do not expand the entire sandbox just to access an adjacent directory.

resume continues an existing session with its context, while fork starts a new branch of work from a historical session. Both support --last for the most recent session; run the selector without arguments when you need to inspect the available choices.

You still need to check the current repository and branches before restoring. The historical context will not guarantee that the working tree is exactly the same as last time.

-c accepts TOML values and can override top-level or nested config.toml fields. Use a one-time override to test an assumption before deciding whether to make the setting persistent.

Sandbox and approval have dedicated -s and -a flags. Prefer those to the generic -c form because they make command intent clearer.

codex exec handles non-interactive calls and reads tasks from an argument or standard input. codex review focuses on repository changes and can inspect uncommitted work, changes relative to a baseline branch or a specific commit.

When automating, you must check the exit code and save the JSONL event separately from the final text; do not judge the task status by searching for natural language "success".

completion generates completion scripts based on the shell; the specific loading method is determined by the shell. update is used to upgrade installations that support self-update. If hosted by a package manager, the same upgrade channel should be maintained.

doctor checks installation, configuration, authentication and the runtime environment. Review its output before sharing it, and remove private paths or organization details from public tickets.