[BUG] Remote Control: Terminal input ignored while remote-control session is active

Description

When a claude remote-control session is active in a terminal, typing into that terminal has no effect — keystrokes are swallowed and pressing Enter clears the input without sending it. The only way to interact is through the remote connection (claude.ai/code).

This is a regression — terminal input previously worked concurrently with remote connections in earlier versions.

Expected Behavior

The terminal running claude remote-control should accept local keyboard input alongside remote input from claude.ai/code, allowing the user to interact from either interface.

Actual Behavior

• Text typed into the terminal appears briefly, then clears on Enter
• No input is sent to the session
• Remote input (via claude.ai/code) works correctly
• The terminal correctly displays conversation updates from remote input, so rendering works — only local input is broken

Reproduction Steps

1. Start a remote-control session:

``
claude remote-control --name "Test" --spawn same-dir --permission-mode default --capacity 4
``

1. Connect to the session via claude.ai/code (session appears and works)
2. In the original terminal where claude remote-control is running, try typing a message and pressing Enter
3. Observe: text clears, nothing is sent

Workaround

Open a separate terminal and run a regular claude session. The remote-control terminal remains display-only.

Environment

• OS: Windows 11 Home 10.0.26200
• Claude Code version: 2.1.76
• Node.js: v22.22.0
• Shell: Git Bash (MINGW64) and PowerShell — same behavior in both
• Launch method: Both direct CLI and via PowerShell script (Start-Process) exhibit the same behavior

Related

• #28771 — Same issue, closed by bot for insufficient detail