You've hit your weekly limit · resets Aug 10 at 3am (Europe/Paris)

Bug Description
I've been hitting the session limits quickly, especially the last 3 days and today my Max weekly limit is 100%. I was trying to understand what is happenig but nothing explaining this behaviour, but i've spotted for 2-3 times Zombie or Ghost agents running in the background, and this happened when i was typing something and then i wanted to delete what i was typing by pressing "Ctrl C" to clear the line, and this was after Claude finished the JOB.
But what i've is the following:
⏺ All background agents stopped

✻ Cogitated for 1d 8h 2m

❯ 16 background agents were stopped by the user: "You are implementing Task 1 of a UI redesign for t...", "You are reviewing Task 1 of a UI redesign in the A...", "You are implementing Task 2 of a UI redesign for t...", "You are reviewing Task 2 of a UI redesign in the A...", "You are implementing Task 3 of a UI redesign for t...", "You are reviewing Task 3 of a UI redesign in the A...", "You are implementing Task 4 of a UI redesign for t...", "You are reviewing Task 4 of a UI redesign in the A...", "You are performing a SCOPED re-review of a fix dif...", "You are implementing Task 5 of a UI redesign for t...", "You are reviewing Task 5 of a UI redesign in the A...", "You are implementing Task 6, the final code task o...", "You are performing a SCOPED re-review of a fix dif...", "You are performing the final whole-branch code rev...", "You are applying the final fix wave to a UI redesi...", "You are performing the SCOPED re-review of the fin...".
Interrupted · What should Claude do instead?

❯ I've stopped the agents by mistake.
16 background agents were stopped by the user:

Where we waiting for background agents?

No — nothing of mine was pending. Those 16 weren't mine.

I launched exactly one background job this session: the Library interrogation workflow (wk3w0z10o), whose agents were named probe:corpus, verify:*, synthesize-brief. It completed before your message, and I reported its findings. Nothing else of mine was in flight.

The stopped agents were implement/review pairs for "Task 1…6 of a UI redesign," plus scoped re-reviews and a final whole-branch review. That's not work I started, and it matches a known pattern in this project: a parallel session executes committed plans and auto-pushes. Let me check what state it left behind, since that's the part that could actually bite.

You can see that i've asked Claude if these background agents are related to our session, and definitely they were not!

Again, this happened with me few times already!

Environment Info

• Platform: darwin
• Terminal: ghostty
• Version: 2.1.220
• Feedback ID: 582ac648-89fa-4341-9e99-b1c40e29bc0e

Errors

[]