Developer commands

ChatGPT web has its own composer command menu. Type / to see the actions available in the current chat. It doesn't expose the ChatGPT desktop app or CLI command set; the Codex slash commands, CLI commands, and flags in this reference don't apply to ChatGPT web.

ChatGPT desktop app commands

The general Commands page covers app navigation, chat shortcuts, keyboard customization, and deep links for chats, settings, skills, scheduled tasks, plugins, and pets.

The Slash commands page covers the commands available from the app composer, including /feedback, /goal, /init, /mcp, /plan, /review, and /status.

How to read this reference

This page catalogs every documented Codex CLI command and flag. Use the interactive tables to search by key or description. Each section indicates whether the option is stable or experimental and calls out risky combinations.

Global flags

These options apply to the base codex command. Most propagate to commands; see the notes above or the relevant command help for exceptions. For propagated flags, follow the relevant command help. For example, codex exec --oss ... applies --oss to exec.

Command overview

Command details

codex (interactive)

Running codex with no subcommand launches the interactive terminal UI (TUI). The agent accepts the global flags above plus image attachments. Web search defaults to cached mode; use --search to switch to live browsing. For low-friction local work, use --sandbox workspace-write --ask-for-approval on-request.

Use --remote ws://host:port or --remote wss://host:port to connect the TUI to an app server started with codex app-server --listen ws://IP:PORT. For a local Unix socket, use --remote unix:// for the default socket or --remote unix://PATH for an explicit path. Add --remote-auth-token-env <ENV_VAR> when the server requires a bearer token for WebSocket authentication.

codex agents

Open the command center to browse chats and switch between agents on a shared server. Use --remote <URL> to connect to a remote server and --cd <DIR> to set the directory for new remote tasks. codex agents doesn't support --no-daemon.

codex queue

Queue a text message for an existing session:

codex queue --thread <SESSION_ID> --message "Run the remaining checks"

--thread accepts a UUID or exact session name. Use a UUID when sessions share the same name. The command also accepts --remote and --remote-auth-token-env; image attachments aren't supported.

codex app-server

Launch the Codex app server locally. This is primarily for development and debugging and may change without notice.

codex app-server --listen stdio:// keeps the default JSONL-over-stdio behavior, and codex app-server --stdio is an alias for that transport. --listen ws://IP:PORT enables WebSocket transport for app-server clients. The server accepts ws:// listen URLs; use TLS termination or a secure proxy when clients connect with wss://. Use --listen unix:// to accept WebSocket handshakes on Codex's default Unix socket, or --listen unix:///absolute/path.sock to choose a socket path. If you generate schemas for client bindings, add --experimental to include gated fields and methods.

Add --code-mode-host wss://code-mode.example.com/host to connect app-server to a remote Code Mode host instead of starting a local host. This outbound connection is separate from --listen and shared by every thread in the app-server process. Use ws:// only for a localhost or SSH-forwarded host.

codex remote-control

Run codex remote-control to start remote control through the managed background server when eligible, with a foreground fallback. Use codex remote-control --no-daemon to run in the foreground explicitly. Use codex remote-control start to start the local app-server daemon with remote control enabled, and codex remote-control stop to stop it. Managed remote-control clients and SSH remote workflows use these commands; they aren't a replacement for codex app-server --listen when you're building a local protocol client.

After the daemon is running, use codex remote-control pair to create and print a short-lived manual pairing code. Add --json to any remote-control command for machine-readable output. For pair, the JSON response includes pairingCode, manualPairingCode, environmentId, and expiresAt. --no-daemon applies only to the bare remote-control command; don't combine it with start, stop, or pair.

codex app

Launch the ChatGPT desktop app from the terminal on macOS or Windows. On macOS, Codex can open a specific workspace path; on Windows, Codex prints the path to open.

codex app opens an installed ChatGPT desktop app, or starts the installer when the app is missing. On macOS, Codex opens the provided workspace path; on Windows, it prints the path to open after installation.

codex debug app-server send-message-v2

Send one message through app-server's V2 thread/turn flow using the built-in app-server test client.

This debug flow initializes with experimentalApi: true, starts a thread, sends a turn, and streams server notifications. Use it to reproduce and inspect app-server protocol behavior locally.

