[BUG] Claude Code Web - Failed Request Remains "Stuck" at Bottom of the Interface w/ Retry Connection Button
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?
A failed request on CC Web resulted in, initially, a perma-loading state where the UI read "Starting Claude Code" and no response was ever received (initially appeared like a standard hanging request).
After waiting and refreshing the page, the prompt from the failed request was still in the same position on the bottom of the screen. I was able to continue using the web app but the aforementioned prompt remained and the "Retry Connection" button would not disappear.
I continued using the web app for another 30-60 minutes and neither the message/prompt or the Retry Connection button has disappeared and the UI makes it appear as though the request is being processed.
See the screenshots in the Additional Information section.
And before someone yells at me, I asked where the appropriate place to report an issue was:
<img width="876" height="602" alt="Image" src="https://github.com/user-attachments/assets/56e5acc5-9948-424b-a612-f536611d0633" />
So there could be two bugs here
What Should Happen?
It's difficult to say exactly what should be done here. Allowing for the removal of a failed request's prompt would make sense in the context of Claude Code web. Hiding the Retry Connection button after multiple refreshes also feels appropriate. Never had anything like this occur in the CLI version of the app.
Error Messages/Logs
Steps to Reproduce
https://claude.ai/code/session_011CUqiyq2ieAay6Xkmoz7us
If you are able to access this session, presumably, you should be able to refresh the page and see the issue persist. I am sorry the steps to reproduce are not more cut-and-dry or helpful. I am happy to provide whatever additional information that might be needed to address the issue. Happy to help in any way I can.
Claude Model
Sonnet (default)
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
Claude Code Web
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Other
Additional Information
GIFs of Issue In Action:
!Image
14 Comments
Found 2 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
This appears to be a potential duplicate although I was unable to find the duplicate issues through a search of the repo's open issues. Seems to have overlap with the following open issues:
https://github.com/anthropics/claude-code/issues/11093
https://github.com/anthropics/claude-code/issues/11018
It also does appear to be consuming credits as was reported in #11018.
Other errors from the console include:
(This being an error that I have seen very commonly occurring in React code generated by Claude Code in other contexts)
&
It is unclear which of these are contributing to the errant state.
@bogini please add the claude-code-web tag to this bug as well so that is sorts easy when searching closed issues. Thanks!
@claude @camolechowski This is not fixed and should be reopened until it is.
<img width="1187" height="102" alt="Image" src="https://github.com/user-attachments/assets/2dd9a00c-9f5e-4e04-9c80-a33f8b99944c" />
That pic has the same timestamp as this comment.
After starting an entirely new session and only a few minutes work:
<img width="1085" height="138" alt="Image" src="https://github.com/user-attachments/assets/4f25bc4d-51ed-4dfa-a14c-7c760a0f5b61" />
At this point if Anthropic handed me
$1,000,000,000in credit to use Claude Code Web, I would not give it serious thought. The UI is so brittle as to be practically useless. It is alpha material at best. Now, on the other hand, if Anthropic wants to offer $$$ credit to my business Claude account which can be used with other Claudes in exchange for me to keep hammering Claude Code Web, I'm all for that. Until then or until they get serious about this, I'm not using Claude Code Web. Sorry. Claude-Code is a fantastic product BTW.Probably not helpful - but - I have/had the same issue. I found if I started a new session, it would work again. Sometimes the session can go for a day before freezing, sometimes less than five minutes, but each time starting a new session, as painful as that can be, got things going again. Please, don't shoot the messenger!
That matches my experience as well. Unfortunately this issue makes Claude Code Web impossible to run in our workflow. The loss of large conversation context often requires more time to recover from than the benefit of a web accessible UI. So until Anthropic gets its act together on CCW, we'll just stick with running multiple Claude-Codes.
One other note: CCW is a tremendous idea and has great potential.
CC on Web seems too early at this point. The ideai is fantastics, but regular hung up without a reliable way to simply try again is frustrating and right now, CC on Web is just a huge waste of time.
The idea of Claude Code web is good, but the web app is broken. If I see “Retry connection” again and can't get out of the loop, I'm not going to pay for this.
Got the same "bug".
I don't know if it's a real bug or a hidden rate limit, either way it's terrible for the claude code web feature showcase...
I think more it's a bug. If you go back to the main prompt window you can continue, but will need to outline the work you want done in a little more detail.
I am definitely still encountering the same variant of this issue. @cnighswonger I believe the primary issue for this bug is now being tracked on https://github.com/anthropics/claude-code/issues/10343 - this is why the ticket was closed as a duplicated, might have accidentally just closed it as completed.
Sometimes pressing the Interrupt button under the Open in CLI button helps to awaken Cloude Code.
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.