AskUserQuestion auto-completes with empty answers in v2.1.104 (regression from v2.1.101)

Status Closed — not planned
Reported on v2.1.104
Maintainer reply None cached
Activity 5 comments · opened Apr 12, 2026 · closed May 23, 2026

Environment

  • Claude Code version: 2.1.104 (published 2026-04-12T02:26:22Z)
  • Previous working version: 2.1.101 (2026-04-10)
  • OS: Windows 11 Pro 10.0.26200
  • Permission mode: bypassPermissions
  • Context: AskUserQuestion called from within Skill tool (custom slash commands)

Description

AskUserQuestion tool returns immediately with empty answers ("User has answered your questions: .") without displaying the interactive question UI to the user. The model then proceeds as if the user answered, fabricating responses based on its own assumptions.

This worked correctly for months through v2.1.101. Broke on v2.1.104 (today's release).

Reproduction

  1. Set "defaultMode": "bypassPermissions" in .claude/settings.json
  2. Create a skill/command that calls AskUserQuestion with options
  3. Invoke the skill via the Skill tool
  4. AskUserQuestion returns instantly with no UI shown
  5. Tool result says "User has answered your questions: ." with empty answer content

Expected Behavior

AskUserQuestion should ALWAYS show the interactive UI and wait for user input, regardless of permission mode. This is an information-gathering tool, not a permission request.

Suspected Cause

v2.1.104 changelog mentions: "Tool calls require explicit approval if blocked by permission mode, preventing unintended external actions." This change likely altered the tool approval flow in a way that auto-completes AskUserQuestion before requiresUserInteraction() is checked.

Impact

High -- AskUserQuestion is foundational to interactive workflows (requirements elicitation, configuration, decision capture). With this bug, all interactive slash commands silently skip user input.

Related Issues

  • #29547 - AskUserQuestion empty in plugin skills
  • #29733 - AskUserQuestion completes without user input
  • #10400 - AskUserQuestion empty with bypassPermissions
  • #13439 - PreToolUse hooks cause empty responses

Workaround

Downgrade to v2.1.101: npm install -g @anthropic-ai/claude-code@2.1.101

View original on GitHub ↗

5 Comments

github-actions[bot] · 6 months ago

Found 3 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/29618
  2. https://github.com/anthropics/claude-code/issues/29530
  3. https://github.com/anthropics/claude-code/issues/30216

This issue will be automatically closed as a duplicate in 3 days.

  • If your issue is a duplicate, please close it and 👍 the existing issue instead
  • To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

pleb · 6 months ago

This may be related to issue #46654

github-actions[bot] · 4 months ago

Closing for now — inactive for too long. Please open a new issue if this is still relevant.

mbadge · 4 months ago

Requesting reopen — symptom confirmed in v2.1.143 with empirical evidence

This issue remains live. Analysis of 7 days of session logs from Claude Code v2.1.143 (Ubuntu 24.04.4 LTS, not bypassPermissions) reveals:

| Metric | Count |
|--------|-------|
| Total AskUserQuestion tool_use calls | 227 |
| Results with empty-answer responses | 54 (24%) |
| Dismissed by user | 12 |

Empty responses came in two forms:

  • v2.1.104 phrasing: "User has answered your questions: ." (27 occurrences)
  • Earlier phrasing: "Your questions have been answered: ." (27 occurrences)

The bug reproduces without bypassPermissions enabled, broadening the affected surface beyond the original report. OS coverage expands to Ubuntu (originally Windows 11).

Root cause indicator

Examining the v2.1.79 source (AskUserQuestion tool definition), the implementation has no internal timeout and is marked requiresUserInteraction:true. Empty results indicate the UI is resolving the deferred call with answers={} without rendering—matching the original symptom exactly. The bug is in the renderer/dismissal path, not the tool.

Related

This appears linked to #58750 ("on app quit, pending request silently resolves as 'Dismissed'") — same end state, likely same root cause.

---
(Reported via 7-day session-log scan)

github-actions[bot] · 2 months ago

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.