[BUG] Claude Code v2.1.79 auto-interrupts every tool use without user input

Resolved 💬 4 comments Opened Mar 18, 2026 by belenayala Closed Mar 18, 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?

Claude Code repeatedly auto-interrupts all tool uses (Search, Read, Bash) with "Interrupted · What should Claude do instead?" without any user input. The session never completes any task.

Steps to reproduce:

  1. Run claude in any project directory
  2. Ask Claude to analyze code (e.g. trace a bug through multiple files)
  3. Claude starts tool use (Search, Read, etc.) and immediately self-interrupts
  4. This repeats in a loop until "Worked for Xs" and the prompt returns empty

Environment:

  • Version: 2.1.79
  • OS: macOS (darwin)
  • Node: v18.20.8
  • Tried both VS Code integrated terminal and external Terminal.app
  • Reinstalling did not fix it

Expected: Claude completes tool use and returns analysis
Actual: Every tool use is interrupted automatically with no user action

What Should Happen?

Claude should complete all tool uses (Search, Read, Bash) and return a full analysis without interrupting itself.

Error Messages/Logs

Steps to Reproduce

  1. Run claude in any project directory
  2. Ask Claude to analyze code across multiple files
  3. Claude starts tool use (Search, Read, etc.)
  4. Claude auto-interrupts with "Interrupted · What should Claude do instead?" without any user input
  5. Repeats in a loop, ends with "Worked for Xs" and returns empty prompt

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.79 Claude COde

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_

View original on GitHub ↗

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