openai / openai/codex

Show authenticated ChatGPT workspace name in /status

Open
#38,196 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

auth CLI enhancement TUI
Dominant language
Rust
Stars
125k
Forks
19.5k
PR merge metrics
PR metrics pending

Description

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.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the interactive /status view and trace how the current account email and plan are obtained and rendered. Check whether authenticated workspace metadata is already available; done means displaying its authoritative workspace name alongside the existing account information, including for users with multiple workspaces.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
authentication, cli
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.