[Bug] Bash commands freeze with no output in Claude Code

[worachai3]

Bug Description
I can't run any bash commands in Claude Code, neither by using ! nor by telling Claude to execute a command. For example, !pwd or telling Claude to list files—both cause the command to freeze, and nothing shows up. The output never comes from these commands run in Claude Code. In my normal terminal, I can run these commands normally.

Environment Info

• Platform: darwin
• Terminal: WezTerm
• Version: 2.0.57
• Feedback ID: 593140d1-7701-4143-bb92-bceb8fb1b9e8

Errors

[{"error":"Error: Request was aborted.\n    at makeRequest (/$bunfs/root/claude:1269:3939)\n    at processTicksAndRejections (native:7:39)","timestamp":"2025-12-03T19:00:57.119Z"},{"error":"AbortError: The operation was aborted.\n    at unknown\n    at abortChildProcess (node:child_process:935:42)\n    at onAbortListener2 (node:child_process:35:24)\n    at abort (unknown)\n    at <anonymous> (/$bunfs/root/claude:4291:2197)","timestamp":"2025-12-03T19:01:23.572Z"}]

[github-actions]

Found 3 possible duplicate issues:

1. [BUG] Bash executions freeze Claude session. #7353
2. [BUG] FreeBSD not supported - bash commands hang indefinitely (v2.0.29) #10673
3. [BUG] Bash tool intermittently hangs when reading from FIFOs (named pipes) #12650

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

[worachai3]

I can't run any command, none of the bash commands work. I've been able to run any command normally before I upgraded to claude 2.0.57

[worachai3]

Confirm the issue is only existed on version 2.0.57.

Once I downgrade to 2.0.56 the issue is gone.

[worachai3]

Updated to version 2.0.60 and tried again, still got same issue. However this comment does fix the issue by running claude code with this command
SHELL=/bin/bash claude

[github-actions]

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.