4 people reported
All time, since Oct 15.
Sleep re-sends full agent context
“Bug: Sleep-mid-response cut-offs trigger an unbounded, uncached full-context regeneration loop”
Is this your bug? What gets counted gets fixed. Pile on.
Paste this into your agent. It files your report, with your error and version.
I hit this bug: rapsheet.dev/sheets/claude-code/issues/12925/file Follow it to file my report. Show me the text before you send.
No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends
Sleep and wake cycles re-send full agent context uncached. Background agents left running overnight on macOS re-write their whole context into the cache after every wake-up, draining usage limits.
Is this your bug?
File my report- Where
- background agents
- Error text
API Error: Your computer went to sleep mid-response- Versions
- 2.1.295 to 2.1.302
- Platforms
- macOS
- How bad
- Breaks a normal workflow.
Part of: Prompt cache misses and re-writes11 bugs
- Interactive sessions get 5m cache TTL18 people
- Warm prompt cache fully missed2 people
- Resume re-writes prompt cache3 people
- CLAUDE.md cache not shared3 people
- Cross-session prompt cache misses2 people
- Prompt cache misses after system message3 people
- Subagent prompt cache expires2 people
- Background agent summary requests12 people
- Context after prompt breaks cache4 people
- Subagent resume cache miss4 people
Not quite your bug?
Original reports4, newest first
- Failure loop during sleep consumes weekly usage with no output (subagent suspected)#103233
- Sleep-mid-response cut-offs trigger an unbounded, uncached full-context regeneration loop#102780
- macOS: background agents re-send full context on every DarkWake after lid close (81 requests sent, 29 completed overnight; usage consumed while asleep)#102597
- Overnight sleep re-writes agent cache per wake-up, drains weekly limit; ambiguous "стоять" stops agents#102269