[BUG] [CRITICAL] Interrupt button does not stop processing - logout also fails to stop

Resolved 💬 3 comments Opened Jan 30, 2026 by bennykyud Closed Feb 2, 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?

The Interrupt button does not stop Claude's processing. Even after
logging out and logging back in, Claude continues the previous task.
This causes uncontrolled token usage and billing.

What Should Happen?

  • Interrupt should IMMEDIATELY stop processing
  • Logout should cancel all pending requests
  • User should have control over their usage

Error Messages/Logs

Steps to Reproduce

  1. Start a task in Claude Code (e.g., grep for React hooks)
  2. While Claude is processing ("Sussing...", "Puzzli..."), click Interrupt
  3. Observe that Claude does NOT stop
  4. Logout from Claude Code
  5. Login again
  6. Observe that Claude CONTINUES the previous task
  7. Usage/billing continues without user control

Claude Model

Not sure / Multiple models

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

1.1.1520 (48ced7)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

Impact:

  • CRITICAL: User has no control over billing
  • Unwanted charges on account
  • Cannot stop runaway processes
  • Very frustrating and concerning

Suggested Solution:

  1. Interrupt should send cancel signal to server
  2. Logout should cancel all pending requests
  3. Add confirmation that process was actually stopped
  4. Add server-side timeout for long-running tasks

<img width="822" height="300" alt="Image" src="https://github.com/user-attachments/assets/f29827cc-2508-4090-9fcc-618be406cd8b" />

<img width="809" height="258" alt="Image" src="https://github.com/user-attachments/assets/2c27b35d-b81c-4233-a621-9e29dcf034fd" />

View original on GitHub ↗

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