[BUG] Remote Control: Stop/Send share one button — UI lag turns "send" taps into Stop
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?
Remote Control (Claude app): Stop/Send share one button, causing accidental interrupts. When a tool starts running, the Send button turns into Stop. If the UI lags, a tap intended as "send message" lands on "Stop" and interrupts the running command mid-way (it happened three times in one session, once leaving a half-finished data migration). Suggestion: put Stop and Send in separate positions (Stop left, Send right).
What Should Happen?
Tapping Send while a tool is running should only queue or steer the message. It should never interrupt the running command. Stop should be a separate, deliberate action:
Separate controls: Stop and Send in fixed, separate positions (e.g. Stop on the left, Send on the right), so a lagging button change can't turn one into the other.
No accidental stops: Stop should only act on the state shown when the tap began. If it switched from Send in the last moment, treat the tap as Send.
Partial work is visible: if a tool does get interrupted, say clearly that it was stopped by the user mid-run, so partial side effects aren't mistaken for a rejected command.
Error Messages/Logs
Steps to Reproduce
On a Mac, run claude remote-control (here: Claude Code 2.1.292, --permission-mode bypassPermissions), and connect from the Claude app on a phone.
Ask Claude to do something that runs a long shell command, e.g. a loop that takes 30+ seconds.
While the command is starting (the moment the Send button changes to Stop), type a short follow-up message and tap Send.
Observed: the button had already turned into Stop but the screen hadn't caught up, so the tap stops the running command. Claude receives "The user doesn't want to proceed with this tool use… [Request interrupted by user for tool use]" followed by the message, and the command is left half-finished. In my case a data migration had already written 14 of 23 entries.
Expected: the message is queued or delivered mid-turn, as it is when sent while Claude is between commands, and the command keeps running.
Happens intermittently, most often right after a command starts. Seen 3 times in one session on 7 Oct 2026.
Claude Model
None
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
2.1.292 (Claude Code)
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Terminal.app (macOS)
Additional Information
_No response_