Remote Control: phantom sessions cannot be closed

Description

After using /remote-env to set a default remote environment, one or more
remote control sessions remain active ("phantom sessions") and cannot be
closed from the interface.

Environment

• Claude Code version: (please fill in — run claude --version)
• OS: Windows 11 Enterprise
• Remote environment ID: env_01Txxxxxxxxxxxxxxxxxxxxxxxxx (redacted)

Steps to reproduce

1. Run /remote-env to set a default remote environment
2. Use the remote control feature across multiple sessions
3. Sessions accumulate and remain listed as active after work is done
4. No option is available to close/terminate them

Expected behavior

Sessions can be explicitly closed or expire automatically when no longer in use.

Actual behavior

Multiple phantom sessions accumulate over time. They cannot be connected to
(attempting to connect fails) nor closed/removed from the interface.
There is no way to clean up stale sessions.

Additional context

There is no documented command to list or terminate remote control sessions
(e.g. claude remote-control --list / --close <session-id>).
A session management feature or /remote-control close command would resolve this.