[BUG] DISABLE 60s question auto-resolving??
Status Fixed / completed
Reported on v2.1.198
Maintainer reply ✓ Yes — bcherny
Activity 4 comments · opened Jul 2, 2026 · closed Aug 16, 2026
💡 Likely answer: A maintainer (bcherny, collaborator)
responded on this thread — see the highlighted reply below.
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?
60S QUESTIONS AUTO RESOLVE
not configurable, not able to opt-out, insane
<img width="1173" height="275" alt="Image" src="https://github.com/user-attachments/assets/f60d7903-5ed0-46b5-9cd1-a98cd09fca04" />
What Should Happen?
REMOVE THE F#%^@NG 60S QUESTIONS AUTO RESOLVE ARE YOU INSANE OR WHAT? This absolutely spoils the whole multi-terminal half-bg workflow where I leave separate tracks to be worked on until something needs my attention. AND QUESTION IS A PAUSE THAT NEEDS MY ATTENTION. That's a crazy change to ship, should fire that guy who came up with this sh*t.
Error Messages/Logs
Steps to Reproduce
use claude code.
Claude Model
None
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
2.1.198
Platform
Anthropic API
Operating System
Ubuntu/Debian Linux
Terminal/Shell
Other
Additional Information
_No response_
Showing cached comments. Read the full discussion on GitHub ↗
3 Comments
Dup of #73125
Thanks for the report — this was changed in 2.1.200, shortly after the version you were on (2.1.198).
In 2.1.198 and 2.1.199 an unanswered
AskUserQuestiondialog auto-continued after 60 seconds of idle. Since 2.1.200 that is off by default: questions wait until you answer them. If you ever want the timeout, it's opt-in via/config→ "Question auto-continue timeout" (settingaskUserQuestionTimeout:60s,5m,10m, ornever).Changelog: https://github.com/anthropics/claude-code/blob/main/CHANGELOG.md (see 2.1.200). Docs: https://code.claude.com/docs/en/settings#available-settings
I checked the current release (2.1.233) and the setting is present with the default
never. Closing as fixed — if you're on 2.1.200 or later and still see a question auto-resolve without having set that option, reply with your version andclaude doctoroutput and we'll reopen.🤖 Generated with Claude Code
This was changed in v2.1.200: questions no longer auto-continue by default and stay open until you answer. If you ever want the timeout, it's opt-in through the
askUserQuestionTimeoutsetting (Question auto-continue timeout in/config). Please update to v2.1.200 or later.🤖 Generated with Claude Code