[FEATURE] Auto-continue after subscription rate limit resets

Problem

When Claude Code hits the subscription usage limit ("5-hour limit reached - resets 3pm"), the session pauses and the user must manually wait and type "continue" to resume. For long-running tasks (overnight work, AFK coding), this kills productivity.

This has been reported multiple times:

• #13354 (41+ upvotes, primary tracking issue)
• #26789 (closed as dup)
• #18980 (closed as dup)
• #28484 (better "stop and wait" behavior)
• #5977 (context loss after usage limit)

Community Solution

I built an open-source tool that solves this today:

npm i -g claude-auto-retry
claude-auto-retry install

How it works: Intercepts the claude command transparently via a shell function, monitors the tmux pane for rate limit messages, waits for the reset time (timezone-aware), and sends "continue" automatically via tmux send-keys.

• Zero dependencies, zero workflow change
• Works with and without tmux (auto-creates session if needed)
• Verifies Claude is still the foreground process before sending keys
• Supports --print mode (buffers + retries for piped usage)
• 59 tests, MIT licensed

Repo: https://github.com/cheapestinference/claude-auto-retry
npm: https://www.npmjs.com/package/claude-auto-retry

Suggested Native Fix

While the community tool works, this behavior should be built directly into Claude Code:

1. When rate limit is hit, show the reset time (already done)
2. Add an "Auto-continue when limit resets" option to /rate-limit-options
3. Claude Code sleeps internally until the reset time + margin
4. Automatically resumes the conversation — no tmux, no wrapper, no external tool

This would be a much cleaner UX since Claude Code already knows the reset time from the API response and can handle the retry internally without needing terminal monitoring.

Environment

• Claude Code 2.1.x
• Anthropic Pro/Max subscription
• All platforms (Linux, macOS)