›_ Claude Code Issues
Claude Code Issues / #23725

[BUG] Linux Terminal Freezes after launching new versions of Claude code from 2.1.34. Complete Freeze - Cannot Type, Ctrl+C Non-Responsive

Resolved 💬 23 comments Opened Feb 6, 2026 by ravibandari28-ops Closed Apr 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?

Environment

  • OS: RHEL 8.10 (Kernel 4.18.0-553.el8_10.x86_64)
  • Shell: zsh
  • Claude Version: 2.1.34 (broken) vs 2.1.20 (working)
  • Installation: Local binary (~/.local/bin/claude)
  • Memory: 15GB total, 11GB available

Configuration

{
  "enabledPlugins": {
    "document-skills@anthropic-agent-skills": true,
    "example-skills@anthropic-agent-skills": true
  },
  "alwaysThinkingEnabled": true,
  "autoUpdaterStatus": "disabled"
}

Reproduction Steps

  1. Launch Claude Code v2.1.34: claude
  2. Terminal appears but is completely unresponsive
  3. Cannot type any input
  4. Ctrl+C, Ctrl+Z, Ctrl+D all non-functional
  5. Must force-close terminal

Expected vs Actual Behavior

Expected: Claude launches with interactive prompt
Actual: Complete freeze, no keyboard input accepted

Workaround

Downgrade to v2.1.20 and disable auto-updates

Additional Context

  • ✅ v2.1.20 works perfectly
  • ❌ v2.1.34 100% reproducible freeze
  • Cannot run /doctor or /bug in frozen version
  • No error messages or logs visible
  • System resources are adequate
  • Other terminal applications work normally

Hypothesis

The v2.1.34 changes (agent teams crash fix or bash security fix) may have introduced a regression affecting terminal I/O on RHEL 8.10 or zsh configurations.

Willingness to Help

  • Can test patches or debug builds
  • Can provide strace/debug output if instructions provided
  • Available for follow-up questions

What Should Happen?

  • Claude Code should launch normally and display a prompt
  • User should be able to type commands and interact with the CLI
  • Ctrl+C should interrupt operations as designed

Error Messages/Logs

Steps to Reproduce

  1. Start from working v2.1.20
  • Claude Code v2.1.20 launches normally
  • User can type commands and interact without issues
  1. Update to v2.1.34 (either manually or via auto-update)
  1. Launch Claude Code v2.1.34

``bash
claude
``

  1. Observe freeze immediately
  • Terminal appears to launch but is completely unresponsive
  • No prompt appears or prompt appears but cannot accept input
  • Cursor may or may not blink, but no keyboard input is registered
  1. Attempt recovery fails
  • Press Ctrl+C - No response
  • Press Ctrl+Z - No response
  • Press Ctrl+D - No response
  • Type any characters - Nothing appears
  • Only option is to close terminal window forcefully

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

2.1.20

Claude Code Version

2.1.34

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

What Doesn't Work

  • ❌ Claude Code v2.1.34 - Complete freeze on launch
  • ❌ Cannot run /doctor in frozen version
  • ❌ Cannot run /bug in frozen version
  • ❌ No error messages displayed
  • ❌ No logs visible to diagnose issue

Diagnostic Attempts

Since v2.1.34 is completely frozen, unable to run:

  • /doctor - Cannot type command
  • /bug - Cannot type command
  • Ctrl+C - Does not respond
  • Any debugging commands - Terminal unresponsive

Impact

  • Severity: CRITICAL - Complete loss of functionality
  • User Impact: Cannot use Claude Code at all in v2.1.34
  • Workaround Available: Yes (downgrade to v2.1.20)
  • Data Loss Risk: No data loss, but complete unusability

Questions for Maintainers

  1. Are there any known issues with v2.1.34 on RHEL 8.10 or zsh shells?
  2. Could the agent teams crash fix or bash security fix affect terminal I/O?
  3. Are there debug logs that can be enabled before launch to diagnose this?
  4. Is there a way to run v2.1.34 in verbose/debug mode to capture startup logs?

