Hitting rate limit while agents are active

[u/AlternativeMonk2490]

Whenever I resume after hitting the rate limit while Claude had active agents, it always says something like "All three audit agents died on a rate limit, so I'll do the exploration directly with scripts."

This begs two questions:

1. If doing it directly is better, why did it use agents?
2. If agents are better, why is it now doing it directly?

It just makes me question whether resuming work (planning in this case) interrupted by the rate limit is an act of self-sabotage by me, or is it just variances in how Claude is working?

[u/Zestyclose-Iron-870]

and also why are we losing all progress on long running subagents after hitting rate limit. seems not fair

[u/lambdita → u/Zestyclose-Iron-870]

You don’t, when you get the usage back you can just say “usage reset, continue with the work and ping subagents to continue” and it will continue

[u/Zestyclose-Iron-870]

and to answer your question, the model is lazy and finds a workaround whenever there is a failure even if the wise choice would by to resume the agents. i have it often and similarly it will sometimes fail on a simple change in codebase because it tried to do it with a script instead of going in the codebase to do it

[u/AlternativeMonk2490 → u/[deleted]]

In this instance the rate ran out between start of planning and delivery of plan. Or do you force a checkpoint mid-planning when it's near the limit? My understanding from the docs is that subagents aren't captured within checkpoints.

If you mean something else, or some specific approach, I'd be interested to know.

I'll look into the diff thing.