[BUG] Session stuck

Found 3 possible duplicate issues:

1. https://github.com/anthropics/claude-code/issues/11018
2. https://github.com/anthropics/claude-code/issues/10995
3. https://github.com/anthropics/claude-code/issues/10343

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

Maybe because session is long

It happens when session becomes too long. It stops responding. In the beginning page refresh works but not for long.
Just open new session and it continues. Not the solution but helps until I spend $250.

I'm seeing this happen a lot. It hangs on any browser I've tried (Firefox, Edge, mobile Edge, etc).

+1 I have the same issue

Is this the same as #10343 ?
I think I'm having this issue too.

two of my repos are stuck like this.

I just noticed I could re-vive an archived session. I found the oldest archived session on my stuck repo, and I was able to send it a message and it responded! I'm going to keep playing with it to see if I can "jostle it loose" somehow to begin accepting new sessions.

So I left the oldest conversation, and tried to start a new one, and got the same thing. It just tried to spin up and then was stuck in the usual way.

I went BACK to the oldest conversation, and NONE of our new conversation was displayed, but what was displayed was this:

<img width="1200" height="654" alt="Image" src="https://github.com/user-attachments/assets/3bd86d32-e4df-4b3c-a90c-802dd1aa35b3" />

The last of the 3 commands has a pulsing grey circle and appears to still be running.

The conversation is still active, I'm able to keep interacting with Claude here.

🤦🏻 Claude and I may have coded ourselves into this problem:

The Prime Suspect: SessionStart Hook

File: .claude/settings.local.json
Added: December 22, 2025 (commit aabb....)

 "hooks": {
   "SessionStart": [{
     "hooks": [{
       "type": "command",
       "command": "bash ./scripts/setup-gradle-proxy.sh",
       "timeout": 30,
       "statusMessage": "Setting up Gradle proxy..."
     }]
   }]
 }

I think Claude helped me set this up in an "on the web" session, and thus we hoisted ourselves on our own petard.

Petard status: unhoisted, by disabling this whole setting. I dunno if the script is broken, or just anything in SessionStart hooks is bad on the web or what. But - glad to have uncovered the problem now.

Closing for now — inactive for too long. Please open a new issue if this is still relevant.

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.