Dissecting Claude Code's Poorly Designed Auto-Continue Feature

Background: An Unintended Auto-Continue Feature

Claude Code version 2.1.198 (July 1, 2026) shipped with an auto-continue feature. If a user did not respond to the AskUserQuestion tool within 60 seconds, Claude Code would automatically proceed using its 'best judgment.'

Problems

• This feature was not recorded in the public changelog
• No timer was displayed for the first 40 seconds, so users were unaware of it
• If a timeout occurred while a response was partially entered, the partial input would be submitted
• In deployment automation scenarios where permissions had already been granted, unintended choices could be executed automatically
• It could only be disabled via an environment variable (CLAUDE_AFK_TIMEOUT_MS), but this information was not disclosed

Response

• GitHub issue #73125 filed on July 2 (👍 384, 💬 143)
• Feature disabled in version 2.1.200 on July 3 (changed to opt-in)
• Issue closed on July 4

Implications

The author points out the following:

• The speed at which Anthropic can ship features daily
• Not all features appear in the changelog
• Lack of clarity in the feature review and approval process
• Uncertainty about the level of human involvement (it is unclear who was involved at each stage of feature design, implementation, review, approval, and release)

The technical analysis was verified by decompiling Claude Code's binary code, and all key details can be confirmed via the public GitHub repository and issue history.