[BUG] Bash tool produces no stdout/stderr on Windows (working directory: C:\Projects\version)

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?

Description: Bash commands execute with exit code 0 but produce no output to stdout or stderr.

Actual Behavior
Tool result shows "(Bash completed with no output)" with no stdout or stderr, regardless of the command

What Should Happen?

1. Expected Behavior:

Command output is displayed (stdout/stderr)

Error Messages/Logs

Logs/Errors:
  - No error messages; commands silently produce no output

Steps to Reproduce

Steps to Reproduce:

1. Open Claude Code with working directory C:\Projects\version
2. Run a simple Bash command via the Bash tool, e.g.:

• echo "Testing Bash output"
• ls -la
• pwd

1. Observe the result

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

Claude 4.5

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

Environment:

• OS: Windows 11 Enterprise 10.0.26100
• Working Directory: C:\Projects\version
• Shell: bash (Git Bash)
• Model: Claude Haiku 4.5

I know there other similar bugs to this issue and I did the fix but it did not fix the issue.

1. [BUG] #62019
2. [[BUG] Bash commands produce no output on Windows 11 · Issue #62970 · anthropics/claude-code](https://github.com/anthropics/claude-code/issues/62970) 62970
3. Bash tool returns empty output when executing shell script files on Windows (MINGW64) #18748

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

Workaround:

I identified that the issue was not related to directory structure — the Bash tool's inability to produce output
persists regardless of working directory. As a temporary workaround, we executed ClaudePM checkin commands directly in
the Git Bash terminal instead of through the Claude Code Bash tool. Commands run identically in Git Bash produce full
stdout/stderr output with no issues. This suggests the problem is isolated to how the Bash tool is configured or
sandboxed within Claude Code on Windows, not a shell or command syntax issue.

---
Note: This is honest about what we did (worked around it, didn't fix it).