[Feature Request] Make interactive question timeout configurable or remove 60s hard limit
Status Fixed / completed
Reported on v2.1.198
Maintainer reply ✓ Yes — bcherny
Activity 3 comments · opened Jul 2, 2026 · closed Aug 17, 2026
💡 Likely answer: A maintainer (bcherny, collaborator)
responded on this thread — see the highlighted reply below.
Bug Description
Interactive question timeout of 60s is unnecessary complexity and doesnot work well with multiple terminals of different kinds of work running. Where, I might come back to an agent ready with questions was a normal flow, now it just decides I am not available and stops abruptly. It is a regression on a perfectly working harness for me.
Environment Info
- Platform: darwin
- Terminal: vscode
- Version: 2.1.198
- Feedback ID: 8c274b7e-a943-4909-afeb-f680d32416e1
Errors
[]
3 Comments
I completely agree. None of my assignments received any (and therefore incorrect) answers. It's impossible to work like this!
Good news — this shipped in v2.1.200:
AskUserQuestiondialogs no longer auto-continue by default. Questions now wait until you answer them.If you do want an idle timeout, it's opt-in: run
/config→ Question auto-continue timeout, or setaskUserQuestionTimeoutin your user settings to"60s","5m","10m", or"never"(the default). Please update to the latest version if you're still seeing the 60s auto-continue.Changelog: https://github.com/anthropics/claude-code/blob/main/CHANGELOG.md
Settings docs: https://code.claude.com/docs/en/settings#available-settings
🤖 Generated with Claude Code
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.