codex debug models

Print the raw model catalog Codex sees as JSON.

Use --bundled when you want to inspect only the catalog bundled with the current binary, without refreshing from the remote models endpoint.

codex debug prompt-input

Render the exact model-visible prompt input list as JSON. Use this when debugging instruction discovery, session context, or prompt construction.

codex apply

Apply the most recent diff from a Codex cloud chat to your local repository. You must authenticate and have access to the chat.

Codex prints the patched files and exits non-zero if git apply fails (for example, due to conflicts).

codex review

Run a code review non-interactively. Choose exactly one review target, or pass custom review instructions as a prompt.

--uncommitted, --base, --commit, and a custom PROMPT conflict with one another. Use --title only with --commit.

codex archive and codex unarchive

Archive or restore a saved interactive session by session ID or session name. Use these commands when you want to clean up the session picker without deleting the transcript. Session IDs take precedence over session names.

codex archive <SESSION>
codex unarchive <SESSION>

codex delete

Permanently delete a saved interactive session by session ID or session name. Use this only when you want to remove the transcript instead of hiding it from active session lists.

codex delete <SESSION>
codex delete <SESSION_UUID> --force

Use --force only with a session UUID. Named sessions still require confirmation so Codex doesn't delete a repeated or ambiguous name without a prompt.

codex cloud

Interact with Codex cloud chats from the terminal. The default command opens an interactive picker; codex cloud exec submits a task directly, and codex cloud list returns recent chats for scripting or quick inspection.

Authentication follows the same credentials as the main CLI. Codex exits non-zero if the task submission fails.

codex cloud list

List recent cloud chats with optional filtering and pagination.

Plain-text output prints a task URL followed by status details. Use --json for automation. The JSON payload contains a tasks array plus an optional cursor value. Each task includes id, url, title, status, updated_at, environment_id, environment_label, summary, is_review, and attempt_total.

codex completion

Generate shell completion scripts and redirect the output to the appropriate location, for example codex completion zsh > "${fpath[1]}/_codex".

codex doctor

Generate a local diagnostic report before filing a support issue or while investigating a broken Codex installation. The report checks installation, configuration, authentication, runtime, Git, terminal, app-server, and thread inventory health.

codex features

Manage feature flags stored in $CODEX_HOME/config.toml. The enable and disable commands persist changes so they apply to future sessions. The features subcommand doesn't accept --profile.

codex exec

Use codex exec (or the short form codex e) for scripted or CI-style runs that should finish without human interaction.

Codex writes formatted output by default. Add --json to receive newline-delimited JSON events (one per state change). The optional resume subcommand lets you continue non-interactive tasks. Use --last to pick the most recent session from the current working directory, or add --all to search across all sessions:

Use codex exec fork <SESSION_ID> [PROMPT] to copy a saved session into a new session. The session argument accepts a UUID or name. With no prompt, Codex creates the fork without starting a turn. Pass - as the prompt to read it from stdin, or add --image to attach images.

A prompt is required when using images, --output-schema, --output-last-message, or --ephemeral.

Add --worktree to a new or forked run to create a managed Git worktree:

codex exec --worktree "implement the next step"
codex exec fork <SESSION_ID> --worktree "try an alternative approach"

--worktree requires local execution. Don't combine it with resume, review, --ephemeral, or --ignore-user-config.

codex execpolicy

Check execpolicy rule files before you save them. codex execpolicy check accepts one or more --rules flags (for example, files under ~/.codex/rules) and emits JSON showing the strictest decision and any matching rules. Add --pretty to format the output. The execpolicy command is currently in preview.

codex login

Authenticate the CLI with a ChatGPT account, API key, or access token. With no flags, Codex opens a browser for the ChatGPT OAuth flow.

codex login status exits with 0 when credentials are present, which is helpful in automation scripts.

codex logout

Remove saved credentials for both API key and ChatGPT authentication. This command has no flags.

codex mcp

Manage Model Context Protocol server entries stored in ~/.codex/config.toml.

The add subcommand supports both stdio and streamable HTTP transports:

OAuth actions (login, logout) only work with streamable HTTP servers (and only when the server supports OAuth).

codex plugin

