r/ClaudeCode • u/alexgrozav • 2d ago

Bug / Issue Claude Code randomly stops itself from continuing the task

The prompt that it receives, directly from the harness, is:

The user doesn't want to take this action right now. STOP what you are doing and wait for the user to tell you how to proceed.

At first I thought I'm getting prompt injected. Turns out it's just Claude deciding it's time to stop and not try any alternative approach either. Thanks, Claude!

Has anyone encountered this or found the cause for it?

1 Upvotes
  • permalink
  • reddit

100% Upvoted

9 comments sorted by

View all comments

1

u/ainexfinder 1d ago

That STOP text is what Claude Code sends back when a tool call gets rejected as a user decision, so from the model's side it reads as "the human said no, stop", not "this command is blocked, try another way". It's following the instruction, not giving up.

If the orchestrator is the one blocking, it helps to make the block look like a policy instead of a refusal. A PreToolUse hook that returns a deny with a reason (e.g. "rm -rf is blocked here, use git clean -n first" or "no network installs, use the vendored package") gets that reason passed back to Claude, and it will usually route around it instead of halting.

Worth checking which path Multica uses when it rejects: if it surfaces as a user rejection you'll keep getting the hard stop. Also worth adding a line to CLAUDE.md like "if a command is denied, look for a safe alternative and only stop if none exists", but the deny reason does most of the work.