Add device/session management for Claude Code authentication

[anuvc]

Feature Request

Problem

There is currently no way to view or manage which devices/sessions Claude Code is authenticated on. If a user wants to check where they're logged in or revoke access from a specific device remotely, there's no mechanism to do so.

Proposed Solution

Add device/session management capabilities, similar to what GitHub, Gmail, and other services provide:

• View active sessions: A list of all devices/sessions where Claude Code is currently logged in (device name, OS, location, last active time)
• Remote logout: Ability to revoke access or log out from specific devices remotely
• CLI commands: Accessible via the CLI (e.g., claude sessions list, claude sessions revoke <id>) and/or the Anthropic Console

Why This Matters

• Security: Users need visibility into where their account is authenticated, especially if a device is lost or compromised
• Account hygiene: Ability to clean up old sessions from devices no longer in use
• Parity with other tools: Most developer tools (GitHub CLI, cloud provider CLIs) offer session/device management

Current Workarounds

• Manually running claude logout on each device with physical access
• Rotating API keys (only applies to key-based auth)
• Changing account password to invalidate OAuth sessions (nuclear option)

None of these provide visibility into active sessions or targeted revocation.

[github-actions]

Found 1 possible duplicate issue:

1. [FEATURE] Add centralized session/token management dashboard for Claude Code Max subscribers #22995

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

[github-actions]

This issue has been automatically closed as a duplicate of #22995.

If this is incorrect, please re-open this issue or create a new one.

🤖 Generated with Claude Code

[github-actions]

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.