Install, list, and remove plugins from configured marketplaces.

codex plugin add --json prints pluginId, name, marketplaceName, version, installedPath, and authPolicy. codex plugin list --json prints installed and available arrays. Entries include pluginId, name, marketplaceName, version, installed, enabled, source, installPolicy, authPolicy, and, when available, marketplaceSource with the configured marketplace source type and value. codex plugin remove --json prints pluginId, name, and marketplaceName.

codex plugin marketplace

Manage plugin marketplace sources that Codex can browse and install from.

codex plugin marketplace add accepts GitHub shorthand such as owner/repo or owner/repo@ref, HTTP or HTTPS Git URLs, SSH Git URLs, and local marketplace root directories. Use --ref to pin a Git ref, and repeat --sparse PATH to use a sparse checkout for Git-backed marketplace repositories.

codex plugin marketplace list prints in-scope marketplace names and roots, including implicitly discovered default marketplaces and configured marketplace snapshots.

Add --json to marketplace add, list, upgrade, or remove commands for automation-friendly output. Marketplace add JSON includes marketplaceName, installedRoot, and alreadyAdded; list JSON includes a marketplaces array with name, root, and optional marketplaceSource; upgrade JSON includes selectedMarketplaces, upgradedRoots, and errors; remove JSON includes marketplaceName and installedRoot.

codex mcp-server

codex resume

Continue an interactive session by ID or resume the most recent chat. codex resume scopes --last to the current working directory unless you pass --all. It accepts model and sandbox overrides, but not --worktree.

If the current working directory differs from the session's saved directory, Codex asks which directory to use. Set tui.resume_cwd to "current" or "session" to reuse that choice without a prompt. An explicit --cd (-C) override takes precedence over tui.resume_cwd.

codex fork

Fork a previous interactive session into a new chat. By default, codex fork opens the session picker; add --last to fork your most recent session instead.

When the current and saved session directories differ, codex fork uses the same working-directory prompt and tui.resume_cwd setting as codex resume.

To fork into a managed Git worktree, run codex fork <SESSION_ID> --worktree. This requires an explicit session ID and local execution; it doesn't support --last or the session picker.

codex sandbox

Use the sandbox helper to run a command under the same policies Codex uses internally.

macOS seatbelt

Linux sandbox

Windows

codex update

Check for and apply a Codex CLI update when the installed release supports self-update. Debug builds print a message telling you to install a release build instead.

Flag combinations and safety tips

• Use --sandbox workspace-write for unattended local work that can stay inside the workspace, and avoid --dangerously-bypass-approvals-and-sandbox unless you are inside a dedicated sandbox VM.
• When you need to grant Codex write access to more directories, prefer --add-dir rather than forcing --sandbox danger-full-access.
• Pair --json with --output-last-message in CI to capture machine-readable progress and a final natural-language summary.

Interactive shortcuts

• Type @ to search for a file in the workspace and add its path to the prompt.
• Press Up or Down to restore draft history.
• Press Ctrl+R to search prompt history, then press Enter to use a match or Escape to cancel.
• Press Ctrl+O or run /copy to copy the latest completed Codex output.
• Prefix a line with ! to run a local shell command under the current approval and sandbox settings.
• Press Tab while Codex is working to queue a follow-up prompt, slash command, or shell command for the next turn.
• Press Enter while Codex is working to inject new instructions into the current turn.
• Press Escape twice with an empty composer to edit the previous user message and fork the chat from that point.
• Press Ctrl+C or run /exit to close the session.

Related resources

• Codex CLI overview: installation, upgrades, and quick tips.
• Config basics: persist defaults like the model and provider.
• Advanced Config: profiles, providers, sandbox tuning, and integrations.
• AGENTS.md: conceptual overview of Codex agent capabilities and best practices.

Slash commands give you fast, keyboard-first control over Codex. Type / in the composer to open the slash popup, choose a command, and Codex will perform actions such as switching models, adjusting permissions, or summarizing long chats without leaving the terminal.

This guide shows you how to:

• Find the right built-in slash command for a task
• Steer an active session with commands like /model, /fast, /permissions, /approve, /raw, /agents, /subagents, and /status

Built-in slash commands

Codex ships with the following commands. Open the slash popup and start typing the command name to filter the list.

