Slash Commands

Command reference and shortcuts on 2026-10-23

The current slash table has 57 rows. /agents browses server chats; /subagents switches child threads of the current session. /tui, /export, /recap, /cd, /pwd (/cwd), /worktree, /daemon, and /warnings are now listed. /agent, /personality, and /sandbox-add-read-dir are absent. Use release evidence for /config and additional /voice behavior.

In 0.163.0 the default /keymap leader is Ctrl+X and voice mute is F9. /daemon warns about affected work before restarting a managed server and reconnecting. Version-specific notes below describe their historical state; this section defines the current baseline.

Developer Commands · 0.163.0 release.

Key takeaways

• Slash commands are the control panel of an interactive Codex session, so teams should standardize the ones expected during planning, review, and handoff.
• Group commands by purpose: Status, Review, Planning, Context, and Lifecycle (stop, resume, fork, compact, archive, hand off, or start a new thread).
• Run review commands before requesting human review on risky changes, and keep slash-command output tied to actual verification rather than treating commands as magic words.
• Track the current official inventory: /app, /copy, /rename, /pets (/pet), and Windows-only /setup-default-sandbox are documented commands; /subagents now has its own thread-switching role, and /btw aliases /side.
• Codex 0.148.0 adds /export for the complete TUI conversation. In 0.150.0, /copy opens a picker for the whole response, code blocks, or blockquotes.
• Codex 0.149.0 adds /cd, /pwd, and /cwd; 0.150.0 adds automatic task titles and editable /rename suggestions.
• On 0.146.0, /new [name] and /clear [name] name fresh threads immediately, while /side can switch among open side conversations without closing them.
• Follow a repeatable routine: inspect status, attach relevant files, request a plan, review the diff, then run verification and summarize evidence.

Slash commands are the control panel of an interactive Codex session. Teams should standardize the commands they expect developers to use during planning, review, and handoff.

Command Categories

Team Practices

• Use review commands before requesting human review on risky changes.
• Record useful command sequences in repository docs.
• Keep slash-command output tied to actual verification.
• Avoid using commands as magic words; define what decision each one supports.
• Treat /archive and /delete as different retention decisions: archive keeps a recoverable transcript, while delete permanently removes the transcript and spawned descendants.
• Run /usage before long /goal or multi-agent sessions, and review /import results with /diff and /debug-config.
• Treat /app as an officially documented handoff command, originally release-tracked from 0.138.0.
• Treat /import as a migration review: 0.145.0 expands it across Cursor and Claude Code settings, MCP servers, plugins, sessions, commands, and project memories.
• Review /export output for secrets and customer data before storing or sharing a full transcript.
• Release-tracked in 0.155.0–0.157.0 but not yet in the official slash table: /voice (experimental in 0.155.0, on by default from 0.156.0, F8 toggle, /voice settings), /tui to choose the fullscreen UI for the next launch (fullscreen transcripts are default from 0.157.0), and /daemon to update the local background server. /usage becomes an analytics dashboard in 0.156.0, and /import works in remote and background-server sessions from 0.157.0.
• /personality is absent from the current table, and 0.156.0 removed personality selection from the TUI and the deprecated friendly and pragmatic settings no longer change response style; keep style guidance in AGENTS.md instead.

Example Routine

1. Inspect status and permissions.
2. Attach or mention the files that matter.
3. Ask for a plan or scoped implementation.
4. Review the diff.
5. Run verification and summarize evidence.

August 28 Command Inventory Re-check