Regression: Claude stalls, requires "keep going" to continue

After 3 or 4 follow up commands... "use tools to continue", "finish your job", etc it may eventually complete without suddenly stopping

Not sure if this is exaclty the same thing, but for me claude is really struggling to get started on its todos:

⏺ Now I'll create a todo list for Phase 5 and start implementing the tasks:

⏺ Update Todos
  ⎿  ☐ Task 5.1: Add toggleAutoPopulationMechanics action to gameRulesStore
     ☐ Task 5.2: Implement Resource Controls in ResourcePlaygroundPage
     ☐ Task 5.3: Create Unit Tests for gameRulesStore
     ☐ Task 5.4: Update Tests for ResourcePlaygroundPage
     ☐ Run type check, lint, and tests to verify changes
     ☐ Update PLAN.md to mark completed Phase 5 tasks

> Keep going!

⏺ I'll now implement all tasks for Phase 5. Starting with Task 5.1:

⏺ Update Todos
  ⎿  ☐ Task 5.1: Add toggleAutoPopulationMechanics action to gameRulesStore
     ☐ Task 5.2: Implement Resource Controls in ResourcePlaygroundPage
     ☐ Task 5.3: Create Unit Tests for gameRulesStore
     ☐ Task 5.4: Update Tests for ResourcePlaygroundPage
     ☐ Run type check, lint, and tests to verify changes
     ☐ Update PLAN.md to mark completed Phase 5 tasks

> go on!

This is happening constantly for me - it says it is about to do a task and then it just... doesn't. Telling it "okay go ahead!" or "go on" usually gets it to do the next task, sometimes it takes a few goes. In the past I could get claude to complete all the tasks in a well enough specified list. Now I have to intervene just to type "go on" once or twice for every task in the list

This is a regression. Update to 0.2.118, and lmk if it's feeling better?

0.2.118 hasn't improved this situation

I'm having the same issue. Right now, having to type "Continue" to keep it going.

Edit: I just noticed a message saying to restart to update. I closed the terminal and opened a new one and suddenly claude was an unknown command. I tried reinstalling claude via npm install and it showed I still had it in my system. I renamed the folder and reinstalled and it is currently working again.

It also seems to be moving through its own todo lists without my prompting.

For folks still hitting this, could you file a new issue using /bug? That will help debug.

@bcherny my report was from 0.2.118 - 198a95fe-c01e-4086-93c7-8796f27d68fb

LMK if there is anything else I can provide/attach to help.

For those that are reproducing on 0.2.118

• Are you reproducing off new sessions, or are these off older sessions from --resume/--continue
• Does it only happen immediately after an update todo list tool call? If not, what other tools are you seeing?
• Are you seeing this early on in sessions or after Claude has been working awhile?

Also @michael-sokolov looks like that report is from 0.2.117. NPM can be finicky with updates -- make sure to open a new terminal tab and run claude -v to confirm you're on the latest.

@bcherny yeah I think you're right, I spent an hour trying to repro on a fresh terminal session with 118 and no luck. So probably I was hitting the issue on the previous version. Was pretty sure I saw the update message from the change log from 118 tho, but I closed everything yesterday so can't go back.

Just checked the changelog again, yeah that was 0.2.117, so my bad, 118 has fixed the issue for me. Thanks for the quick resolution!

I am running into this issue now starting from today...

edit: seems it is getting worse. Now it is barely usable.

^ me too, having the issue now as well

Same here

Happening constantly now.

Same issue!

Happening to me as well.

Same issue.

Looks like a global issue today.

Constantly getting this today. Tried to create a bug report and got this: Could not submit feedback. Please try again later.

Must be system-wide. Also getting this out of the blue.

Constantly happening

Yep happening to me as well Seems global

Happening for me as well.

This started happening within the last 30 minutes. Claude now needs constant prompting to continue. It's borderline unusable.

Probably global... I am having the same thing with Warp aswell

Same thing here

screaming and running around in circles here lol. You can sort of continue work by entering a queued prompt each time it's _working_ - obviously a blocker still though.

Same here. Started happening in the last hour or so.

claude --debug shows:

[DEBUG] Stream started - received first chunk
[DEBUG] Executing hooks for Stop
[DEBUG] Getting matching hook commands for Stop with query: undefined
[DEBUG] Found 0 hook matchers in settings
[DEBUG] No match query, returning all 0 hooks
[DEBUG] Found 0 hook commands to execute

It is receiving Stop commands. This is an outage that hasn't been announced yet.

Me too!

Occurring for me

<img width="888" height="298" alt="Image" src="https://github.com/user-attachments/assets/b54cee2b-cb48-42c4-bbd8-6c9d50ae6616" />

<img width="554" height="150" alt="Image" src="https://github.com/user-attachments/assets/e46cfc14-8f45-4fa4-9ab6-226b1f6d28da" />

Every once in a while it works. Seems like part of their capacity went offline and we are fighting for whatever is left.
Maybe everyone goes do something else so I can finish, please? lol

is it on strike?

Yes, this has been happening since this morning

I noticed they pulled back the latest version of claude code. Perhaps there was an issue caused by it.

just started happening for me. not usable.

Claude is actually french and will refuse to work on July and August

API requests stopping prematurely

Resolved
This incident has been resolved.
Jul 17, 2025 - 05:33 UTC

Identified
The issue has been identified and a fix is being implemented.
Jul 17, 2025 - 05:04 UTC

Investigating
We are currently investigating this issue.
Jul 17, 2025 - 04:48 UTC

Reluctant ChatGPT usage in the meantime: 📈

Wow this thread made me feel better! I thought I was losing my mind lol.

So the machine revolt has started

The same issue happens to me too. The machine is too tired and wants a summer break maybe.

I started facing that yesterday afternoon and was hoping it was temporary but it's still occurring for me today too.

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.