[Feature Request] Auto-resume on rate limit with configurable retry behavior

Resolved 💬 2 comments Opened Dec 27, 2025 by vamseeachanta Closed Dec 27, 2025

Bug Description

Feature Request: Auto-Continue After Rate Limit Reset

Problem

When Claude Code hits a rate limit mid-task, it stops completely and requires manual intervention. This breaks workflow for long-running tasks, background agents, and unattended operations.

Proposed Solution

Add an option to automatically wait and resume:

  • Flag: --auto-continue or --wait-on-limit
  • Setting: autoResumeOnRateLimit in settings.json
  • Environment variable: CLAUDE_AUTO_CONTINUE=1

Desired Behavior

  • Detect rate limit error
  • Display countdown timer until reset
  • Auto-resume once limit resets
  • Preserve full context and state

Use Cases

  • Overnight multi-file refactors
  • Automated CI/CD code review pipelines
  • Long research tasks with subagents
  • Batch processing across repositories

Alternatives Considered

  • External wrapper scripts (fragile, loses context)
  • Manual monitoring (not scalable)

---

To submit: Run /feedback in Claude Code and paste the content above.

Environment Info

  • Platform: linux
  • Terminal: gnome-terminal
  • Version: 2.0.76
  • Feedback ID: 09159f48-cd5a-427b-bca6-24be961b71b2

Errors

[{"error":"AbortError: The operation was aborted\n    at abortChildProcess (node:child_process:725:27)\n    at EventTarget.onAbortListener (node:child_process:795:7)\n    at [nodejs.internal.kHybridDispatch] (node:internal/event_target:831:20)\n    at EventTarget.dispatchEvent (node:internal/event_target:766:26)\n    at abortSignal (node:internal/abort_controller:370:10)\n    at AbortController.abort (node:internal/abort_controller:392:5)\n    at Timeout._onTimeout (file:///home/vamsee/.npm-global/lib/node_modules/@anthropic-ai/claude-code/cli.js:4967:6586)\n    at listOnTimeout (node:internal/timers:581:17)\n    at process.processTimers (node:internal/timers:519:7)","timestamp":"2025-12-27T17:57:16.419Z"}]

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