[BUG] CLI freezes after Ctrl+C, becomes completely unresponsive

Resolved 💬 9 comments Opened Jan 13, 2026 by zedzima Closed May 3, 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?

CLI freezes after Ctrl+C, becomes completely unresponsive

Environment: macOS Tahoe 26.2 M3Pro

Expected: Ctrl+C should cleanly cancel and return to input prompt
Actual: Complete freeze requiring force quit

This has happened multiple times.

What Should Happen?

⏺ Read(content/services.en.toml)
⎿  Read 468 lines
⎿  Interrupted · What should Claude do instead?

· Catapulting… (ctrl+c to interrupt · thinking)

Error Messages/Logs

⏺ Background command "Start local server" failed with exit code 137.

Steps to Reproduce

Steps to reproduce:

  1. Start typing a prompt
  2. Press Shift+Enter (trying to add newline)
  3. Press Ctrl+C to cancel
  4. CLI becomes frozen - no input accepted, commands don't work
  5. Pressing Escape shows recent requests but they're not interactive
  6. Eventually crashes to terminal

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

2.1.6

Claude Code Version

2.1.6

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_

View original on GitHub ↗

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