[BUG] Can't submit prompt without stopping on mobile browser Claude code
Status Closed — not planned
Maintainer reply None cached
Activity 10 comments · opened Apr 26, 2026 · closed Jul 16, 2026
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?
On the browser version of claude code, I can't submit a new prompt without first stopping the execution of my currently running prompt.
What Should Happen?
I should always have a send/submit button.
Error Messages/Logs
Steps to Reproduce
- use the browser version of Claude code
- Write a prompt that requires a lot of thinking and writing
- while it's thinking and working, write a new prompt and try to submit it without stopping the current execution
Claude Model
Not sure / Multiple models
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
latest
Platform
Other
Operating System
Other
Terminal/Shell
Other
Additional Information
suggested UX experience is to move the stop button next to the pulsing anthropic logo and timer because that's the more contextual place to place the stop button.
that way, the text area input always has the consistent send button
10 Comments
suggested UX experience is to move the stop button next to the pulsing anthropic logo and timer because that's the more contextual place to place the stop button.
that way, the text area input always has the consistent send button
please fix this
that bug is unrelated to this
@omid-ant , you were an awesome help with my other Claude Code Web mobile issue, can you assist here?
One of the joys of Claude code is that I can send prompts while it's already thinking and working to better guide the path it takes while it shares what it's thinking. Without that ability, it's a poor experience 😔
please fix @claude
this is still an issue! please fix this!!!!
@omid-ant please!!!
Closing for now — inactive for too long. Please open a new issue if this is still relevant.
fyi, this has been resolved.