Remote control sessions not released when archiving conversations in Claude app

Description

When using the Claude app (desktop/web) connected to Claude Code via remote MCP, there is a 32 concurrent session limit. Archiving or stopping a conversation in the app does not terminate the underlying remote Claude Code session, meaning slots are consumed indefinitely with no way for the user to free them from the client side.

Steps to reproduce

1. Connect to Claude Code via remote MCP from the Claude app
2. Have a conversation (consumes a session slot)
3. Archive the conversation (the only available option)
4. Observe that the remote session slot is still occupied

Expected behavior

• Closing or archiving a conversation should release the remote session
• Or: provide an explicit "disconnect" button to terminate the remote session from the client

Actual behavior

Archived conversations continue to hold remote session slots, eventually exhausting the 32-session limit with no client-side way to reclaim them.

Impact

Users are locked out of creating new remote sessions once the limit is reached, with no self-service way to recover without server-side intervention (manually killing processes).