[BUG] Claude Code 2.1.34+ unusable on Oracle Linux 8 - CPU spin or immediate exit

Resolved 💬 3 comments Opened Feb 7, 2026 by bennyfactor Closed Feb 7, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report
  • [x] I am using the latest version of Claude Code (Note: latest versions are broken; this report documents that)

What's Wrong?

Claude Code 2.1.34 renders the UI, mounts the REPL, then spins at 100% CPU indefinitely. No input is accepted and Ctrl+C doesn't work.

Versions 2.1.36 and 2.1.37 render the UI then immediately exit back to shell with no error.

Version 2.1.7 works perfectly on the same machine.

What Should Happen?

Claude Code should accept input normally after displaying the welcome screen.

Error Messages/Logs

No errors in debug log. Startup completes normally:

[DEBUG] [REPL:mount] REPL mounted, disabled=false
[DEBUG] [render] first ink render: 1403ms since process start
...
[DEBUG] Released PID lock for 2.1.34

ps aux shows 99% CPU for the stuck 2.1.34 process.

Steps to Reproduce

  1. Install Claude Code 2.1.34+ on Oracle Linux 8
  2. Run claude or claude --debug
  3. Welcome screen appears normally
  4. Process either spins at 100% CPU (2.1.34) or immediately exits (2.1.36/2.1.37)

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

2.1.7

Claude Code Version

2.1.34, 2.1.36, 2.1.37 (all broken)

Platform

Anthropic API (Claude Max)

Operating System

Oracle Linux 8 (Other Linux)

Terminal/Shell

Other - SSH and mosh to Oracle Linux 8, tested both with and without tmux. Same behavior in all cases.

Additional Information

Workaround: Recovered working 2.1.7 binary from a still-running process:

cp /proc/<pid>/exe /tmp/claude-old-working
ln -sf /tmp/claude-old-working ~/.local/bin/claude

This confirms the regression - old binary works, new binaries don't, same machine and environment.

View original on GitHub ↗

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