Complete command list

Reading the labels · Terminal CLI reference

Official slash table

Release additions, aliases, and older commands

These entries track evidence outside the official table and names from older documents. For removed or renamed entries, use the current replacement given in the command guide.

Command guides

Syntax, examples, and effects for commands without a page of their own, grouped by category. Select "Guide" in the tables above to jump to a command. Unless noted, the installed command menu and account or organization settings determine availability.

Conversation and context

/clear

Clear the terminal and current chat context, then start a fresh Codex chat.

/clear

Kind Built-in · Current reference.

Effects Starts a fresh conversation. Restate instructions that depended on the previous conversation when needed.

More sources Changelog

When to use it

1. Inspect /diff, then use /clear before beginning an unrelated task.
2. Run /export before /clear when the transcript is an audit artifact.

Choosing related commands

/clear clears the terminal and starts a fresh chat. The Developer Commands signature checked on 2026-08-30 has no name argument, so this handbook no longer documents /clear [name]. Use /new [name] when the new chat needs a name at creation time.

Cautions

• /clear does not revert Git changes or delete generated files.
• Record a name, session ID, or export first when the old transcript must be recoverable.
• If the installed build differs, treat its slash popup and / as the build-specific contract.

/rename

Rename the current saved Codex chat without changing its transcript or execution state.

/rename [name]

Kind Built-in · Current reference.

Examples

/rename parser-migration

Effects Changes the current session's name while retaining its conversation.

More sources Slash_Command.Rs

When to use it

1. Run /rename AUTH-241 refresh-token race to record the issue and purpose.
2. Run /rename without arguments and edit the suggested title to match the team convention.

Choosing related commands

/rename [name] updates the saved name of the current chat without changing its transcript.

Cautions

• Renaming does not change the transcript or Git branch.
• Do not put secrets, customer data, or tokens in chat names.
• Prefer a short searchable prefix over a long description.
• Unnamed tasks receive automatic titles in 0.150.0+, but durable work should still use a reviewed team-readable name.

/delete

Permanently delete the current Codex session transcript and spawned descendant sessions.

/delete

Kind Built-in · Current reference.

Effects Opens the permanent session-deletion flow. Use archive when you only want to put the session aside.

More sources Changelog

When to use it

1. Delete a temporary test session that included sensitive prompt material.
2. Remove an abandoned experiment and its spawned descendant sessions.
3. Before deleting an audit-relevant session, capture required evidence in a ticket, PR, or export.

Choosing related commands

/delete is an official slash command for permanently deleting the current Codex session transcript and exiting the TUI. Use it for sensitive or disposable sessions where archiving is not enough.

Cautions

• Deletion is permanent; check retention, audit, and incident-response needs first.
• /delete is unavailable while a task is running or inside a side conversation.
• If you only want to clean the resume list, use /archive.

/compact

Summarize a long conversation to free context.

/compact

Kind Built-in · Current reference.

Effects Replaces older conversation context with a summary. Identify decisions and constraints that must survive before compacting.

When to use it

1. Compact after a long investigation before moving into implementation.
2. Compact before handing a session to another teammate, then run /status.

Choosing related commands

/compact summarizes the visible conversation so Codex can keep the critical points without overloading the context window.

Cautions

• Review the summary if the task contains subtle requirements.
• Do not compact away unresolved blockers, IDs, test results, or acceptance criteria.

/memories

Configure memory use and generation for Codex sessions.

/memories

Kind Built-in · Current reference.

Effects Manages memory settings for future sessions; it does not erase the current conversation or all previously stored memories.

More sources Memories

When to use it

1. Disable memory behavior before working with sensitive external context.
2. Verify memory settings when a long-running project depends on team preferences.

Choosing related commands

/memories controls whether Codex uses existing memories and whether new sessions contribute to memory generation.

Cautions

• Treat memories as a convenience layer with explicit privacy rules.
• Be conservative when web, MCP, or browser context is involved.

/init

Generate an AGENTS.md scaffold for persistent repository instructions.

/init

Kind Built-in · Current reference.

Effects Starts creation or updating of project instructions. Review the proposed file contents and project scope.

When to use it

1. Run /init at the repository root before writing team-specific Codex guidance.
2. Edit the generated AGENTS.md to include test commands, coding standards, and safety rules.

Choosing related commands

/init creates an AGENTS.md scaffold in the current directory so future Codex sessions can load repository-specific instructions.

