Make /status output safer to share by redacting account and session details

Open
#34,869 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
rust
Domain
cli, security

Research direction

Start by locating the /status command entry points in the Codex app and CLI, then trace where account and session details are assembled. Compare the proposed default-redaction and explicit-full-output alternatives, and define completion around share-safe output that preserves an intentional way to reveal full details.

Written by the indexing model from the issue text.

Description

auth CLI enhancement session TUI
What variant of Codex are you using?

App / CLI, etc

What feature would you like to see?

Summary

The /status command can expose information that users may not realize is sensitive:

  • In the Codex app, it includes the session ID.
  • In the Codex CLI, it can include account details such as the user’s personal email address.

People frequently share screenshots of /status on social media and in the Codex Discord to show their weekly limits, usage, or progress. They may not notice that the same screenshot also reveals their
account details. It would also be preferable not to expose the full session ID unnecessarily.

Suggested behavior

Consider redacting sensitive fields in /status output, such as:

  - Email address: `f••••@example.com`
  - Session ID: `019•••••••••••••••••••••••••••••`

One possible approach would be to make the redacted output the default and provide an explicit option to reveal everything:

/status --full

Alternatively, to preserve the existing behavior, /status could continue showing the full details while offering a share-safe mode:

/status --privacy

The first option—redacting sensitive information by default, would provide stronger protection because users may not realize they need to enable privacy mode before taking a screenshot.

Additional information

Why this would help

A share-safe /status output would reduce accidental disclosure while preserving access to the full information when it is genuinely needed. This is especially useful because screenshots of usage and
rate-limit information are commonly shared publicly.

Dominant language
Rust
Stars
125k
Forks
19.5k
Avg merge
1m
Merged PRs (30d)
1k

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.

More from openai/codex

All issues in openai/codex

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.