Cmd. /statusline

Purpose

Configure TUI footer status-line fields.

/statusline

Availability

The installed command menu and account or organization settings determine availability.

Examples

/statusline

Choosing footer items

1. Run /statusline in the prompt to open the item picker.
2. Pick the footer items and set their order. The official command docs list the model, context usage, rate limits, git branch, token counters, session ID, current directory, and Codex version as examples.
3. Confirm. The footer updates right away and your choice is saved as the status_line array under [tui] in config.toml.

tui.status_line is an array of item identifiers in display order. The official config reference does not publish the list of valid identifiers, so pick items with /statusline and copy the saved array into team settings rather than typing identifiers by hand.

When to use it

1. During long work, keep context usage and rate limits in view instead of running /status repeatedly.
2. When switching between worktree or branch sessions, add the git branch and session ID to tell them apart.
3. When your team often toggles /fast or changes models, add the model item so a switch is never missed.

Related commands and where they save

Effects and persistence

Changes which footer items appear and in what order, and saves them to tui.status_line in config.toml; it does not change the model or permission policy.

The saved value applies to later launches as well. From 0.128.0 you can edit it during an active turn, so long work does not have to stop. Version changes are in the command history.

Cautions

• Item identifiers can be added or renamed between versions. Before adding them to shared team settings, confirm the same items appear in your installed picker.
• The footer only changes what is displayed. Use /model, /permissions, or /usage to change the underlying settings.
• If both user settings and a project .codex/config.toml set the value, check which one applies with /debug-config.
• Too many items get cut off in narrow terminals. Pin only the information your team actually confuses.

Official sources

• Developer Commands
• Cli
• Config reference

Complete command list · Verification scope · History for this command