Navigate the CLI command families

Understand the approach

The shell command codex can launch several workflows. Some commands inspect the local setup, some start work and others change saved state. Begin with help at the relevant level: codex --help for the command family and codex exec --help for a scripted run. A command that authenticates, installs a plugin or deletes a session is not equivalent to a read-only inventory command.

Useful inspection controls include codex --version and codex login status. The latter reports whether credentials are present; that does not prove access to every model, workspace or connected record. codex resume opens saved interactive sessions, while codex fork creates a new chat from a saved session. Confirm the working directory when resuming, especially if the current terminal folder differs from the session’s saved project.

For a repository review, codex review --uncommitted selects uncommitted changes as the target. Review findings still need evaluation and relevant tests. Inside the TUI, slash controls such as /status and /diff operate the live session; they are not external shell executables. Keeping a small notebook of command, location and effect prevents accidental execution of a state-changing operation while you were only trying to inspect something.

A saved session is not a restored repository

The linked matrix includes shell syntax and separate composer syntax. codex resume selects conversation history; codex fork creates a conversation branch. Inspect the working folder before accepting either selection. In the practice project, starting a new chat leaves a changed README heading unchanged.

A review examines the chosen diff and returns findings; it does not imply fixes were applied. For scripted continuation, codex exec resume --last chooses recent history associated with the directory. Deliberately select a harmless practice session and check installed help rather than relying on an unknown last task.

Read-only diagnostics can still contain sensitive details

A diagnostic report may reveal local paths, account context or configuration even when it does not edit anything. Inspect such output before sharing it and never paste authentication files into a support request. This lesson does not require logout, deletion, plugin installation or remote-control setup. Use the smallest command family that answers the current question and preserve the result with its project and client context.

Try it step by step

1. Classify each matrix entry as shell or composer and describe its observable effect.
2. Inspect installed command help and version if a CLI already exists; do not install one for the exercise.
3. Resume only an identified harmless practice session and verify its actual directory, or mark that observation unrun.
4. Compare review findings with the chosen diff; neither session navigation nor review is file restoration.

A useful starting example

Illustration · adapt before use.

codex --version
codex login status
codex resume --help
codex fork --help
codex review --help

Check your result

• The notebook distinguishes shell commands from interactive slash commands with correct examples.
• Credential status is described as a local authentication check, not a claim of unrestricted product or record access.
• A review result is reconciled with the selected diff and does not imply that fixes were applied automatically.

Common mistakes

• Typing a terminal command into the composer and interpreting the model’s explanation as actual command execution.
• Resuming the most recent session without checking whether it belongs to the current project.