claude-code - 💡(How to fix) Fix Feature request: Option to hide organization name from startup display

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

Workarounds: Currently, the only ways to avoid this are switching to a personal/non-org account or authenticating via API key, neither of which may be desirable for users who need org-level plan features.

RAW_BUFFERClick to expand / collapse

Feature Request

Summary: Add a setting to hide or suppress the organization name line (e.g., "[email protected]'s Organization") that appears during Claude Code startup.

Problem: When logged in under an organization account, the org identifier is always displayed at startup. Some users (especially solo developers or personal-use orgs) find this unnecessary clutter and would prefer a cleaner startup experience.

Proposed solution: Add a user-configurable setting (e.g., hideOrgDisplay or showOrganization: false) in settings.json or settings.local.json to suppress the organization line from the startup display. This would be a cosmetic preference and would not affect authentication or org-level policies.

Workarounds: Currently, the only ways to avoid this are switching to a personal/non-org account or authenticating via API key, neither of which may be desirable for users who need org-level plan features.

extent analysis

TL;DR

Adding a user-configurable setting to hide the organization name line during startup is the most likely fix.

Guidance

  • Review the proposed solution of adding a hideOrgDisplay or showOrganization: false setting in settings.json or settings.local.json to determine its feasibility and potential impact on the application.
  • Consider the trade-offs between adding a new setting versus other potential solutions, such as modifying the existing authentication flow or display logic.
  • Evaluate the potential effects of this change on different user roles and organization types to ensure it meets the needs of various stakeholders.
  • Investigate how the setting would be implemented and stored, ensuring it is secure and follows best practices for user configuration management.

Example

No code snippet is provided as the issue focuses on a feature request rather than a specific code-related problem.

Notes

The solution's implementation details, such as how the setting would be stored and applied, are not specified in the issue and would require further investigation.

Recommendation

Apply workaround: Until a formal setting is implemented, users could explore alternative authentication methods or account types that do not display the organization identifier, albeit with the understanding that these workarounds may not be ideal for all users.

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

claude-code - 💡(How to fix) Fix Feature request: Option to hide organization name from startup display