When a chat is already running, you can type a slash command and press Tab to queue it for the next turn. Codex parses queued slash commands when they run, so command menus and errors appear after the current turn finishes. Slash completion still works before you queue the command.

/quit and /exit both exit the CLI. Use them only after you have saved or committed any important work.

Use /permissions to adjust what Codex can do without asking first. Use /approve only when you need to retry a recent action that automatic review denied.

Control your session with slash commands

The following workflows keep your session on track without restarting Codex.

Choose the terminal mode with /tui

1. Type /tui.
2. Choose scrollback or fullscreen mode, then confirm.
3. Restart Codex to apply the selection.

Expected: The next launch uses the saved terminal mode. Launch overrides such as --no-alt-screen still apply.

Export a conversation with /export

1. Type /export.
2. Choose Copy to clipboard or Save to file.

Expected: Codex exports the complete conversation as Markdown. To save directly to a file, run /export session.md. Wait for the current turn to finish before exporting.

Summarize the chat with /recap

1. When Codex is idle, type /recap.

Expected: Codex generates a summary of the conversation, even if tui.auto_recap = false. Use /compact when you want to free context space.

Change directories with /cd

1. Type /pwd (or /cwd) to check the current directory.
2. Type /cd <path> to change directories, or /cd to use your home directory.

Expected: Codex continues the chat in the selected directory. Changing directories requires an idle primary session with no queued input or background terminals.

Continue in a worktree with /worktree

1. Type /worktree in a local Git repository.
2. Choose whether to start a new chat or continue the current conversation in a new worktree.

Expected: Codex creates a managed Git worktree and starts the selected chat there. Choose Browse worktrees to find existing worktrees and their owner chats. This command requires local worktree support and is unavailable while a task is running.

Manage the background server with /daemon

1. Type /daemon.
2. Review the server connection and available actions.

Expected: Codex offers to install the latest public stable release or use the current CLI build for the local background server. Confirming an update exits Codex and may interrupt active work. For a remote connection, manage the server on its host.

Inspect warnings with /warnings

1. Type /warnings.

Expected: Codex shows retained warnings and their diagnostic details.

Set the active model with /model

The picker only shows models available to your account and workspace. If GPT-6.1 Sol isn't listed, choose another model. See GPT-6.1 Sol availability by plan.

1. Start Codex and open the composer.
2. Type /model and press Enter.
3. Choose a model such as gpt-6-luna or gpt-6.1-sol from the popup.

Expected: Codex confirms the new model in the transcript. Run /status to verify the change.

Toggle Fast mode with /fast

1. Type /fast to turn the current model's Fast service tier on.
2. Type /fast again to turn it off.

Expected: Codex toggles the tier and saves the selection. In the TUI footer, you can also show a Fast mode status-line item with /statusline.

Fast tier commands are catalog-driven. If the current model doesn't advertise a Fast tier, Codex won't show /fast.

Switch to plan mode with /plan

1. Type /plan and press Enter to switch the active chat into plan mode.
2. Optional: provide inline prompt text (for example, /plan Propose a migration plan for this service).
3. You can paste content or attach images while using inline /plan arguments.

Expected: Codex enters plan mode and uses your optional inline prompt as the first planning request.

While Codex is already working, /plan is temporarily unavailable.

Set or view a task goal with /goal

1. Type /goal <objective> to set the goal, for example /goal Finish the migration and keep tests green.
2. Type /goal to view the current goal.
3. Use /goal edit to revise the objective. Use /goal pause, /goal resume, or /goal clear to pause, resume, or remove it.

Expected: Codex keeps the goal attached to the active chat while work continues.

Goal objectives must be non-empty and at most 4,000 characters. For longer instructions, put the details in a file and point the goal at that file.

Toggle experimental features with /experimental

1. Type /experimental and press Enter.
2. Toggle the features you want (for example, Network proxy or Prevent sleep while running), then restart Codex if the prompt asks you to.

Expected: Codex saves your feature choices to config and applies them on restart.

Approve an auto review denial with /approve

Use /approve when the automatic reviewer denied a recent action and you want Codex to retry it once.

1. Type /approve.
2. Confirm the retry when Codex shows the relevant denied action.

