[BUG] Bash Commands do not execute, Return No Output

[djbyrne17]

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?

All bash commands executed through the Bash tool return (Bash completed with no output) regardless of the command. This affects even the simplest commands like echo, pwd, and ls.

What Should Happen?

Bash commands should return their standard output, for example:

• echo "test" should return: test
• pwd should return the current working directory path
• ls should return directory contents

Error Messages/Logs

`(Bash completed with no output)`

Steps to Reproduce

1. Start Claude Code session
2. Ask Claude to run any bash command, for example:
   • echo "test"
   • pwd
   • ls
   • which bash
3. Observe result: (Bash completed with no output)

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

No response

Claude Code Version

2.1.81 (Claude Code) stable channel, confirmed up to date as of 2026-03-31

Platform

AWS Bedrock

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

Additional Observations

• Other tools work normally:

  • Read tool ✓
  • Write tool ✓
  • Glob tool ✓
  • Grep tool ✓

• Issue is consistent:

  • Occurs across multiple environments (Docker and native macOS)
  • Persists across sessions
  • Affects ALL bash commands without exception

• User's terminal works normally:

  • User can run bash commands directly in terminal successfully
  • Issue is isolated to Claude Code's bash execution/capture

• No obvious configuration issues:

  • Checked ~/.claude/settings.json - no bash-specific redirections
  • No unusual environment variables that would suppress output

Impact

• Severity: Medium-High
• Users cannot use Claude to run bash commands for diagnostics, system operations, or automation
• Workaround exists: Ask user to run commands manually, but this defeats the purpose of Claude Code automation

Suggested Investigation Areas

1. Bash stdout capture mechanism in Claude Code
2. Pipe/buffer handling for bash subprocess output
3. TTY/PTY allocation for bash subprocess
4. Shell initialization or profile loading that might redirect stdout

Configuration Files

Settings from ~/.claude/settings.json:

{
  "apiKeyHelper": "/Users/djbyrne/Desktop/genAI/genai_api/claude_code_apikeyhelper.sh",
  "env": {
    "CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC": "1",
    "CLAUDE_CODE_DISABLE_EXPERIMENTAL_BETAS": "1",
    "CLAUDE_CODE_API_KEY_HELPER_TTL_MS": "1800000",
    "ENABLE_TOOL_SEARCH": "0",
    "ANTHROPIC_BASE_URL": "https://gov.genai-api.jpl.nasa.gov/sub-id-djbyrne-timecard-govcloud",
    "ANTHROPIC_MODEL": "us-gov.anthropic.claude-sonnet-4-5-20250929-v1:0"
  }
}

Session Information

• Project: /Users/dj_pastlives/2026_genAI/claude/20260331_pdf_and_plantuml
• Session occurred: 2026-03-31

Contact

• User: djbyrne
• Organization: JPL (Jet Propulsion Laboratory)

---

Note: This issue was discovered and documented with assistance from Claude during an active debugging session where we attempted to diagnose the problem using non-bash tools.

[github-actions]

Found 3 possible duplicate issues:

1. Claude Code CLI Bug Report: Bash Tool Returns No Output on macOS 26 #19663
2. Bash tool returns exit code 1 with no stdout/stderr on CachyOS (Arch Linux) #41124
3. [BUG] Claude unable to run any bash commands #32778

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

[djbyrne17]

It's not just the output; bash commands are not executing at all. Snippet of session below.

⏺ Bash(pwd > /Users/dj_pastlives/2026_genAI/claude/20260331_pdf_and_plantuml/test_output.txt)
⎿  (No output)

Read 1 file (ctrl+o to expand)

⏺ No, the workaround doesn't work. The bash commands appear to complete but they're not actually
executing - the redirected output files aren't being created at all.

This is an important finding: bash commands aren't just failing to capture stdout, they're not
executing at all. The "completed with no output" message is misleading - it should probably say "no
execution" or show an error.

This makes the bug more severe than we initially thought. It's not just a stdout capture issue -
the bash subprocess isn't executing the commands at all.

[djbyrne17]

In addition to seeing this on macOS Tahoe 26.3.1, I have the same problem in a docker environment on linux
Linux 4.18.0-553.72.1.el8_10.x86_64 #1 SMP Sat Aug 23 20:13:38 EDT 2025 x86_64 x86_64 x86_64 GNU/Linux
but not on the same linux box outside of docker.

[latannon]

Hi, I a m facing the same issue on Windows 11 too (with Git Bash)

[itsuitsuki]

same issue on windows 11 too with git bash

[qingshu-ui]

Hey, I kind of know what's going on with this.

You need to set the system variable CLAUDE_CODE_GIT_BASH_PATH

• You need to provide D:\Programs\Git\bin\bash.exe instead of D:\Programs\Git\git-bash.exe
• DO NOT D:\Programs\Git\git-bash.exe

Here's the final outcome:

[djbyrne17]

You need to set the system variable CLAUDE_CODE_GIT_BASH_PATH

On the macOS or linux/docker platforms where I'm seeing the problem, CLAUDE_CODE_GIT_BASH_PATH is not relevant. I hope it helps someone else.