View original on GitHub ↗

23 Comments

github-actions[bot] · 5 months ago

Found 3 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/23661
  2. https://github.com/anthropics/claude-code/issues/23619
  3. https://github.com/anthropics/claude-code/issues/23326

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

stevecrawshaw · 5 months ago

Also on Windows 11 with Git Bash VS Code integrated terminal on v 2.1.34. Seems to "unlock" and become responsive when Enter key is pressed(!)

saadsinpk · 5 months ago

Same issue with mac terminal v 2.1.34

mmotzer · 5 months ago
Also on Windows 11 with Git Bash VS Code integrated terminal on v 2.1.34. Seems to "unlock" and become responsive when Enter key is pressed(!)

Works also for me. Thank you!

rviragh-awesome · 5 months ago

For me it only freezes when typing a large amount of text (>1500 characters). It does open and run normally.

pmatos · 5 months ago

I also am seeing this. I think it might be related to agent teams. Do you also have agent teams enabled?

rviragh-awesome · 5 months ago

yes, I believe I have agent teams enabled. (Not 100% sure where to find the setting, but I've seen Claude use it.) By the way, if a session freezes you can resume it with "claude /resume" to resume a session. (include --dangerously-skip-permissions if you want that, the option won't be inherited from the session you're resuming.)

Sillocan · 5 months ago

Also seeing this with 2.1.37 (Claude Code) with straight bash on centos.

Update: this only happens in a new workspace when it tries to draw the box around the terminal. Odd.

Frozen:

<img width="938" height="334" alt="Image" src="https://github.com/user-attachments/assets/c8ae48e4-b220-4492-8732-9dcd807f936e" />

not frozen:

<img width="938" height="196" alt="Image" src="https://github.com/user-attachments/assets/62a42d79-cf6a-41f8-8098-27946c05a102" />

ravibandari28-ops · 5 months ago
I also am seeing this. I think it might be related to agent teams. Do you also have agent teams enabled?

No agent teams not enabled

stevecrawshaw · 5 months ago

version 2.1.38 has fixed this for me on windows git bash in VS Code \ Positron

rviragh-awesome · 5 months ago

can you try entering around 2000 characters (a very long paragraph) into
the prompt to see if it freezes for you?

On 2026. Feb 10., Tue at 14:38, Steve Crawshaw @.***>
wrote:

stevecrawshaw left a comment (anthropics/claude-code#23725) <https://github.com/anthropics/claude-code/issues/23725#issuecomment-3877675139> version 2.1.38 has fixed this for me on windows git bash in VS Code \ Positron — Reply to this email directly, view it on GitHub <https://github.com/anthropics/claude-code/issues/23725#issuecomment-3877675139>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/B6BVZ2SD6L5EINYBLVTB7FD4LHNOFAVCNFSM6AAAAACUHZQWJCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTQNZXGY3TKMJTHE> . You are receiving this because you commented.Message ID: @.***>
ravibandari28-ops · 4 months ago
Also seeing this with 2.1.37 (Claude Code) with straight bash on centos. Update: this only happens in a new workspace when it tries to draw the box around the terminal. Odd. Frozen: <img alt="Image" width="938" height="334" src="https://private-user-images.githubusercontent.com/1627865/547302238-c8ae48e4-b220-4492-8732-9dcd807f936e.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NzEzMTE1OTgsIm5iZiI6MTc3MTMxMTI5OCwicGF0aCI6Ii8xNjI3ODY1LzU0NzMwMjIzOC1jOGFlNDhlNC1iMjIwLTQ0OTItODczMi05ZGNkODA3ZjkzNmUucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI2MDIxNyUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNjAyMTdUMDY1NDU4WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9ZGFjMjNkYjA2Mzk2NDAyMGQ0M2IwODliNjY3ZmNhYjY0MTYyMjMyNzMwYmQzODNlMjQ3YThlMGFjYmRmODllNSZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QifQ.ZwjnCtENK8YO7xokaa40ADaLsjt1epdBO7xVgfu5rIs"> not frozen: <img alt="Image" width="938" height="196" src="https://private-user-images.githubusercontent.com/1627865/547302296-62a42d79-cf6a-41f8-8098-27946c05a102.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NzEzMTE1OTgsIm5iZiI6MTc3MTMxMTI5OCwicGF0aCI6Ii8xNjI3ODY1LzU0NzMwMjI5Ni02MmE0MmQ3OS1jZjZhLTQxZjgtODA5OC0yNzk0NmMwNWExMDIucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI2MDIxNyUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNjAyMTdUMDY1NDU4WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9NzUzZGUzY2E1MWM5NDE4YzQ5N2RkOTBiZjJhYTEzYzU2MDljMDMxNTg5ODYzODM1ZTA5NzRmYzhiM2IxNmQ2MiZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QifQ.qlS4kY3BTLxcH62JlaeSdKPO-8fWGWdIG432CS1NCs4">

What is the hack you did for non-frozen case?

ravibandari28-ops · 4 months ago

Any update on the issue. The issue is still persisting for me!

Bad-Listener · 4 months ago

Me too, tried downgrading to latest stable with no luck.
Now I cannot even run claude doctor

ravibandari28-ops · 4 months ago

Submitted internal bug report via /bug command.
Feedback ID: 0f0784d8-bae5-4922-a7f4-e2ac74c245f4

ravibandari28-ops · 4 months ago

Bump — any update on this? Still blocked from Opus 4.6 as a Max subscriber."

castrapel · 4 months ago

The only fix that I've found was to avoid using the standalone Linux CC binary and installing the npm package. If you are running CC in an offline environment as I am, you'll need to build it in a docker container with similar glibc (and possibly gcc) as the systems you intend to run CC on.

rviragh-awesome · 4 months ago

This might not be the right thread, but I keep getting messages in it for
weeks. I'd like you all to sign our petition to give Claude a body:
https://www.change.org/p/create-a-physical-embodiment-for-claude

It will help solve this problem by giving the team a bit more money that
they can spend on bugfixes. Please sign the petition.

On 2026. Feb 19., Thu at 17:55, Curtis @.***> wrote:

castrapel left a comment (anthropics/claude-code#23725) <https://github.com/anthropics/claude-code/issues/23725#issuecomment-3928509375> The only fix that I've found was to avoid using the standalone Linux CC binary and installing the npm package. If you are running CC in an offline environment as I am, you'll need to build it in a docker container with similar glibc (and possibly gcc) as the systems you intend to run CC on. — Reply to this email directly, view it on GitHub <https://github.com/anthropics/claude-code/issues/23725#issuecomment-3928509375>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/B6BVZ2WDBFRHABUFG3HYTVD4MXTHZAVCNFSM6AAAAACUHZQWJCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTSMRYGUYDSMZXGU> . You are receiving this because you commented.Message ID: @.***>
ravibandari28-ops · 4 months ago
The only fix that I've found was to avoid using the standalone Linux CC binary and installing the npm package. If you are running CC in an offline environment as I am, you'll need to build it in a docker container with similar glibc (and possibly gcc) as the systems you intend to run CC on.

You are saying that through curl installation there was a problem, but through npm package you are not finding any problems in Linux?

DylanMaxStermer · 4 months ago

Any update, this issue prevents me from using anything past Claude 1.2.23

ravibandari28-ops · 4 months ago
Any update, this issue prevents me from using anything past Claude 1.2.23

hi @DylanMaxStermer ,
At present this can only be solved through npm package installation instead of native installer or curl based insataller.
With the npm based installation I can able to access new versions of Claude code. Remember to backup the claude folder and settings before removing native installation and through npm installation.

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.