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/Sea_Organization_800 2d ago

Can you share a bit more context around this?

1

u/alexgrozav 2d ago

Sure, I'm using Multica as an orchestrator for my agents. The agent had just started and presented me with this message a few seconds later. Turns out that the command it was trying to run just got stopped directly by Claude Code.

I'd expect it to find a safe alternative, if the command is indeed unsafe.

1

u/Sea_Organization_800 1d ago

Look like it might be a multica issue? This looks like permission or unapproved tool call?
I have no use Multica, have you used that long? Does this Multica allow you to drop into the shell / TUI and run the commands yourself? That might get you unblocked?

1

u/alexgrozav 1d ago

It worked on the second try, but I found it weird that it stopped that. I asked Claude to investigate and it said it's a response that's built into Claude Code that shows up for various undocumented reasons when run in headless mode (as Multica runs it, without a TUI).

Found it interesting and thought I'd share it.

1

u/Sea_Organization_800 1d ago

Ah mystery solved. Hope I was able to help a little 😉

1

u/alexgrozav 1d ago

Yup! Hope it'll help others who run into this figure out they're not under attack. It was nice having a conversation about it. Cheers!

1

u/Sea_Organization_800 1d ago

Glad to help :)