How to read a detail guide

Key takeaways

• Syntax notation explains the interface; concrete examples show actual input.
• Do not infer cross-session persistence when a setting does not document its scope.

From prerequisites to checking the result

1. Purpose explains the task and exact syntax.
2. Availability gives the input surface, status, aliases, and documented minimum.
3. Examples use concrete values. Replace paths and task names; separate lines are separate invocations.
4. Effects and persistence identifies display, session, file, settings, or cloud effects.
5. Cautions explains command-specific exceptions.
6. Official sources links the evidence and earlier change records.

Commands inside the complete list

Only the 15 commands with the most material have pages of their own. The rest are collected under Command guides in the complete command list. Each entry gives the summary, syntax, kind and status, examples, and effects, followed where useful by when to use it, related commands, and cautions. Select "Guide" in the list tables to jump straight to a command.

When a command is missing

Check the installed version, account, platform, model, and feature settings. Type / to inspect the Codex command menu; /help is not an official CLI slash command. Also check whether the instruction belongs in the operating-system shell or inside the running session.

Korean and English editions

Both editions share command syntax, status, sources, and detail-page order. Extended operational explanations may differ in length. Historical records preserve the content of the edition at the time.