[Bug] Auto-continue disabled after five_hour rate limit reset with multiple sessions
Bug Description
Summary
With /config → "Continue automatically at usage limit" enabled, a CLI session stopped at a five_hour usage limit and never retried after the reset time. The process stayed alive the whole time; the session only resumed when I typed into it manually the next morning, ~8.5 hours later.
Environment
- Claude Code
2.1.261 - macOS (Apple Silicon)
entrypoint: cli, launched as:exec caffeinate -dims claude --enable-auto-mode- Model:
claude-opus-5
Timeline (JST)
| Time | Event |
|---|---|
| 00:45:06 | Session A (e8d777e2) hits limit, HTTP 429 |
| 00:49:10 | Session B (991e4133, sessionKind: bg) hits same limit |
| 01:20 | resetsAt (1788625200) |
| 01:20–09:41 | No records at all in either session JSONL |
| 09:41:12 / 09:41:24 | Both resumed — by me typing into the still-running sessions |
Gap: 536 min / 532 min with zero records, spanning the reset.
Rate limit payload
{
"status": "rejected",
"resetsAt": 1788625200,
"unifiedRateLimitFallbackAvailable": false,
"rateLimitType": "five_hour",
"overageStatus": "rejected",
"overageDisabledReason": "member_zero_credit_limit",
"isUsingOverage": false
}
Ruled out
- Sleep: none.
pmset -g logshows powerd's "Prevent sleep while display is on" assertion (same id0x10000944f) held continuously across the window; no Sleep/Wake/DarkWake events. - Crash:
~/Library/Logs/DiagnosticReports/has no entries for the window. - Network: kernel TCP + mDNSResponder logs show the Claude process connecting every ~20s throughout.
- Process death: the CLI process was alive — I typed into the same running session the next morning and it continued.
Expected
After resetsAt, the interrupted turn is re-sent automatically.
Actual
Nothing happens. The session sits idle indefinitely until manual input.
Possibly relevant
Two sessions shared the same five-hour window, one of them sessionKind: bg. Both failed to auto-resume.
Environment Info
- Platform: darwin
- Terminal: Orca
- Version: 2.1.261
- Feedback ID: da04df96-5a70-4032-b3dc-1b8ad537cbbf
Errors
[]This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