Show authenticated ChatGPT workspace name in /status

Open 💬 1 comment Opened Aug 12, 2026 by azat-badretdin

What variant of Codex are you using?

CLI

What feature would you like to see?

Display the authenticated ChatGPT workspace name in the interactive /status view.

Currently, /status shows the account email and plan, for example:

Account: user@example.com (Enterprise)

For users who have access to multiple ChatGPT workspaces, this does not identify which workspace the current Codex session is using.

I'd like /status to show the authoritative ChatGPT workspace name associated with the current authentication, for example:

Account: user@example.com (Enterprise)
Workspace: Example Workspace

Ideally, this value should come from the authenticated workspace metadata rather than from a locally configured display name.

Additional information

I'm using Codex CLI v0.147.0.

I searched existing issues before filing this. Two related issues are:

#10233 proposes a non-interactive/headless status interface. Its proposed schema includes account.workspace.id and account.workspace.name.
#6360 discusses /status account/session identification when multiple logins are involved.

This request is narrower than #10233: I'm specifically requesting that the existing interactive /status view display the authenticated ChatGPT workspace name.

The motivation is to make it possible to verify at a glance that Codex is operating under the intended ChatGPT Enterprise/Business workspace. An email address plus (Enterprise) does not necessarily distinguish between workspaces available to that account.

My current /status already displays identity and session information such as Account, Directory, Thread name, Collaboration mode, and Session, so the authenticated workspace seems like a natural field to display alongside Account.

If workspace metadata is already available to Codex, it would be preferable to display that authoritative value rather than introduce a user-configurable workspace label.

View original on GitHub ↗

1 Comment

jdcodes1 · 9 days ago

Scoping note from the code: the ID token codex parses already carries the workspace identifier — IdTokenInfo.chatgpt_account_id ("Organization/workspace identifier associated with the token"), plus is_workspace_account() to know when it matters (https://github.com/openai/codex/blob/1f41cc5d92/codex-rs/login/src/token_data.rs#L29-L60). What it does not carry is the human-readable workspace name — that's not a JWT claim, so showing a name means either (a) displaying the account id (ugly but unambiguous and purely local), or (b) one lookup against the ChatGPT backend's account/workspace endpoint at login or /status time, cached in auth state.

A reasonable increment: show Workspace: <name> when a cached name exists, fall back to the account id when it doesn't, and display it only for is_workspace_account() logins so Plus/Pro personal accounts see no extra noise. The multi-workspace confusion this solves is real — the same email can be logged into different workspaces with very different data-governance settings, and today nothing in /status distinguishes them.