[BUG] All Bash tool commands hang indefinitely

[ShacharRonZoharLili]

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?

Every Bash tool invocation in Claude Code hangs indefinitely and never
returns, even for trivial commands like echo "hello". The command must be
manually cancelled (Ctrl-C). This affects all bash commands without exception
— both sandboxed and with dangerouslyDisableSandbox: true. Non-bash tools
(Read, Write, Edit, Glob, Grep) work normally.

What Should Happen?

Bash commands should execute and return output within a reasonable time.

Error Messages/Logs

Exit code 137                                                                 
  [Request interrupted by user for tool use]                                    
                                                                                
  No other error output — the commands simply hang until manually killed.

Steps to Reproduce

1. Open Claude Code in any directory (does not need to be a git repo)
2. Ask Claude to run any bash command (e.g., echo "hello", date, ls)
3. The Bash tool is invoked but never returns
4. Must manually interrupt with Ctrl-C

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

No response

Claude Code Version

2.1.89

Platform

AWS Bedrock

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

• This starts happening randomly after using claude code for a few days. Reinstalling claude code fixes the issue. The same commands execute instantly in a normal terminal session
• Tested with ~/.zshrc removed (empty shell init) — bash commands still hang indefinitely. This rules out shell configuration as the cause.
• Shell config (~/.zshrc) contains: nvm loading, a custom aws-access function, pnpm PATH setup ~/.zprofile contains only eval "$(/opt/homebrew/bin/brew shellenv)"
• No ~/.zshenv, ~/.zlogin, ~/.bashrc, ~/.bash_profile, or oh-my-zsh
• Claude Code settings inject env vars: CLAUDE_CODE_USE_BEDROCK=1, AWS_PROFILE=my-profile-name, AWS_REGION=us-east-1
• AWS profile is authenticated, no MFA or interactive shell is blocking the shell
• Disabling sandbox (dangerouslyDisableSandbox: true) does not help
• Non-Bash tools (Read, Write, Edit, Glob, Grep) all work correctly

[luckyboy703]

same to you

[olegovsyannikov]

Final fix for the "Bash tool randomly fails with Exit code 126 / [Request interrupted by user for tool use]" issue on Linux Claude Code:

Downgrade to 2.1.112 and pin it.

npm install -g @anthropic-ai/claude-code@2.1.112

Then disable autoupdates so a future startup doesn't silently re-upgrade:

claude config set autoUpdates false # or set "autoUpdates": false in ~/.claude/settings.json

Verify:

• claude --version → 2.1.112 (Claude Code)
• Install dir at ~/.npm-global/lib/node_modules/@anthropic-ai/claude-code/ should contain cli.js (NOT bin/claude.exe).

After downgrade, fully exit and re-launch any CC session that was running on 2.1.113+. The old native binary stays loaded in memory until the process is restarted; --resume after restart is fine, just don't /clear or hot-reload — fully exit first.

Verified: 50/50 parallel echo calls succeeded after downgrade. Same test was failing within the first 6–8 calls on 2.1.117 every single time.

---

Stuff that does NOT work, save your time:

• Rebooting the VPS — symptom continued unchanged after a clean boot with no stale libs.
• The /sandbox slash command → "Sandbox disabled" — bwrap still wraps every Bash call, race still hits.
• "sandbox": { "enabled": false } in ~/.claude/settings.json — silently ignored on Linux per sandbox.enabled: false setting ignored — bwrap still wraps all Bash commands #35986. Made things look fixed for a 6–8 call streak then failed again.
• sudo mv /usr/bin/bwrap /usr/bin/bwrap.disabled — actively makes it worse: CC has bwrap path resolved at startup, so with bwrap missing every Bash call returns Exit 126 immediately. The "graceful fallback to unsandboxed execution" promised in the docs does not actually trigger in-session. If you've done this, restore with the inverse mv.

---

Why: v2.1.113 switched the npm package from a JS entrypoint (cli.js) to a native Linux binary (bin/claude.exe, ELF). The native build wraps every Bash call in bwrap --new-session --die-with-parent --unshare-pid --unshare-net .... Parallel/burst Bash invocations race during bwrap setup; the sub-second non-zero bwrap exit is reported with the same string CC uses for a real Ctrl-C — looks like the user is interrupting when they aren't.

2.1.112 is JS-based and doesn't wrap every Bash call this way → race never happens.

Related upstream issues:

• [BUG] All Bash tool commands hang indefinitely #41983 — "All Bash tool commands hang indefinitely"
• sandbox.enabled: false setting ignored — bwrap still wraps all Bash commands #35986 — sandbox.enabled: false not respected on Linux
• Sandbox fails with "bwrap: execvp /bin/bash: No such file or directory" on Ubuntu 24.04 #41863 — bwrap fails with execvp on Ubuntu

Once Anthropic ships a fix in the native build, re-enable autoupdates / upgrade manually.

[github-actions]

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