Skip to main content

Codex Command Master Command Overview How to Use This Book

Core Command Groups

Core Command Group Session Command Group

Advanced Commands

Cmd. /permissions Cmd. /approve Cmd. /sandbox-add-read-dir Cmd. /agent Cmd. /app Cmd. /apps Cmd. /archive Cmd. /ide Cmd. /hooks Cmd. /compact Cmd. /diff Cmd. /exit Cmd. /experimental Cmd. /memories Cmd. /feedback Cmd. /init Cmd. /logout Cmd. /mcp Cmd. /mention Cmd. /model Cmd. /fast Cmd. /plan Cmd. /goal Cmd. /personality Cmd. /ps Cmd. /stop Cmd. /plugins Cmd. /fork Cmd. /side Cmd. /raw Cmd. /resume Cmd. /new Cmd. /quit Cmd. /review Cmd. /status Cmd. /title Cmd. /theme Cmd. /debug-config Cmd. /statusline Cmd. /keymap Cmd. /skills Cmd. /vim Cmd. /approvals

Extensions

Custom Command Guide MCP Command and Integration Guide

Operations

Verification Report Updates

Handbook›Codex Command Master›How to Use This Book

한국어 English

How to Use This Book

Recommended reading paths for different Codex users and team situations.

Key takeaways

Read overview first for command categories, then use the core and session command groups as your daily checklist.
New users should start with /status, /new, /plan, /quit, and /resume.
Team leads should focus on /permissions, /mcp, /plugins, /hooks, /review, and /diff.
Standardize command names before rollout and re-check the official slash table and changelog before updating playbooks.

Recommended Order

Read overview to understand the command categories.
Use basic-commands-core and basic-commands-session as the daily command checklist.
Open individual command pages only when you need deeper operational detail.
Check verification before using version-sensitive commands in team standards.

Paths by Situation

New Codex user: start with /status, /new, /plan, /quit, and /resume.
Team lead: focus on /permissions, /mcp, /plugins, /hooks, /review, and /diff.
Long-running work: combine /goal, /plan, /status, /compact, /ps, and /stop.
Multi-session work: use /title, /statusline, /fork, /side, and /resume.

Team Rollout Tips

Standardize the command names first; avoid teaching old aliases as primary commands.
Keep safety commands close to automation commands in onboarding material.
Re-check the official slash command table and changelog before updating internal playbooks.

Related docs

Command Overview

Categorize Codex slash commands by role and choose the right command for the job.

Cmd. /approvals

Legacy alias for the /permissions command.

Claude Code Command Master

A practical command handbook for Claude Code slash commands, CLI workflows, skills, and automation.

Slash Commands

Advanced Codex Usage · Use Codex slash commands as an operating surface for sessions, review, models, and status.

reopt Handbook

undefined · English handbook collection for practical AI engineering operations.

Command Overview

Categorize Codex slash commands by role and choose the right command for the job.

Core Command Group

The most frequently used Codex commands in one page.

On This Page

Recommended Order Paths by Situation Team Rollout Tips