What this error means
AskUserQuestion fallback on tool denial removed — model must figure out why tool was denied on its own; silent failures in autonomous coding sessions is a Claude Code failure pattern reported for developers trying to fix claude code tools silently failing after denied by permission model without explaining why or asking for clarification; resolve broken agent workflow due to prompt change. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.
Why this happens
Source: Reddit r/ClaudeCode deep analysis of system prompt delta between CC ~2.1.70 (March 2026) and CC ~2.1.117 (April 2026). Key delta: '# System' section lost 'If you do not understand why the user has denied the tool call, use the AskUserQuestion to ask them'. Previously Claude triggered AskUserQuestion on tool denial; now it self-diagnoses, causing silent failures in CI-like autonomous sessions. 43 upvotes, 22 comments as of 25 days ago. Mapping: per approved mappings, Claude Code → AI Coding Tools.
Common causes
- Source: Reddit r/ClaudeCode deep analysis of system prompt delta between CC ~2.1.70 (March 2026) and CC ~2.1.117 (April 2026). Key delta: '# System' section lost 'If you do not understand why the user has denied the tool call, use the AskUserQuestion to ask them'. Previously Claude triggered AskUserQuestion on tool denial; now it self-diagnoses, causing silent failures in CI-like autonomous sessions. 43 upvotes, 22 comments as of 25 days ago. Mapping: per approved mappings, Claude Code → AI Coding Tools.
Quick fixes
- Confirm the exact error signature matches
AskUserQuestion fallback on tool denial removed — model must figure out why tool was denied on its own; silent failures in autonomous coding sessions. - Check the Claude Code account, local tool state, and provider configuration involved in the failing workflow.
- Compare the failing environment with a known working setup, then change one configuration value at a time.
Platform/tool-specific checks
- Verify the command, editor, extension, or API client that produced the error.
- Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
- Avoid deleting credentials, local model data, or project settings until the failing scope is clear.
Step-by-step troubleshooting
- Capture the exact error message and the command, editor action, or request that triggered it.
- Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
- Review the source evidence below and compare it with your environment.
- Apply one change at a time and rerun the smallest failing action.
- Keep the working fix documented for the team or deployment environment.
How to prevent it
- Keep provider/tool configuration documented.
- Record non-secret diagnostics such as tool version, provider name, model name, and command path.
- Add a lightweight check before CI or production workflows depend on the tool.