Cautions

• Treat the generated file as a scaffold, not a finished policy.
• Keep instructions concise and maintainable; stale instructions are worse than missing instructions.

/mention

Attach a file or path to the conversation.

/mention <path>

Kind Built-in · Current reference.

Examples

/mention src/main.ts

Effects References a selected file or path in the prompt without editing the file merely by mentioning it.

When to use it

1. Mention the file that contains the failing behavior before asking for a fix.
2. Mention a design doc or config file when the next request depends on it.

Choosing related commands

/mention highlights a file or folder for Codex so the next turns can reference that context directly.

Cautions

• Mention only the files that matter; too much context can distract the model.
• Do not mention files containing secrets unless the task truly requires it and the policy allows it.

/fork

Branch the current conversation into a new thread.

/fork

Kind Built-in · Current reference.

Effects Branches the current conversation into a separate thread for another approach.

When to use it

1. Fork before trying an alternate implementation path.
2. Use codex fork from the shell when you need to fork a saved session rather than the current one.

Choosing related commands

/fork clones the current conversation into a new thread with a fresh ID, preserving the original transcript.

Cautions

• Forked work still needs review, diff inspection, and tests.
• Name or title related sessions so you can identify them later.

/side

Start an ephemeral side conversation from the current thread.

/side

Kind Built-in · Current reference · Aliases /btw.

Effects Handles a side question separately from the main task flow.

More sources Changelog

When to use it

1. Use /side Check whether this plan has an obvious risk for a short independent critique.
2. Ask a policy or documentation question without polluting the main transcript.
3. Let the human decide whether the side result should influence the parent thread.

Choosing related commands

/side (/btw) starts a focused side conversation without switching the main task away from the parent thread.

Cautions

• You cannot open /side from inside another side conversation.
• /side is unavailable in review mode.
• Use /fork for longer alternate implementations.

/resume

Reopen the saved-session picker to continue earlier Codex work across interruptions, remote app-server sessions, and large multi-thread task histories.

/resume

Kind Built-in · Current reference.

Effects Continues the selected saved conversation. From 0.160.0, saved permissions are restored unless you explicitly override them. Check its working directory, model, and permissions after resuming.

More sources Rust V0.160.0

When to use it

1. Resume a prior migration thread, then run /status and /goal before continuing.
2. Use /title or /statusline after resume when many sessions have similar names.
3. After a long break, compare /diff and the current branch state before editing again.

Choosing related commands

/resume opens the saved-session picker so you can continue work from a previous CLI session. It is the command for preserving continuity across interruptions, remote app-server sessions, and large multi-thread task histories.

Cautions

• After resume, confirm model, permissions, working directory, and active goal.
• Do not assume old context is still correct after external code changes.
• If the repository changed outside the thread, inspect current Git state before relying on old assumptions.

/new

Start a new conversation inside the current CLI session.

/new [name]

Kind Built-in · Current reference.

Examples

/new parser-migration

Effects Starts a fresh conversation. Restate instructions that depended on the previous conversation when needed.

When to use it

1. Use /new when switching to an unrelated task in the same repository.
2. Use /plan immediately after /new when the new task has risk or ambiguity.

Choosing related commands

/new [name] resets chat context inside the same CLI session and optionally persists a thread name.

Cautions

• Save important details before starting a new conversation.
• /new does not replace Git hygiene; review changes before changing tasks.

/export

Export the complete TUI conversation as Markdown to the clipboard or a new file.

/export

Kind Built-in · Current reference · Release evidence v0.148.0. This entry is absent from the current command table or tracked separately through releases. Check the evidence and installed build.

Effects Exports conversation content to the supported destination. Code and local paths in the conversation may be included.

More sources Changelog · Rust V0.148.0

Choose the clipboard or a new Markdown file as the destination.

When to use it

1. Preserve a long investigation as evidence for a team document or issue.
2. Save a reproducible work record as a Markdown artifact.
3. Export a migration or incident-response conversation for retrospective review.

Choosing related commands

/export exports the complete current TUI conversation as Markdown to the clipboard or a new file.

Cautions

• The exported file contains conversation content; check its destination and whether it belongs in the repository.
• Remove secrets, access tokens, customer data, and local absolute paths before external sharing.
• Do not treat conversation export as a replacement for structured audit logs or retention policy.

/recap

Manual task recaps and the automatic recap setting

/recap

