Diagnosis · Claude · Hard reset
Claude names the thief: parallel subagents, and a reset for Pro and Max
Both clocks cleared for Pro and Max users after a fix for Claude Code sessions that were spawning excessive parallel subagents.
We've reset 5-hour and weekly rate limits for all users on Pro and Max plans. We fixed an issue that caused some Claude Code sessions to spawn excessive parallel subagents, burning through usage faster than expected.
“We've reset 5-hour and weekly rate limits for all users on Pro and Max plans. We fixed an issue that caused some Claude Code sessions to spawn excessive parallel subagents, burning through usage faster than expected.”
The first Monday in June, the Claude desk did something this beat almost never gets: it named the mechanism. Sessions had been spawning excessive parallel subagents. Usage burned faster than expected. The issue was fixed, and both clocks were cleared for Pro and Max.
Keep this card next to the Codex drain weekend four weeks later, where the autopsy also landed on background work doing extra laps. Two houses, two products, one failure mode: an agent that keeps going after the useful part is finished.
We are not claiming a shared cause, because neither post claims one. We are claiming that the same shape appeared twice in a month, and that both times the remedy was a zeroed meter and a paragraph.
What it means
- Named plans this time — Pro and Max — unlike the July posts, which say all users. The difference is in the copy, so it is in the card.
- Both buckets cleared: five-hour and weekly.
- The stated cause is excessive parallel subagents burning usage faster than expected, and the post says the issue was fixed before the reset went out.