Slash Commands

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 release-specific behavior: /archive is official table coverage, /app is a 0.138.0 handoff command, and 0.139.0 adds code-mode web search, MCP schema preservation, resume/fork --last handling, and sandbox diagnostics.
• 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 as official table coverage and /app as a 0.138.0 release-tracked handoff command until it appears in the slash table.
• Track the adjacent 0.139.0 operational changes with command docs: code-mode web search, MCP schema preservation, resume/fork --last prompt handling, and sandbox diagnostics.

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.