claude-code - 💡(How to fix) Fix Add option to hide email address from welcome banner

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Fix Action

Fix / Workaround

  • CLAUDE_CODE_HIDE_CWD=true hides the working directory but does not affect the email display.
  • Switching to API key auth (ANTHROPIC_API_KEY) removes the email from the banner, but loses Claude Pro features and requires per-token billing — not a practical workaround for Pro subscribers.
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing requests and this feature hasn't been requested yet
  • This is a single feature request (not multiple features)

Problem Statement

The Claude Code welcome banner displays the authenticated user's email address (e.g., [email protected]'s Organization). There is no way to suppress or hide this.

This is a privacy concern when screen-sharing, live-streaming, recording demos, pair programming, or working in public spaces. The email is visible to anyone who can see your screen whenever you open a new Claude Code session.

Proposed Solution

Add a configuration option to hide the email/org from the welcome banner. Either of these would work:

  • An environment variable: CLAUDE_CODE_HIDE_EMAIL=true
  • A /config setting: privacy.hideEmailInBanner: true

The banner would still show the model, effort level, and working directory — just not the account email.

Alternative Solutions

  • CLAUDE_CODE_HIDE_CWD=true hides the working directory but does not affect the email display.
  • Switching to API key auth (ANTHROPIC_API_KEY) removes the email from the banner, but loses Claude Pro features and requires per-token billing — not a practical workaround for Pro subscribers.

Priority

Low - Nice to have

Feature Category

Configuration and settings

Use Case Example

No response

Additional Context

No response

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING