[FEATURE] Allow disabling Remote Control mid-session without terminating the session

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

When Remote Control is activated mid-session via /remote-control or /rc, there is no way to deactivate it without terminating the entire session. The activation is one-way: you can turn it on, but you can't turn it off.
This is a problem because:

Security hygiene: A user may want to temporarily enable Remote Control to handle something from their phone, then revoke remote access once they're back at their desk — without losing conversation history and context.
Principle of least privilege: Keeping a remote access channel open longer than needed increases the attack surface unnecessarily. The session URL grants full control of the Claude session to anyone who has it.
Workflow flexibility: Users who start sessions with --remote-control or have "Enable Remote Control for all sessions" turned on currently have no way to selectively close the remote bridge for a given session while continuing to work locally.

Related but distinct from #28917, which asks for revoking links from already-terminated sessions. This request is about revoking remote access on a live, ongoing session.

Proposed Solution

Expected Behavior
A slash command (e.g., /stop-remote-control or /stop-rc) that:

Tears down the remote bridge and invalidates the session URL/QR code
Keeps the local interactive session running with full conversation history intact
Allows re-enabling Remote Control later via /rc if needed (issuing a new URL)

Alternative Solutions

Alternatives Considered

Terminating and restarting the session: loses conversation context and is disruptive mid-task.
Using --resume after restarting: partial workaround, but still interrupts flow and any in-progress work.

Priority

Medium - Would be very helpful

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

_No response_