Remote Control: Dispatch stuck on "Brewing..." - no response from spawn session (Windows 11)

Bug Description

claude remote-control shows "Connected" and "Attached" successfully, but Dispatch sessions from both the mobile app and browser (claude.ai/code) get stuck on "Brewing..." indefinitely. No response is ever received, and the command prompt shows no activity when messages are sent.

Environment

• OS: Windows 11 Home 10.0.26200
• Claude Code: 2.1.81
• Node.js: v24.14.0
• npm: 11.9.0
• Auth: OAuth (firstParty), logged in successfully

Steps to Reproduce

1. Run claude remote-control in Command Prompt (inside a git repo)
2. Select spawn mode: same-dir
3. Status shows: Connected, Capacity 1/32, Attached
4. Send a message from the Claude mobile app (Dispatch tab) or browser (claude.ai/code)
5. Message is marked as "read" on mobile
6. Response never comes - stuck on "Brewing..."
7. Command prompt shows zero activity

What I Tried

• Restarting claude remote-control multiple times
• Restarting the Claude desktop app (updated to v1.1.8359)
• Reinstalling Claude Code (npm install -g @anthropic-ai/claude-code)
• Adding Node.js to Windows Firewall allow rules
• Testing from both mobile app and browser - same result on both
• No proxy configured

Expected Behavior

Dispatch session should connect to the remote-control and execute the prompt.

Actual Behavior

Session stays in "Brewing..." state forever. The claude remote-control terminal shows no incoming session activity.