[BUG] Remote Control: Send button stuck as Stop/Interrupt button on Android. As a result, I cannot send first message from mobile

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

When connecting to a Remote Control session from the Claude Android app, the send button in the chat input area appears as a stop/interrupt button instead of the normal send button. This makes it impossible to send the first message from the mobile device because the session only becomes usable on mobile after a message is first sent from the desktop terminal.

The issue persists across -

Disconnecting and reconnecting to the same session
Starting a completely new Remote Control session
Force-closing and reopening the Claude Android app

The mobile client appears to initialize in a "generating/processing" UI state when connecting to a Remote Control session, even when the desktop session is idle and waiting for input. The button state never transitions to "ready for input" until it observes a completed request-response cycle initiated from the desktop side.

Environment Info -

Claude Code CLI version: 2.1.71 (latest as of 9th march, 2026)
Platform: Windows (native)
Terminal: PowerShell / CMD
Plan: Pro
Mobile device: Android
Claude Android app version: 1.260302.17
Connection method: Session list in Claude app Code tab

Additional Context -
I also checked related but distinct issues:

#28926 — Remote control infinite loading loop on mobile (different: that bug is about responses not rendering; this bug is about being unable to send the first message at all due to incorrect button state)
#29215 — Responses not visible on phone (different: that bug is about missing response display; this bug is about the input UI being stuck)

Impact -
This effectively makes Remote Control a monitor-then-type workflow rather than a true mobile-first workflow. Users cannot initiate work from their phone. They must always start at the desktop, which defeats the core use case of Remote Control (like starting a task from the couch or while commuting)

What Should Happen?

When connecting to an idle Remote Control session from the Android app, the send button should appear in its normal "send" state, allowing the user to compose and send the first message directly from mobile without needing to initiate from desktop first.

Error Messages/Logs

Steps to Reproduce

On desktop (Windows), start a Remote Control session:

claude remote-control

Open the Claude Android app
Navigate to the Code tab and connect to the active Remote Control session
Observe the input area at the bottom — the send button appears as a stop/interrupt icon (square/circle stop symbol)
Try to type and send a message — the button does not function as a send action
Workaround: Go back to the desktop terminal, send any message there, wait for the response to complete
Return to the Android app — the send button now appears correctly and messages can be sent from mobile

Claude Model

Opus

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

2.1.71

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

_No response_