[BUG] after rate limit reset it does not automatically continue

Resolved 💬 2 comments Opened Mar 12, 2026 by alpham8 Closed Mar 13, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

I couldn't find any existing Bug, that addresses exactly this behaviour:

You have a plan subscription (Pro, Max, etc.) and you're using Opus 4.6 model. If you hit the rate limit during Claude's work and you decide to wait until the reset, it doesn't automatically continue its work after reset.

What Should Happen?

After limit reset (time expiration), it should automatically continue, because you decided to wait until the reset happens.

Error Messages/Logs

Steps to Reproduce

  1. Use a paid monthly plan
  2. In a task, hit your rate limit
  3. Then, claude will ask you what to do.
  4. Decide to wait until the reset.

Claude Model

Opus

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

2.1.73

Platform

Anthropic API

Operating System

Other Linux

Terminal/Shell

IntelliJ IDEA terminal

Additional Information

This behaviour is also reproducible with a simple task with only one agent.

I'm on Linux openSUSE and I've installed Claude using Linuxbrew. This is reproducible in bash and IntelliJ terminal (which should be the same - in Rider and PHPStorm).

View original on GitHub ↗

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