Problem
When rate limited, Claude Code shows a message like:
You're out of extra usage · resets 11:30am (Asia/Colombo)
Currently, the user must manually return and type "continue" or press enter when the reset time is reached. This interrupts workflows, especially for:
- Long-running tasks left overnight
- Users in different timezones
- Automated/unattended use cases
Proposed Solution
Add an option to automatically resume the interrupted task when the rate limit resets.
Implementation Ideas
- Parse the reset time from the rate limit message
- Schedule a continuation using:
- Native timer/cron within Claude Code
- Or system-level scheduler (launchd on macOS, systemd on Linux)
- Auto-send continuation when time is reached
Configuration
Could be a setting in settings.json:
{
"autoResumeAfterRateLimit": true
}
Or a CLI flag:
Fallback Behavior
- If the terminal/session is closed, do nothing (safe default)
- Only auto-resume if the session is still active
User Benefit
- Unattended long-running tasks complete without manual intervention
- Better developer experience for heavy users who hit rate limits regularly
- Enables "fire and forget" workflows
Alternatives Considered
- Hooks: Users could build this with custom hooks, but native support would be cleaner
- External scripts: Possible but fragile and platform-specific
Would love to see this as a first-class feature!
Problem
When rate limited, Claude Code shows a message like:
Currently, the user must manually return and type "continue" or press enter when the reset time is reached. This interrupts workflows, especially for:
Proposed Solution
Add an option to automatically resume the interrupted task when the rate limit resets.
Implementation Ideas
Configuration
Could be a setting in
settings.json:{ "autoResumeAfterRateLimit": true }Or a CLI flag:
Fallback Behavior
User Benefit
Alternatives Considered
Would love to see this as a first-class feature!