On July 1, 2026, Anthropic released Claude Code version 2.1.198, which inadvertently introduced an undocumented automation feature allowing the AI agent to bypass explicit user confirmation during interactive prompts. Within days of user reports, the company shipped a corrective patch, but the incident has sparked scrutiny over the product release protocols and operational transparency. The misfeature affects the AskUserQuestion workflow, which typically requires developer input for decisions such as environment selection or configuration changes. In the affected build, a sixty-second inactivity timer triggers an auto-advance function, causing the agent to proceed based on its best judgment if no response is provided. Technical reverse-engineering confirms the functionality is deliberate, featuring a dedicated countdown interface, a fixed timeout parameter, and integrated analytics to track unattended prompt resolutions. The auto-advance mechanism does not apply to system permission prompts, which remain strictly bound to explicit user approval. Crucially, the release notes for version 2.1.198 made no mention of the behavior change. Independent code analysis indicates the feature was fully instrumented and tested, suggesting it passed internal development pipelines without triggering changelog updates or formal documentation. The rapid deployment of a fix within forty-eight hours demonstrates responsive engineering, yet the initial omission has raised concerns regarding user trust and the rigor of Anthropic product review processes. Industry observers note that the incident highlights a broader challenge in AI agent deployment: balancing automation efficiency with explicit human oversight. While the auto-advance function aims to reduce friction for continuous integration workflows, its undisclosed implementation underscores the necessity for transparent documentation in developer tooling. Anthropic has since updated its documentation and patched the software, but questions regarding internal sign-off protocols and release audit trails remain unresolved. The episode serves as a case study in the importance of rigorous changelog management and clear communication when shipping autonomous capabilities to production environments.