Cmd. /status
Inspect session configuration, token usage, model, and policy.
Key takeaways
- Inspect session configuration, token usage, model, and policy.
- Check the input surface and availability before using the examples below.
Purpose
Inspect session configuration, token usage, model, and policy.
/statusAvailability
| Field | Value |
|---|---|
| Input surface | Running CLI prompt |
| Kind | Built-in |
| Status | Current reference |
| Aliases | — |
| Documented minimum | Not specified |
| Reviewed against | 2026-09-22 · Codex CLI 0.155.1 |
The installed command menu and account or organization settings determine availability.
Examples
/statusWhen to use it
- Run
/statusat the start of a task to verify model, directory, and permissions. - Run
/statusafter/permissions,/model,/resume, or/goal.
Choosing related commands
| Command | Difference | Choose It When |
|---|---|---|
/status | Inspects runtime state | You need to know how Codex is configured |
/model | Changes model | You need to switch after checking state |
/debug-config | Explains config layers | You need deeper config diagnostics |
Effects and persistence
Inspects current session state so you can check the effective model, permissions, and usage.
/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.
Cautions
/statustells you state; it does not change policy or fix configuration by itself.- In remote or resumed sessions, re-check state before editing.
Official sources
Complete command list · Verification scope · History for this command