Cmd. /statusline
Configure TUI footer status-line fields.
Key takeaways
- Configure TUI footer status-line fields.
- Check the input surface and availability before using the examples below.
Purpose
Configure TUI footer status-line fields.
/statuslineAvailability
| 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
/statuslineWhen to use it
- Add model, reasoning, branch, tokens, and session ID to the footer for long work.
- Add Fast mode status if your team frequently toggles
/fast.
Choosing related commands
| Command | Difference | Choose It When |
|---|---|---|
/statusline | Changes footer fields | You need persistent in-session visibility |
/title | Changes terminal title fields | You need window/tab identification |
/status | Prints session state | You need a one-time snapshot |
Effects and persistence
Changes the status-line configuration and displayed information; it does not itself change the model or permission policy.
/statusline lets you pick and reorder TUI footer items, then persists them to tui.status_line in
config.toml.
Cautions
- Avoid overloading the footer with too many fields.
- Standardize only the fields that materially reduce team confusion.
Official sources
Complete command list · Verification scope · History for this command