claude-code - 💡(How to fix) Fix [FEATURE] Remote session revocation / active sessions management

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

This is a common situation: office computers, home PCs shared with family, or any machine you don't fully control 24/7. The only workarounds today are changing your account password (which invalidates all sessions everywhere and is disruptive) or physically accessing the machine to run claude logout.

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

I use Claude Code on a shared or semi-shared machine — for example, a work PC that colleagues occasionally use. When I step away or work remotely, there's no way to sign out of Claude Code from another device. Anyone with access to the machine can open the terminal and use my Claude session without any additional authentication.

This is a common situation: office computers, home PCs shared with family, or any machine you don't fully control 24/7. The only workarounds today are changing your account password (which invalidates all sessions everywhere and is disruptive) or physically accessing the machine to run claude logout.

Proposed Solution

Add an "Active Sessions" page in claude.ai account settings where users can:

  • See all devices/machines with an active Claude Code session, with enough info to identify them (hostname, last active, OS)
  • Revoke access for individual sessions with one click

This follows a well-established pattern — GitHub, Google, and Spotify all offer this. Claude Code already uses OAuth under the hood, so the infrastructure for token management likely exists. This would be a UI layer on top of what's already there.

Alternative Solutions

  • Changing account password: works but invalidates all sessions everywhere and is disruptive
  • Running claude logout on the machine: requires physical access, defeats the purpose
  • OS-level user accounts: overly complex for casual shared machine scenarios

Priority

Medium - Would be very helpful

Feature Category

Configuration and settings

Use Case Example

  1. I use Claude Code on my work PC during the day
  2. I go home and realize I left the session authenticated
  3. A colleague sits at my desk and opens the terminal — Claude Code works with my account, my usage, my subscription
  4. From home, I have no way to revoke that access without changing my password or calling someone to run claude logout on my machine
  5. With active session management in claude.ai settings, I'd just open the browser, find the session for that machine, and revoke it, done in 10 seconds

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

claude-code - 💡(How to fix) Fix [FEATURE] Remote session revocation / active sessions management