[FEATURE] VSCode integration has no way to display which subscription is currently active in my claude code conversation or panel

Status Fixed / completed
Maintainer reply None cached
Activity 4 comments · opened Mar 6, 2026 · closed Mar 9, 2026

Preflight Checklist

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

Problem Statement

i have used a company email for my personal MAX 5 subscription for work. now my company provides a enterpise subscription using the same email address and requires i use it in vscode. there appears to be (according to your claude code bot) NO indicator in vscode as to which account/subscription is currently being used for my claude code discussions. I can lose my job if i dont use the enterprise subscription for work. kinda important...
many thanks

Proposed Solution

make a command similar to "/DisplayLogin" that shows the login id and the subscription used for that connection

Alternative Solutions

_No response_

Priority

High - Significant impact on productivity

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

_No response_

View original on GitHub ↗

4 Comments

github-actions[bot] · 7 months ago

Found 3 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/30031
  2. https://github.com/anthropics/claude-code/issues/18435
  3. https://github.com/anthropics/claude-code/issues/31346

This issue will be automatically closed as a duplicate in 3 days.

  • If your issue is a duplicate, please close it and 👍 the existing issue instead
  • To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

PaulCharlton · 7 months ago

/status from the claude command line?

EUA-Ward · 7 months ago

found mine is duplicte of #30031 so closing

github-actions[bot] · 7 months ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.