Expected: Codex retries that denied action once under the current session policy.

Configure memories with /memories

1. Type /memories.
2. Choose whether Codex should use existing memories, generate new memories, or keep memory behavior disabled.

Expected: Codex updates the relevant memory settings for future sessions.

Use skills with /skills

1. Type /skills.
2. Pick the skill you want Codex to apply.

Expected: Codex inserts the selected skill context so the next request follows that skill's instructions.

Import Claude Code or Cursor setup with /import

1. Type /import.
2. Choose Claude Code or Cursor.
3. Select the setup, project files, or recent chats you want to migrate.

Expected: Codex opens the external-agent import picker and imports the selected supported artifacts into Codex configuration and local files. Session discovery includes up to 50 chats from the last 30 days.

Run /import from a local TUI session. It's unavailable while a task is running, in remote sessions, and while connected to the local app-server daemon.

For the desktop app workflow and supported artifact types, see Import from another agent.

Clear the terminal and start a new chat with /clear

1. Type /clear and press Enter.

Expected: Codex clears the terminal, resets the visible transcript, and starts a fresh chat in the same CLI session.

To name the new chat as you create it, run /clear release prep.

Unlike Ctrl+L, /clear starts a new chat.

Ctrl+L only clears the terminal view and keeps the current chat. Codex disables both actions while a task is in progress.

Archive the current session with /archive

1. Type /archive and press Enter.
2. Confirm that you want to archive the current session.

Expected: Codex archives the session and returns to the command center when connected to a local background server or remote server. Without a shared server, Codex exits. Codex keeps the transcript; restore it later with codex unarchive <SESSION>.

If a turn is running, confirming /archive stops that turn before archiving.

Delete the current session with /delete

1. Type /delete and press Enter.
2. Confirm that you want to delete the current session.

Expected: Codex permanently deletes the transcript and spawned descendant sessions. When connected to a local background server or remote server, Codex returns to the command center. Without a shared server, Codex exits.

/delete is unavailable while a chat is running or in a side chat.

Update permissions with /permissions

1. Type /permissions and press Enter.
2. Select the approval preset that matches your comfort level, for example Auto for hands-off runs or Read Only to review edits. When named permission profiles are active, the picker also shows configured custom profiles and their descriptions.

Expected: Codex announces the updated policy. Future actions respect the updated approval mode until you change it again.

Include IDE context with /ide

1. Type /ide.
2. Add optional inline text if you want to explain what Codex should do with the current IDE selection or open files.

Expected: Codex includes available IDE context in the next prompt.

Toggle Vim mode with /vim

1. Type /vim.
2. Continue editing in the composer.

Expected: Codex toggles composer Vim mode for the current session. To make Vim mode the default for new sessions, set tui.vim_mode_default = true in config.toml.

Set up the elevated Windows sandbox with /setup-default-sandbox

This command appears only on Windows when Codex is using the degraded restricted-token sandbox.

1. Type /setup-default-sandbox.
2. Follow the administrator setup flow.

Expected: Codex configures the elevated Windows sandbox and selects the corresponding automatic approval preset.

Copy the latest response with /copy

1. Type /copy and press Enter.

Expected: Codex copies the latest completed Codex output to your clipboard.

If a turn is still running, /copy uses the latest completed output instead of the in-progress response. The command is unavailable before the first completed Codex output and immediately after a rollback.

You can also press Ctrl+O from the main TUI to copy the latest completed response without opening the slash command menu.

Toggle raw scrollback with /raw

1. Type /raw, /raw on, or /raw off.

Expected: Codex toggles raw scrollback mode, which makes terminal selection and copying more direct. You can also use the default Alt+R binding or persist the default with tui.raw_output_mode = true.

Inspect the session with /status

1. In any chat, type /status.
2. Review the output for the active model, approval policy, writable roots, and current token usage. When the TUI connects remotely, the output also shows the remote address and the server version.

Expected: Codex prints a summary confirming that it's operating where you expect.

View account usage with /usage

1. Type /usage to open the usage menu.
2. Choose whether to show token activity or redeem an available earned reset.
3. To open token activity directly, type /usage daily, /usage weekly, or /usage cumulative.

