[BUG] All Bash tool commands hang indefinitely
Resolved 💬 3 comments Opened Apr 1, 2026 by ShacharRonZoharLili Closed May 27, 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?
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
- Open Claude Code in any directory (does not need to be a git repo)
- Ask Claude to run any bash command (e.g., echo "hello", date, ls)
- The Bash tool is invoked but never returns
- 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
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