CLI should show status outside session

[Glaysia]

What feature would you like to see?

• slash command /status works only inside a TUI session.
• Outside a session, codex login status just says “Logged in using ChatGPT” with no model/approval/sandbox/session id.
• Please add cli option to print the same metadata as the TUI, without opening a session or using PuTTY.

$ codex login status
Logged in using ChatGPT
<< this is so less information

I just want to see next information in bash
/status

╭──────────────────────────────────────────────────────────────╮
│ >_ OpenAI Codex (v0.42.0) │
│ │
│ Model: gpt-5-codex (reasoning high, summaries auto) │
│ Directory: ~/Documents/b3 │
│ Approval: on-request │
│ Sandbox: workspace-write │
│ Agents.md: │
│ Account: __@gmail.com (Pro) │
│ Session: 01999a57-9ae0-7721-8c84-ad0e2e85f70X │
│ │
│ Token usage: 0 total (0 input + 0 output) │
│ Limits: send a message to load usage data │
╰──────────────────────────────────────────────────────────────╯

Are you interested in implementing this feature?

No response

Additional information

No response

[samreid]

This would be a valuable feature to implement, even if it requires client or server side adjustments. Here is an actual prompt I wrote yesterday as a workaround so I would be able to use /status at the beginning of a session:

This is the world's simplest test. Do not overthink. What is 2+2? This is just a test, do not write code or overthink. We are going for speed here.

[alhridoy]

Hi @samreid @Glaysia i am on it

[samreid]

/status now has a very clear output, even before any queries are sent. So this issue is ready to close. Nice work, team.

[jonaustin]

Why is this issue closed? The PR was not merged and this is still needed.

It was closed "as completed" and it is clearly not completed @etraut-openai

[etraut-openai]

I closed it based on the "So this issue is ready to close" statement, but I see that the original request is different from some of the recent improvements to /status. I'll reopen.

There is some overlap with #4108.

[jonaustin]

Thanks @etraut-openai ! Appreciate it. Given the quotas, it's helpful to be able to plan around quota running out during heavy usage.
e.g. I was thinking of creating a tmux statusline that would track current usage in near realtime if i could call code status --json or similar (tmux, since codex doesn't currently have a way to customize the statusline like claude code does).

[oxysoft]

Related but adjacent status-surface proposal: #14043\n\nThis issue is about exposing status outside a live session, which is distinct. Still, if Codex grows a richer status ecosystem, a custom in-session statusline/widget API feels like the natural companion rather than continuing to accrete only fixed built-in status fields.