Expected: Codex opens usage actions or shows account token activity for the selected view. If the session doesn't have Codex service account auth, Codex shows a sign-in requirement.

Inspect config layers with /debug-config

1. Type /debug-config.
2. Review the output for config layer order (lowest precedence first), on/off state, and policy sources.

Expected: Codex prints layer diagnostics plus policy details such as allowed_approval_policies, allowed_sandbox_modes, mcp_servers, rules, and experimental_network when configured.

Use this output to debug why an effective setting differs from config.toml.

Configure footer items with /statusline

1. Type /statusline.
2. Use the picker to toggle and reorder items, then confirm.

Expected: The footer status line updates immediately and persists to tui.status_line in config.toml.

Available status-line items include model, model+reasoning, context stats, rate limits, git branch, token counters, session id, current directory/project root, and Codex version.

Configure terminal title items with /title

1. Type /title.
2. Use the picker to toggle and reorder items, then confirm.

Expected: The terminal window or tab title updates immediately and persists to tui.terminal_title in config.toml.

Available title items include app name, project, spinner, status, thread, git branch, model, and task progress.

Choose a syntax theme with /theme

1. Type /theme.
2. Preview a theme from the picker, then confirm.

Expected: Codex updates syntax highlighting and persists the choice to tui.theme in config.toml.

Choose a terminal pet with /pets

1. Type /pets (or /pet) to open the pet picker.
2. Choose a built-in or custom pet, or turn pets off.

Expected: Codex displays the selected ambient pet in supported terminals and persists the selection. You can also type /pets off to hide it.

Remap TUI shortcuts with /keymap

Use /keymap to inspect, update, and persist keyboard shortcut bindings for the TUI.

1. Type /keymap.
2. Pick the shortcut context and action you want to change.
3. Enter the new binding or remove the existing one.

Expected: Codex updates the active keymap and writes the custom binding to tui.keymap in config.toml.

Key bindings use names such as ctrl-a, shift-enter, and page-down. Context-specific bindings override tui.keymap.global; an empty binding list unbinds the action.

Check background terminals with /ps

1. Type /ps.
2. Review the list of background terminals and their status.

Expected: Codex shows each background terminal's command plus up to three recent, non-empty output lines so you can gauge progress at a glance.

Background terminals appear when unified_exec is in use; otherwise, the list may be empty.

Stop background terminals with /stop

1. Type /stop.
2. Confirm if Codex asks before stopping the listed terminals.

Expected: Codex stops all background terminals for the current session. /clean is still available as an alias for /stop.

Keep transcripts lean with /compact

1. After a long exchange, type /compact.
2. Confirm when Codex offers to summarize the chat so far.

Expected: Codex replaces earlier turns with a concise summary, freeing context while keeping critical details.

Review changes with /diff

1. Type /diff to inspect the Git diff.
2. Scroll through the output inside the CLI to review edits and added files.

Expected: Codex shows changes you've staged, changes you haven't staged yet, and files Git hasn't started tracking, so you can decide what to keep.

Highlight files with /mention

1. Type /mention followed by a path, for example /mention src/lib/api.ts.
2. Select the matching result from the popup.

Expected: Codex adds the file to the chat, ensuring follow-up turns reference it directly.

Start a new chat with /new

1. Type /new and press Enter.
2. If Codex offers a checkout choice, choose the current directory or a new worktree.

Expected: Codex starts a fresh chat in the same CLI session, so you can switch chats without leaving your terminal.

To name the new chat as you create it, run /new bug bash.

Unlike /clear, /new doesn't clear the current terminal view first.

Rename the current chat with /rename

1. Type /rename <name>, or type /rename to open the naming prompt.
2. Enter a short name that will help you find the chat later.

Expected: Codex updates the saved chat name without changing its transcript.

Resume a saved chat with /resume

1. Type /resume and press Enter.
2. Choose the session you want from the saved-session picker.

Expected: Codex reloads the selected chat's transcript so you can pick up where you left off, keeping the original history intact.

Fork the current chat with /fork

1. Type /fork and press Enter.
2. If Codex offers a checkout choice, choose the current directory or a new worktree.

Expected: Codex clones the current chat into a new chat with a fresh ID, leaving the original transcript untouched so you can explore an alternative approach in parallel.