Kind Built-in · Current reference · Release evidence v0.153.0. Tracked through releases outside the slash table. Manual /recap remains available with tui.auto_recap = false.

Effects Shows a short recap of the conversation. It serves a different purpose from context compaction.

More sources Changelog

Use /recap for a manual recap. Disable automatic recaps in user configuration with:

[tui]
auto_recap = false

0.153.0 explicitly preserves manual /recap when automatic recaps are disabled. Add the key to an existing [tui] table rather than duplicating the table. /compact is a separate command for freeing context space.

Cautions

Tracked through releases outside the slash table. Manual /recap remains available with tui.auto_recap = false.

Planning and execution

/plan

Switch to plan mode and optionally send a planning prompt.

/plan

Kind Built-in · Current reference.

Effects Switches to a planning workflow. Review the plan and scope before implementation starts.

More sources Rust V0.159.0

When to use it

1. Use /plan Propose a migration plan for this package before editing a risky module.
2. Use /plan after /status when you need Codex to reason through scope before implementation.

Choosing related commands

/plan switches the active conversation into plan mode. You can include inline text as the first planning request.

From 0.159.0, you can scroll the transcript with the mouse wheel while the prompt asking whether to implement the plan is open, so earlier plan steps stay reviewable.

Cautions

• /plan is temporarily unavailable while a task is already running.
• Planning is not verification; still run tests or reviews after implementation.

/ps

Show background terminals and recent output.

/ps

Kind Built-in · Current reference.

Effects Lists background terminal work in the current session. From 0.158.0, multiline commands are shown in the preview.

More sources Rust V0.158.0

When to use it

1. Run /ps before /stop so you know what will be cancelled.
2. Check /ps before exiting a session that started a dev server or long test run.

Choosing related commands

/ps lists experimental background terminals and shows recent output so you can understand what is still running.

From 0.158.0, /ps also shows multiline commands in its preview.

Cautions

• Background terminals appear when the relevant exec mechanism is in use.
• /ps inspects session-owned background terminals, not every process on the machine.

/stop

Stop all background terminals owned by the current Codex session.

/stop

Kind Built-in · Current reference · Aliases /clean.

Effects Stops active background work in the current session.

When to use it

1. Run /ps first, then /stop when a watcher or long test is no longer needed.
2. Use /stop before leaving a session that started background work.

Choosing related commands

/stop stops all background terminals for the current session. /clean remains available as an alias.

Cautions

• /stop targets Codex background terminal work. It does not guarantee cleanup of unrelated external processes.
• Inspect with /ps before stopping when there is any doubt.

Review and verification

/review

Ask Codex to review the current working tree.

/review

Kind Built-in · Current reference.

Effects Starts a dedicated review of changes. Decide which findings to apply after inspecting the review.

When to use it

1. Run /review after implementation and before committing.
2. Follow with /diff when you need to inspect the exact changed lines behind a finding.

Choosing related commands

/review asks Codex to review local working tree changes, focusing on behavior changes, risks, and missing tests.

Cautions

• Review findings are not a substitute for running tests.
• Make sure user edits and Codex edits are understood in a dirty worktree.

Models and settings

/fast

Turn Fast mode on or off, or report its status, to change the service tier without changing reasoning effort.

/fast

Kind Built-in · Conditional. Requires Fast support in the model catalog; check credit usage for the selected service tier.

Effects Switches the supported model's fast processing path. It is separate from reasoning effort and may have different billing or quota rules.

More sources Releases · Speed

When to use it

1. Use /fast on when faster responses justify increased credit consumption.
2. Use /fast off to switch back, and /fast status to verify the setting.

Choosing related commands

/fast turns Fast mode on or off, or reports the current Fast mode status.

Cautions

• The command is visible only when the active model catalog offers a Fast tier.
• Document when the team expects Fast mode to be allowed.

Permissions and integrations

/permissions

Change Codex approval and permission policy during a session.

/permissions

Kind Built-in · Current reference · Aliases /approvals.

Effects Applies the chosen permission policy or rules to later tool calls. Managed organization settings can restrict the available choices.

More sources Rust V0.158.0 · Rust V0.160.0

When to use it

1. Start a risky refactor in a stricter mode, then move to a more autonomous mode after the plan is clear.
2. Use /status before and after the change to confirm the effective approval policy.

Choosing related commands

/permissions adjusts what Codex can do without asking first. Use it to tighten or relax approval requirements while the session is still running.

