Customizable status line
## Feature Request ### Problem Claude Code has a built-in customizable status line feature that allows users to display useful real-time information at the bottom of the terminal UI — token usage, model name, rate limits, context window, git branch, etc. This is configured via a simple shell script hook in settings: ```json { "statusLine": { "type": "command", "command": "/bin/bash ~/.claude/statusline.sh", "padding": 0 } } ``` The script receives JSON context on stdin and returns formatted text. This is incredibly useful for power users who want to monitor their session at a glance. **Codex CLI currently has no equivalent mechanism.** There's no way to display custom information in the TUI — no status line, no hooks, no plugin system for UI customization. ### Proposed Solution Add a `statusLine` (or similar) configuration option to `~/.codex/config.toml` that allows running an external command and rendering its output in the Codex TUI (e.g., at the bottom of the screen). Something like: ```toml [status_line] command = "/bin/bash ~/.codex/statusline.sh" refresh_interval_secs = 10 ``` The command would receive session context (model, token count, etc.) as JSON on stdin and return a single line of text (with ANSI colors) on stdout. ### Use Cases - Display current model and token/context usage - Show API rate limit status and reset times - Display git branch and repo info - Show project-specific metadata - Integration with external monitoring tools
Posted by pkondaurov on Apr 14, 2026, 7:24 PM
Tags
Related issues
- To be fair, Inform7 can't succeed, generally, because there is no market for the kind of games that you create with Inform7.
- > The notion that somehow LR reliability is misunderstood by Consumer Reports, JD Power, Car & Driver, Automobile etc.
- Custom trigger IDs are not displayed in the new 2026.10 trigger selector
- I hate that too, but I think it’s more the ux than the concept of a default.
- > The biggest problem with UX developers is they know better than you AND force you into their paradigm.
- "Focus follows mouse" is what I use to keep the file manager from popping up when click-dragging files.
Raise real-world problems, find people facing the same issue, and discuss solutions.2,000 issues0 comments
ux (Other)
To be fair, Inform7 can't succeed, generally, because there is no market for the kind of games that you create with Inform7.
New> The notion that somehow LR reliability is misunderstood by Consumer Reports, JD Power, Car & Driver, Automobile etc.
Custom trigger IDs are not displayed in the new 2026.10 trigger selector
I hate that too, but I think it’s more the ux than the concept of a default.
> The biggest problem with UX developers is they know better than you AND force you into their paradigm.
"Focus follows mouse" is what I use to keep the file manager from popping up when click-dragging files.
The biggest problem with this is if the target URL doesn't load but also doesn't quickly error out, like e.g.
Google wants to build up a private web here.
Customizable status line
## Feature Request ### Problem Claude Code has a built-in customizable status line feature that allows users to display useful real-time information at the bottom of the terminal UI — token usage, model name, rate limits, context window, git branch, etc. This is configured via a simple shell script hook in settings: ```json { "statusLine": { "type": "command", "command": "/bin/bash ~/.claude/statusline.sh", "padding": 0 } } ``` The script receives JSON context on stdin and returns formatted text. This is incredibly useful for power users who want to monitor their session at a glance. **Codex CLI currently has no equivalent mechanism.** There's no way to display custom information in the TUI — no status line, no hooks, no plugin system for UI customization. ### Proposed Solution Add a `statusLine` (or similar) configuration option to `~/.codex/config.toml` that allows running an external command and rendering its output in the Codex TUI (e.g., at the bottom of the screen). Something like: ```toml [status_line] command = "/bin/bash ~/.codex/statusline.sh" refresh_interval_secs = 10 ``` The command would receive session context (model, token count, etc.) as JSON on stdin and return a single line of text (with ANSI colors) on stdout. ### Use Cases - Display current model and token/context usage - Show API rate limit status and reset times - Display git branch and repo info - Show project-specific metadata - Integration with external monitoring tools
Comments (0)
No comments yet. Start the discussion.