claude-code - 💡(How to fix) Fix [FEATURE] Let users remove stale/dead Remote Control environments from the claude.ai/code environment list [2 comments, 2 participants]

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

After running claude remote-control multiple times on my local machine and shutting each session down (Ctrl+C / closing the terminal), the old environments continue to appear in the environment list at claude.ai/code. The entries persist indefinitely with no way to remove them, even though none of them work anymore, clicking them leads to a dead/non-functional session.

Over time, anyone who uses Remote Control regularly ends up with a long list of stale, non-functional environments in the web UI, making it hard to find the one active session among the dead ones. There is currently no affordance in the CLI or on the web to delete these stale entries.

Proposed Solution

Expected behavior: Users should be able to remove dead Remote Control environments from the list shown at claude.ai/code (and the mobile apps). Feature request:

1. Remove from web UI — A "Remove" / trash icon next to each entry in the environment list at claude.ai/code that deletes the stale environment from the list. This is the primary request.
2. Bulk "Clean up disconnected" action — A single button that removes all environments that are no longer online, for users who accumulate many of them.
3. CLI command — Something like claude remote-control --list and claude remote-control --revoke <session> for users who prefer the terminal.
4. Optional auto-cleanup — After a configurable period of inactivity (e.g., 24h / 7d), stale environments are removed automatically.

Why this matters

• UX / clutter: The environment dropdown becomes unusable after normal daily use of Remote Control. There's no way to tell at a glance which sessions are alive without clicking.
• User control: Users should be able to manage their own environment list. Right now there's no action of any kind available on these entries.
• Security (secondary): As noted in #28917, stale session links can linger with no way to invalidate them, which is a concern on shared machines.

Alternative Solutions

No response

Priority

Medium - Would be very helpful

Feature Category

CLI commands and flags

Use Case Example

1. Start a Remote Control session in the morning, work on it, close the terminal at lunch.
2. Start another one in the afternoon on a different project, close it at the end of the day.
3. Next day, repeat.
4. Within a week, claude.ai/code shows 10+ dead environments in the list with no way to remove them, making it hard to locate the one I'm currently using.

Additional Context

Related: #28917 (focuses on security/link-invalidation after shutdown). This request overlaps but emphasizes the environment list UX at claude.ai/code specifically, and the case where a user has accumulated multiple stale entries from normal repeated use.