[BUG] Claude Code confirms stop but silently continues in the background spending tokens forever ("Tool permission request failed: Error: Stream closed")

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?

Claude Code 1.0.1768 'Pro' (ha!) mark (help check for updates says its the latest)

Sorry 100% a bit jaded here, I use several AI agents but cc seems to be the most frustrating.

While claude has many bugs this is my favorite yet. New week and new 5 hour block of my child allowance 0% usage. I type the word OK before realizing I am talking to claude vs the agent I wanted to use so immediately hit STOP. Perfect, [Request interrupted by user] claude stops and I go make the request with an agent that can get the work done. As Claude Code doesn't make it quick and easy to see usage during a session (despite the low limits) I maintain a web app window open too just to monitor my usage constantly. Some hours later I am alt tabbing, and notice in the preview of that usage for the current session is 100%. Not only is the current session maxed out but I am at 12% the weekly allowance and I have had claude do absolutely nothing. I go back to the claude session window and last it shows is it was stopped.

So, I do my favorite, restart claude code assuming yet another bug and go back to the session.
Now it shows what it actually was doing, hundreds of lines of:

R:\Path\to\Code\File\BtCodeGenerator.cs
Tool permission request failed: Error: Stream closed
Edit
R:\Path\to\Code\File\BtCodeGenerator.cs
Tool permission request failed: Error: Stream closed
Edit
R:\Path\to\Code\File\BtCodeGenerator.cs
Tool permission request failed: Error: Stream closed
Edit
R:\Path\to\Code\File\BtCodeGenerator.cs
Tool permission request failed: Error: Stream closed
Edit
R:\Path\to\Code\File\BtCodeGenerator.cs
Tool permission request failed: Error: Stream closed
Edit
R:\Path\to\Code\File\BtCodeGenerator.cs
Tool permission request failed: Error: Stream closed
Edit
R:\Path\to\Code\File\BtCodeGenerator.cs
Tool permission request failed: Error: Stream closed

Clearly it kept doing the same thing over and over again. Ironically, in my global CLAUDE.md file I already have plenty of babysitting directives including: - If you continue to fail to edit files don't resort to bad ideas like using sed. Instead stop, figure out why you can't edit on your first try, and then lets update your claude.md. but as it often ignores its directives I guess that isn't too surprising.

Given it seems this would have spun until any credits were used up I can only imagine if I had wallet enabled to pay for extra usage or enterprise billing.

I used the contact support with details and a screenshot to receive back:

• Told me to file a bug report here

and to prevent this:
• After stopping a session, verify no orphaned processes remain by running ps aux | grep claude in your terminal
• If you see lingering processes, kill them explicitly
• Use the /usage command to check your quota before and after sessions

Of course the question of what claude code can't keep track of its own children processes is beyond me, manually making sure claude isn't doing something sneaky in the background is more work. Using /usage wouldn't have helped as I immediately stopped using claude but I guess even when not using claude I could call usage to make sure it doesn't randomly consume tokens.

I was also told it was a "known bug pattern with Claude Code". One would think a known bug that bills users extra doing nothing would be a big issue, but clearly its the users responsibility to make sure claude doesn't run away with your wallet.

If you assume there was some credit back you would be wrong.

Honestly, it's embarrassing a company valued at over 150B has their premiere tool make such major mistakes and doesn't have a better support system. MONTHLY revenue is some ~580M and growing, if 1/1000th of that was additionally spent on bug monkeys/ cs agents making say 125K a year that would be 50+ additional staff or one staff member to triage only 2 tickets a day (or even fewer if you consider several more tickets are feature requests/dupes/or my favorite claude filing bugs in the wrong repo;00).

What Should Happen?

Stop when it says it stopped. Not make you pay to your limit for it to spin doing nothing over and over again.

Error Messages/Logs

Steps to Reproduce

I would guess just start a conversation and hit stop several times. I would troubleshoot further for you, but literally just asking claude hiaku in a new text session what time is it uses 3% usage and CC isn't mine to debug.

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

1.0.1768

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

_No response_