From 0.158.0, approval for sending terminal input to commands running with elevated permissions (write_stdin_approval) is on by default. From 0.160.0, a session started in a directory outside a project skips the folder-trust prompt and applies workspace-write permissions and granular approval defaults only when local execution, configuration, and managed policy allow them. Use /status to confirm the permissions in effect.

Cautions

• Treat /permissions as part of the safety boundary, not as a convenience toggle.
• Re-check policy after side conversations, resumed sessions, or remote app-server flows.

/ide

Include open files, selections, and IDE context in the next prompt.

/ide

Kind Built-in · Current reference.

Effects Shows the current session's IDE connection and integration target. File edits occur through subsequent requests and tool calls.

More sources Ide

When to use it

1. Ask Codex to refactor the function currently selected in your IDE.
2. Reuse open-file context without restating every relevant path.

Choosing related commands

/ide brings IDE context such as open files and the current selection into the next Codex prompt.

Cautions

• IDE context does not replace complete project context.
• Check open sensitive files before attaching editor state.

/setup-default-sandbox

Set up the elevated Windows agent sandbox when Codex is running in degraded restricted-token mode.

/setup-default-sandbox

Kind Built-in · Conditional. Native Windows only; distinguish this from Linux sandboxing under WSL.

Effects Runs the Windows default-sandbox setup flow.

More sources Slash_Command.Rs

When to use it

1. Run it after Codex detects the degraded Windows sandbox and offers elevated setup.
2. Verify the resulting sandbox and approval state with /status and /permissions.

Choosing related commands

/setup-default-sandbox configures the elevated Windows agent sandbox when Codex detects degraded mode.

Cautions

• This is Windows-only and appears only in the degraded restricted-token state.
• Check organizational endpoint and security policy before the administrator flow.
• Re-check the effective mode and writable roots with /status afterward.

/sandbox-add-read-dir

Older sandbox read-path command, absent from the current reference.

/sandbox-add-read-dir <absolute-directory-path>

Kind Built-in · Not in current table. Absent from the reference reviewed on 2026-10-23. Check the installed menu and use current permission or agent controls.

Examples

/permissions

Effects Preserved as an older sandbox read-path command. On current installations check /permissions and permission-profile paths, and verify support in the installed menu.

/approve

Approve one retry of a recent auto-review denial.

/approve

Kind Built-in · Current reference.

Effects Retries one selected recent auto-review denial once without changing future permission policy.

More sources Auto Review

When to use it

1. Retry a local test command after you confirm the auto-review denial was too conservative.
2. Keep the current permission policy while allowing one specific denied action to run again.

Choosing related commands

/approve lets you review a recent auto-review denial and retry that specific action once.

Cautions

• /approve is not a permanent permission-policy change.
• Repeated denials usually mean the policy or task setup needs adjustment.

/skills

Browse and apply local skills for task-specific behavior.

/skills

Kind Built-in · Current reference.

Effects Shows available skills. Executing a skill or changing its visibility is a separate action from opening the list.

More sources Build Skills · Figma Designs To Code · User Stories To Ui Mocks · Rust V0.159.0

When to use it

1. Select the Figma skill to pull design context and screenshots from an exact node before implementation.
2. Use $imagegen for UI mock directions or $playwright to verify the implementation in a real browser.
3. Confirm that team-provided skills are visible in the current session.

Choosing related commands

/skills lets you browse available Codex skills and apply the relevant skill context to a task.

Cautions

• Skills can load from project, user, or administrator locations.
• Skills that depend on scripts or MCP servers need the same approval policy review as other tools.
• The bundled plugin-creator skill was removed in 0.159.0 and no longer appears in the picker.
• Figma, ImageGen, and Playwright are not built-in /design commands. Use the exact token exposed by the /skills picker and installed bundle.

Status and diagnostics

/agent

Older /agent spelling; use /agents for the command center and /subagents for child threads.

/agent

Kind Built-in · Not in current table. Absent from the reference reviewed on 2026-10-23. Check the installed menu and use current permission or agent controls.

Examples

/agents
/subagents

Effects Current guidance separates /agents and /subagents. No alias or support contract is inferred for the older /agent spelling.

More sources Rust V0.160.0 · Rust V0.162.0

/apps

Browse apps and connectors, then insert app mentions into the prompt.

/apps

Kind Built-in · Current reference.

