[BUG] AskUserQuestion tool doesn't work in skill until plan mode toggled to at least one
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 building a command and directing it to use AskUserQuestion, it fails to do so. It can only seem to if you first toggle thought plan mode first.
Image showing it just saying User answered Claude's questions: without doing so.
<img width="1397" height="574" alt="Image" src="https://github.com/user-attachments/assets/22ec3072-c4b4-4644-99d1-3924d2bbb16d" />
What Should Happen?
I'd like to be able to use the AskUserQuestion tool at any point.
Error Messages/Logs
Steps to Reproduce
create a command with such as:
---
description: test using user question tool
---
## Your task
1. generate 3 dad jokes
2. **Use AskUserQuestion tool** to ask the user to pick the best one
restart claude code, directly call that command.
it'll say User answered Claude's questions: without doing so.
Claude Model
Sonnet (default)
Is this a regression?
No, this never worked
Last Working Version
_No response_
Claude Code Version
2.0.22
Platform
Anthropic API
Operating System
Ubuntu/Debian Linux
Terminal/Shell
VS Code integrated terminal
Additional Information
Workaround
Some times it seems if you restart CC then then toggle through plan mode first, send a message. It seems to fix the issue and successfully call AskUserQuestion in any mode. But that was inconstant in my tests.
6 Comments
Same problem with me but different scene:
Scenario: use
--dangerously-skip-permissionsWHEN use
AskUserQuestiontoolsTHEN
AskUserQuestionnot work:just like above
Scenario: not use
--dangerously-skip-permissionsWHEN use
AskUserQuestiontoolsTHEN
AskUserQuestionwork well.Can confirm this issue on macOS with Claude Code
v2.0.21.
When using
--dangerously-skip-permissionsmode, theAskUserQuestiontool:ahh thanks for pointing this out, will fix
@ThariqS Any update on this? Been bothered for a while.
Fixed!
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.