[BUG] Claude Code CLI freezes

Resolved 💬 16 comments Opened Nov 20, 2025 by alghimo Closed Apr 6, 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?

While working with Claud Code (from VSCode using the official extension, on Ubuntu 25), occasionally I get an issue where the terminal freezes. Before that happens, it often "looks" like there is quite a lot of code / messages being shown in the terminal, and when the freeze happens, I only get to see older text, but not the most recent things Claude was doing. If I kill the terminal and start claude again with claude --continue, I do see (part of) what claude was doing. I also verified that when this happens, it is not just a display issue, Claude stops doing work also, and the terminal becomes unresponsive (no way to ctrl + c, ctrl + z, etc)
Before switching to Ubuntu I was working on Windows (also VSCode + Claude Code extension) and had the same issues.

What Should Happen?

The Claude Code terminal keeps working as intended, without freezing or becoming unresponsive.

Error Messages/Logs

No error messages shown

Steps to Reproduce

I am unable to reproduce it, but I have the issue daily (I am not working with Claude the full day, just a few hours a day)

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.0.47

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

VS Code integrated terminal

Additional Information

_No response_

View original on GitHub ↗

16 Comments

github-actions[bot] · 7 months ago

Found 3 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/7455
  2. https://github.com/anthropics/claude-code/issues/10481
  3. https://github.com/anthropics/claude-code/issues/8904

This issue will be automatically closed as a duplicate in 3 days.

  • If your issue is a duplicate, please close it and 👍 the existing issue instead
  • To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

alghimo · 7 months ago

I have checked the 3 issues that are potential duplicates and they are not exactly the same. I get the issues with or without --continue, in my case I can use --continue after the crash, it is just that my current terminal session with claude freezes and becomes unresponsive, and the only option is to kill the terminal and open a new one

Actioninsight · 7 months ago

Ditto I have intermittent freezes, mostly I notice them SSH'ing in from Windows Terminal to ubuntu VM, but I noticed these on my local as well. I have recovered mine on occasion, though I'm not sure how to replicate each time, but usually it involves repeated typing and maybe the esc key.

peixotorms · 7 months ago

I have upgraded the cli today, and I also have this.
I run claude on a server via ssh, ubuntu.
connect via ssh to it.

lukaso · 7 months ago

This is happening on MacOS as well.

cheezmil · 7 months ago

v2.0.55

I use the terminal that comes with vscode and it freezes for over 10 seconds before I can enter a command, but when I use the windows terminal to run claude, I can enter the command immediately. It's really strange

mkavinkumar1 · 6 months ago

Use the '--continue' flag to resume the previous conversation.

alghimo · 6 months ago
Use the '--continue' flag to resume the previous conversation.

Have you read the text I wrote?

kevin-allen · 6 months ago

Additional reproduction case: SSH commands to remote cluster

Environment:

  • Claude Code v2.1.5
  • Linux (Ubuntu)
  • CLI terminal (not VSCode)

Reproduction scenario:
Running multiple SSH commands to a remote HPC cluster caused complete freeze:

● Bash(ssh user@cluster "command1") timeout: 15s
  ⎿  Waiting…

● Bash(ssh user@cluster "command2") timeout: 15s
  ⎿  Waiting…

✢ Roosting… (ctrl+c to interrupt · 51s)

Symptoms:

  • Two SSH commands stuck in "Waiting…" state
  • Session showed "Roosting…" after 51 seconds
  • Terminal completely unresponsive - Ctrl+C does nothing
  • Had to kill the process from another terminal

Notes:

  • SSH commands had 15s timeout configured but freeze persisted well beyond that
  • Multiple concurrent SSH commands may be a trigger
  • The freeze seems to occur when commands are waiting for remote responses
github-actions[bot] · 5 months ago

This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.

Satvik-B · 4 months ago

I have been seeing this issue very frequently.

adityasharma-rzp · 4 months ago

+1, i have been facing this issue very frequently now

mikface · 4 months ago

+1, also happening quite often

vinnyvekaria-apra · 4 months ago

We are getting this issue also unless we turn off telemetry

github-actions[bot] · 3 months ago

Closing for now — inactive for too long. Please open a new issue if this is still relevant.

github-actions[bot] · 3 months ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.