Anthropic's Claude-Code system continued processing prompts without providing responses after a 60-second timeout period [1].
This behavior indicates a potential failure in the system's timeout mechanisms, which are designed to prevent infinite loops and resource waste. If an AI continues to execute a prompt without delivering an output, it may lead to unexpected system behavior or inefficient compute usage.
According to a report filed in a GitHub issue, the system failed to trigger a stop or an error message when the expected response time was exceeded [1]. A user said, "It just kept running without an answer" [2].
Technical documentation suggests that the process remained active despite the lack of a visible result. A developer said, "the system continued to execute the prompt after a timeout" [3].
While the specific cause of the processing loop was not explicitly stated in the report, the incident highlights the complexities of managing real-time AI execution. The 60-second threshold [1] is a standard benchmark for many API responses, but the failure to terminate the process suggests a disconnect between the execution layer and the response handler.
Anthropic has not yet provided a detailed explanation for why the system continued to run. The issue remains a point of discussion among developers utilizing the Claude-Code tool for software engineering tasks.
“"It just kept running without an answer."”
This incident underscores a critical challenge in AI reliability: the 'silent failure.' When a system continues to consume computational resources without producing an output, it creates a blind spot for developers and users. Ensuring that timeout protocols strictly terminate processes is essential for the stability of autonomous coding agents.