Effects Browses and manages available apps. App connection and approval of individual tool actions remain distinct.

When to use it

1. Use /apps before asking Codex to work with a connector so the app mention is explicit.
2. Pair /apps with /permissions when the connector exposes actions with side effects.

Choosing related commands

/apps browses connected apps and inserts them into the composer as app mentions such as $app-slug.

Cautions

• An app mention is not a substitute for reviewing tool permissions.
• Connector availability can differ by account, workspace, and installed plugin state.

/diff

Review staged, unstaged, and untracked Git changes from inside Codex.

/diff

Kind Built-in · Current reference.

Effects Displays code changes; opening the viewer does not commit or revert them.

When to use it

1. Run /diff before /review so you know the exact behavioral surface being reviewed.
2. Use /diff after applying a subagent result before merging it into the main thread.

Choosing related commands

/diff shows the Git diff, including files Git is not tracking yet, so you can inspect Codex edits before committing or testing.

Cautions

• Output includes staged and unstaged changes plus files Git isn't tracking yet. Exclude files that shouldn't be committed.
• /diff is not a test. Run the relevant verification command after reviewing changes.
• In dirty worktrees, separate user changes from Codex changes before judging the result.

/feedback

Send feedback and diagnostics to Codex maintainers.

/feedback

Kind Built-in · Current reference.

Effects Opens feedback submission with diagnostic context. Review what will be sent.

When to use it

1. Use /feedback after a reproducible CLI issue while the session context is still fresh.
2. Pair it with /debug-config when the issue involves config, policy, or tool availability.

Choosing related commands

/feedback collects feedback and, when requested, diagnostics or logs for maintainers.

Cautions

• Review what information you are comfortable sending.
• Remove secrets from prompts or local files before sharing repro material.

/personality

Older style command, absent from the current table; use AGENTS.md for response preferences.

/personality

Kind Built-in · Not in current table. Absent from the reference reviewed on 2026-10-23. Check the installed menu and use current permission or agent controls.

Effects Since 0.156.0, friendly and pragmatic no longer select response styles; the command is also absent from the current table. Put response preferences in AGENTS.md.

More sources Rust V0.156.0

/raw

Toggle raw scrollback mode for easier terminal selection and copying.

/raw

Kind Built-in · Current reference.

Effects Opens a raw session view without executing code changes.

When to use it

1. Copy a long build or test log exactly as it appeared.
2. Paste an error trace into an issue without markdown rendering changes.

Choosing related commands

/raw toggles raw scrollback mode so terminal output is easier to select and copy without extra formatting.

Cautions

• /raw does not clear or compact the conversation.
• Document the default with team keybindings if terminal behavior changes are confusing.

/status

Inspect session configuration, token usage, model, and policy.

/status

Kind Built-in · Current reference.

Effects Inspects current session state so you can check the effective model, permissions, and usage.

When to use it

1. Run /status at the start of a task to verify model, directory, and permissions.
2. Run /status after /permissions, /model, /resume, or /goal.

Choosing related commands

/status displays session configuration and token usage, including the active model, approval policy, writable roots, and remaining context capacity.

Status display in 0.155.0–0.155.1

0.155.0 added live reasoning summaries in the status row and completion timestamps. In 0.155.1, new local TUI sessions default summaries to disabled while respecting explicit settings.

Official changelog

Cautions

• /status tells you state; it does not change policy or fix configuration by itself.
• In remote or resumed sessions, re-check state before editing.

/debug-config

Inspect Codex config layers, policy sources, and requirements diagnostics.

/debug-config

Kind Built-in · Current reference.

Effects Displays effective configuration and its sources without editing configuration files.

More sources Config Reference

When to use it

1. Run /debug-config when config.toml does not appear to match runtime behavior.
2. Use it before changing managed or project-scoped configuration.

Choosing related commands

/debug-config prints configuration layer diagnostics and policy details, including approval policies, sandbox modes, MCP servers, rules, residency, and experimental network settings.

Cautions

• Diagnostics may expose paths or policy details; share output carefully.
• Do not change managed policy locally without understanding ownership.

/title

Configure terminal window or tab title fields.

/title

Kind Built-in · Current reference.

Effects Adjusts the terminal title; use rename to change the session name.

More sources Changelog · Rust V0.117.0

When to use it

1. Add branch, project, or thread fields when several Codex sessions are open.
2. Use action-required title items so pending user intervention is easier to notice.

