claude-code - 💡(How to fix) Fix Claude Code 2.1.118+ hangs on macOS Sequoia 15.7.2 with OpenCore Legacy Patcher (Non-Metal GPU) [1 participants]

Preflight Checklist

• I have searched existing issues and this hasn't been reported yet
• This is a single bug report (please file separate reports for different bugs)
• I am using the latest version of Claude Code

What's Wrong?

Claude Code 2.1.118 and 2.1.119 hang immediately on launch. The terminal freezes with a blank cursor, no output is produced, and the process must be killed manually. This happens with any command: claude, claude "hello", claude --version, claude auth status, etc.

Using lsof on the hanging process shows it is stuck on a KQUEUE with count=1, state=0x10 — waiting for a system event that never arrives.

What Should Happen?

Claude Code should launch normally and respond to commands, as it did with version 2.1.116 and earlier.

Error Messages/Logs

No error messages are displayed. The terminal simply hangs silently.

lsof output on hanging process:
2.1.118 PID  sb  cwd  DIR  ...  /Users/sb
2.1.118 PID  sb  txt  REG  ...  /Users/sb/.local/share/claude/versions/2.1.118
2.1.118 PID  sb  3u   KQUEUE   count=1, state=0x10

ps aux shows process in state S (sleeping):
sb  XXXX  0.0  0.7  ...  S  claude "hello"

Steps to Reproduce

1. Install Claude Code 2.1.118 or 2.1.119
2. Run: claude "hello"
3. Terminal hangs indefinitely with blank cursor
4. Process shows state S (sleeping) in ps aux
5. lsof shows KQUEUE blocked with count=1, state=0x10

Note: Version 2.1.116 works perfectly on the same system.

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

2.1.116

Claude Code Version

2.1.119 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

Hardware: iMac 27" (unsupported, running via OpenCore Legacy Patcher 2.4.1) macOS: Sequoia 15.7.2 (24G325) GPU: Non-Metal (no Metal support) Terminal: Terminal.app Shell: zsh

Tested with Node.js 18, 20, and 24 — same result. Tested with npm install and native installer — same result. Tested calling the binary directly — same result. Version 2.1.116 and 2.1.114 work perfectly on the same system. Workaround: manually symlinking to version 2.1.116 restores functionality.