[FEATURE] Add centralized session/token management dashboard for Claude Code Max subscribers
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
As a Claude Code Max subscriber using claude setup-token across multiple devices, there is currently no way to audit, view, or revoke active sessions from a single place.
Current behavior
claude setup-tokengenerates an OAuth token stored locally on each device- Token storage varies by platform (macOS Keychain, libsecret on Linux, plain file on headless systems)
- No CLI command or web dashboard to list all active tokens/sessions tied to my subscription
- No way to revoke a specific device's token remotely
- No visibility into how many concurrent session slots are in use
The problem
I use Claude Code across 4+ devices — macOS terminal, Android (Termux), and 2 Ubuntu VMs. To audit which devices are authenticated, I have to SSH into each machine and check platform-specific credential stores individually. If a device is lost or compromised, there's no quick way to revoke just that token without accessing the device itself.
Additional context
This becomes more critical when using setup-token to authorize third-party tools (e.g., AI agent platforms that consume the subscription via the token). Without centralized visibility, subscribers lose track of what's authorized to use their account.
Proposed Solution
Proposed solution
A session management panel (on claude.ai/settings or console.anthropic.com) that shows:
- Active sessions list — device name/hostname, platform, token creation date, last active timestamp
- Revoke individual tokens — invalidate a specific device without affecting others
- Concurrent usage visibility — current active slots vs plan limit
- Usage breakdown per device — token consumption per session (optional)
Prior art
- GitHub → Settings → Sessions
- Google → Security → Your Devices
- Slack → Settings → Active Sessions
These are standard for any subscription service that supports multi-device authentication.
Alternative Solutions
_No response_
Priority
Medium - Would be very helpful
Feature Category
Configuration and settings
Use Case Example
_No response_
Additional Context
_No response_
This issue has 7 comments on GitHub. Read the full discussion on GitHub ↗