If you need to fork a saved session instead of the current one, run codex fork in your terminal to open the session picker.

Continue in the desktop app with /app

On macOS and Windows, type /app to open the current session in the ChatGPT desktop app. If the app isn't installed or running, Codex shows an error asking you to install or launch it.

Expected: The desktop app opens the same saved chat so you can continue there.

Start a side chat with /side

Use /side to start an ephemeral fork from the current chat without switching away from the main chat.

1. Type /side to open a side chat.
2. Optionally add inline text, for example /side Check whether this plan has an obvious risk.
3. Return to the parent chat after the focused detour finishes.

Expected: Codex opens a side chat whose transcript is separate from the parent chat. While you are in side mode, the TUI continues to show the parent chat's status so you can see whether the main chat is still running.

/side is unavailable inside another side chat and during review mode.

Generate AGENTS.md with /init

1. Run /init in the directory where you want Codex to look for persistent instructions.
2. Review the generated AGENTS.md, then edit it to match your repository conventions.

Expected: Codex creates an AGENTS.md scaffold you can refine and commit for future sessions.

Ask for a working tree review with /review

1. Type /review.
2. Follow up with /diff if you want to inspect the exact file changes.

Expected: Codex summarizes issues it finds in your working tree, focusing on behavior changes and missing tests. It uses the current session model unless you set review_model in config.toml.

List MCP tools with /mcp

1. Type /mcp.
2. Review the list to confirm which MCP servers and tools are available.

Expected: You see the configured Model Context Protocol (MCP) tools Codex can call in this session.

Use /mcp verbose to include detailed server diagnostics. Use /mcp login <name> to sign in to a configured MCP server from the active session.

Browse apps with /apps

1. Type /apps.
2. Pick an app from the list.

Expected: Codex inserts the app mention into the composer as $app-slug, so you can immediately ask Codex to use it.

Browse plugins with /plugins

1. Type /plugins.
2. Choose a marketplace tab, then pick a plugin to inspect its capabilities or available actions.

Expected: Codex opens the plugin browser so you can review installed plugins, discoverable plugins that your configuration allows, and installed plugin state. Press Space on an installed plugin to toggle its enabled state.

View and manage lifecycle hooks with /hooks

1. Type /hooks.
2. Choose a hook event to inspect the matching handlers.
3. Trust, disable, or re-enable non-managed hooks as needed.

Expected: Codex opens the hook browser so you can review configured lifecycle hooks. Managed hooks appear as managed and can't be disabled from the user hook browser.

Manage chats with /agents

1. Type /agents and press Enter.
2. Select a chat from the command center to open it.

Expected: Codex shows an overview of chats on the connected server. You can inspect their status and switch between them. To open the command center directly from your terminal, run codex agents. The command center requires a shared local or remote server.

Switch agent threads with /subagents

1. Type /subagents and press Enter.
2. Select the thread you want from the picker.

Expected: Codex switches the active thread so you can inspect or continue that agent's work.

Send feedback with /feedback

1. Type /feedback and press Enter.
2. Follow the prompts to include logs or diagnostics.

Expected: Codex collects the requested diagnostics and submits them to the maintainers.

Sign out with /logout

1. Type /logout and press Enter.

Expected: Codex clears local credentials for the current user session.

Exit the CLI with /quit or /exit

1. Type /quit (or /exit) and press Enter.

Expected: Codex exits immediately. Save or commit any important work first.

Use these commands to control Codex from the VS Code Command Palette. You can also bind them to keyboard shortcuts.

Assign a key binding

To assign or change a key binding for a Codex command:

1. Open the Command Palette (Cmd+Shift+P on macOS or Ctrl+Shift+P on Windows/Linux).
2. Run Preferences: Open Keyboard Shortcuts.
3. Search for Codex or the command ID (for example, chatgpt.newChat).
4. Select the pencil icon, then enter the shortcut you want.

Extension commands

Slash commands let you control Codex without leaving the composer. Use them to check status, switch between local and cloud mode, or send feedback.

Use a slash command

1. In the Codex composer, type /.
2. Select a command from the list, or keep typing to filter (for example, /status).
3. Press Enter.

Available slash commands