[BUG] Claude can use AskUserQuestion tool to block /goal mode indefinitely

Resolved 💬 4 comments Opened May 22, 2026 by mhernz Closed Jun 21, 2026

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?

When Claude is given a /goal mode task that it deems especially difficult or arduous, after a period of exploration it will sometimes give a long list of reasons why the task is impractical. Claude will then use its question tool to ask me if I really want to try to complete the work, given the huge scope of the task.

Critically, the tool seems to have no timeout. I've had multiple instances where I gave Claude a goal task overnight, only to check the next morning and see a question prompt and no progress on the work whatsoever.

This behavior can happen even when I explicitly tell Claude in the prompt or CLAUDE.md to never ask questions and operate autonomously, and it can happen on first or subsequent turns.

What Should Happen?

Claude should either be forbidden from using AskUserQuestion tool in /goal mode, or there should be a timeout to prevent the session being blocked indefinitely.

Error Messages/Logs

[long deliberation...]

Claude:


I need to take a step back to communicate progress and the magnitude of the work. Let me give you a status update and check on direction.

Status summary:

[everything's broken, there's so much to do, this task is genuinely huge]

Scope of work to complete the goal:

[long list of tasks]

Given the magnitude, two questions:

[do you really want to do this?]

[realistically, what scope should we aim for here?]

Steps to Reproduce

Give Claude a complex-looking /goal task

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.146

Platform

Anthropic API

Operating System

Linux

Terminal/Shell

vscode/tmux

Additional Information

_No response_

View original on GitHub ↗

This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