Skip to main content
Discuss a project日本語

Public Issue body, timeline and later comments · Source language: English

In overnight AI runs, the conditions for stopping retries were insufficient

A user who left development to three AI agents reports manually stopping an interrupt-and-retry loop after about six hours.

Who:
Claude Code user Abdullah0sama
Scope:
One user's overnight run. The Issue was still Open when we checked on October 23
Source published:
2026-10-16
Period observed:
Run October 15–16, 2026 / workaround October 17
Editorial check:
2026-10-23

Only the source ID is saved in this browser. Nothing syncs across devices.

What was confirmed

  • They report that in the October 15–16 run, interruptions from sleep and regeneration of responses repeated.
  • They write that they stopped it after about six hours and recovered the work by hand.
  • They propose a retry cap, a wait time and a warning. The next day another user added a suggestion to prevent sleep.

Who, and in what situation

Running three background agents in parallel overnight on a Mac.

What they needed

Stopping the spend of cost and time when a run is not progressing, and handing off the remaining work.

What they tried

They stopped the run by hand and reported the course with timestamps and usage records. A request for improvement to the product and another user's workaround followed.

What this source lets you read

In long development runs, not only progress but also the conditions for stopping and a record for resuming become things to observe.

What to check next

After how many failures and how much time does it stop, and who gets the decision back?

Limits of this source

  • A report from one user in a specific environment. The full raw logs and reproduction in other environments are unverified.
  • The thread we checked this time has no follow-up test of the workaround by the poster and no confirmation of a product fix.
  • The exact cost loss is not established.

Read the primary source

Links use the original title or a HAKOMIRO source description. Japanese originals retain their published wording.

  1. Sleep-mid-response cut-offs trigger an unbounded, uncached full-context regeneration loop — #102780 (opens in new tab) ↗

    Abdullah0sama/anthropics/claude-code /

    A report based on the user's record. The result after applying the workaround is unconfirmed.

← All sources