Choosing related commands

/title opens a picker for terminal title fields such as app name, project, status, thread, branch, model, and task progress.

Cautions

• Title fields are a visibility aid, not an operational source of truth.
• Use /status when policy or model state matters.

Display and input

/keymap

Inspect and remap TUI keyboard shortcuts.

/keymap

Kind Built-in · Current reference.

Effects Inspect and persist shortcuts, including a leader key. In 0.163.0 the default leader is Ctrl+X and hints remain until selection or cancellation. Voice mute moved to F9.

More sources Config Reference · Changelog · Codex CLI 0.163.0

When to use it

1. Use /keymap when tmux, SSH, VS Code terminal, or JetBrains terminal conflicts with default bindings.
2. Use /keymap debug to inspect terminal key events when the changelog-supported debug flow is available.
3. Review Vim composer contexts before standardizing modal editing shortcuts.

Choosing related commands

/keymap edits TUI shortcut bindings by context and action, then persists custom bindings to tui.keymap in config.toml.

Cautions

• Key names and contexts can expand by CLI version; document values observed in the UI.
• Avoid forcing personal preferences as team defaults unless they solve a real conflict.

/vim

Toggle Vim mode for the Codex TUI composer.

/vim

Kind Built-in · Current reference.

Effects Toggles Vim editing behavior for terminal input.

More sources Changelog

When to use it

1. Use Vim normal and insert modes while drafting longer prompts.
2. Test Vim composer behavior before setting it as the default for new sessions.

Choosing related commands

/vim switches the Codex TUI composer between default editing and Vim normal/insert behavior.

Cautions

Review tui.vim_mode_default = true when making Vim the default editing mode. Inspect shortcut conflicts with /keymap.

• /vim is now listed in the official slash commands documentation.
• Confirm that paired or training sessions will not be confused by Vim default mode.

/experimental

Toggle experimental Codex features from the TUI.

/experimental

Kind Built-in · Current reference.

Effects Lets you select experimental features offered by the installed build. Follow its activation and restart instructions.

When to use it

1. On 0.155.x, enable voice conversations here before trying /voice; from 0.156.0 voice is on by default.
2. Inspect experimental toggles during onboarding so team docs match actual feature flags.

Choosing related commands

/experimental opens controls for optional Codex features. Some changes may require a restart.

Voice conversations in 0.155.0

On 0.155.x, voice conversations were enabled through /experimental before running /voice. From 0.156.0, voice conversations and worktree support are enabled by default, so no /experimental step is needed.

Cautions

• Treat experimental toggles as version-sensitive.
• Do not put experimental behavior into team standards without a version and rollback note.

/theme

Choose and persist the TUI syntax-highlighting theme.

/theme

Kind Built-in · Current reference.

Effects Changes the terminal color theme without editing code or conversation content.

When to use it

1. Improve diff contrast in a light or dark terminal.
2. Standardize the theme used during team screen-sharing and reviews.

Choosing related commands

/theme opens the theme picker so you can preview and save Codex TUI syntax-highlighting themes.

Cautions

• 0.156.0 added six terminal themes, and inline code and file paths now use syntax theme colors.
• Themes do not change model behavior or permissions.
• Document custom theme file installation if you distribute one.

/pets

Choose or hide an ambient terminal pet in the Codex TUI.

/pets [off]

Kind Built-in · Current reference · Aliases /pet.

Examples

/pets
/pets off

Effects Selects a displayed pet or hides it with off.

More sources Rust V0.131.0

When to use it

1. Run /pets to choose a built-in or compatible custom pet.
2. Run /pets off before screen-sharing or in a constrained terminal.

Choosing related commands

/pets (/pet) opens the terminal pet picker or hides the pet with off.

Cautions

• Some terminals and execution environments may not display pets.
• Do not treat the animation as a reliable task-status signal.
• Prefer accessibility and screen-sharing requirements when setting a team default.

/daemon

Menu for updating the local background server; eligible interactive sessions start it automatically from 0.157.0.

/daemon

Kind Built-in · Current reference · Release evidence v0.156.0. Added in release 0.156.0 and not yet in the official slash table. Launch with codex --no-daemon to bypass the shared background server.

Effects Inspect the connection and manage or update the Codex-owned local background server. From 0.163.0, restarting warns about affected work and reconnects automatically. Other sessions sharing the server can be affected.

More sources Changelog · Rust V0.156.0 · Rust V0.157.0 · Codex CLI 0.163.0

/daemon was added in Codex CLI 0.156.0 as a menu for the local background server. Use it to update the daemon package or restore a pinned package to the latest stable.

1. Run /daemon.
2. Choose an update action from the menu.
3. If other sessions share the server, check their state after the update.

From 0.157.0, eligible interactive sessions start the background server automatically and offer recovery choices when server settings are incompatible. To bypass the shared server, launch with --no-daemon.

codex --no-daemon

Cautions

• Several sessions share the daemon, so an update affects them too.
• From 0.156.0, daemon packages are managed separately from the standalone CLI installation.
• The command is now listed in the official slash table (2026-10-23), so confirm it appears in the installed / menu.

Account and usage

/exit

Exit the Codex CLI session; equivalent to /quit.

/exit

Kind Built-in · Current reference.

Effects Exits the CLI conversation. Choose a saved session through resume to continue later.

When to use it

1. Run /diff or /status before exiting a session with meaningful local changes.
2. Use /exit when your team prefers explicit shell-like naming over /quit.

Choosing related commands

/exit exits the CLI. It is the alternative spelling of /quit.

Cautions

• Save, commit, or intentionally discard important work before exiting.
• /exit does not replace process cleanup for externally started commands.

/logout

Sign out of Codex and clear local credentials for the current user.

/logout

Kind Built-in · Current reference.

Effects Signs out of the current account; later authenticated operations require sign-in again.

When to use it

1. Run /logout before handing a workstation to another user.
2. Use it during auth troubleshooting before logging in again.

Choosing related commands

/logout signs out of Codex. Use it when rotating accounts or leaving a shared machine.

Cautions

• Log out only after confirming no long-running work depends on the current account.
• Credential storage can differ by platform and configuration.

/quit

Exit the Codex CLI session cleanly, with /exit as the equivalent alias, after reviewing the diff and stopping background terminals.

/quit

Kind Built-in · Current reference.

Effects Exits the CLI conversation. Choose a saved session through resume to continue later.

When to use it

1. Use /quit after reviewing /diff and cleaning background terminals with /ps and /stop.
2. Use /resume later if you need to return to saved work.

Choosing related commands

/quit exits Codex CLI. /exit is equivalent.

Cautions

• Save, commit, or intentionally leave changes before exiting.
• Use /stop first if Codex-owned background terminals should not continue.

Aliases and older commands

/approvals

Legacy alias for the /permissions command.

/approvals

Kind Alias · Renamed. Legacy alias. Use /permissions in the current menu and new documentation.

Examples

/permissions

Effects Applies the chosen permission policy or rules to later tool calls. Managed organization settings can restrict the available choices.

More sources Changelog

When to use it

1. Use /approvals only when following old notes or muscle memory.
2. Rewrite team playbooks to point users to /permissions.

Choosing related commands

/approvals still works as an alias, but the official slash popup no longer lists it. Prefer /permissions in new documentation.

Cautions

• Do not teach /approvals as the primary command in new material.
• Use /permissions for clearer alignment with current docs.

Current settings and conversation controls

/agents

Browse and switch chats in the server agent command center.

/agents

Kind Built-in · Current reference. Check availability on the connected server and installed menu.

Effects Browse chats on the connected local or remote server. Use /subagents to switch child threads in the current session.

/subagents

Switch the active subagent thread in the current session.

/subagents

Kind Built-in · Current reference. Check availability on the connected server and installed menu.

Effects Inspect a child transcript or continue work in that thread. Browse server-wide chats with /agents.

/pwd

Show the working directory (alias /cwd).

/pwd

Kind Built-in · Current reference · Aliases /cwd. Check availability on the connected server and installed menu.

Effects Shows the active session directory; use /cd to change it.

/warnings

Revisit retained warnings and diagnostics.

/warnings

Kind Built-in · Current reference. Check availability on the connected server and installed menu.

Effects Reopens warnings and diagnostics seen during the session so you can inspect the cause and related configuration.

/config

Searchable settings panel (0.163.0).

/config

Kind Built-in · Release-tracked · Release evidence v0.163.0. Check availability on the connected server and installed menu.

Effects Search settings by category and apply supported changes immediately. Follow the panel indication for changes requiring a restart.

More sources Codex CLI 0.163.0

Official sources

• Codex CLI command reference
• Changelog