[BUG] Bash commands produce no output on Windows 11

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?

Platform: Windows 11 Enterprise 10.0.26100, Claude Code 2.1.116

Issue: Bash commands are executing but producing zero output in both the ! <command> prompt interface and the direct
Bash tool API. Even simple commands like echo "hello" or pwd that should always produce output return nothing.

Steps to reproduce:

1. Run ! echo "hello" in the Claude Code prompt
2. Run ! pwd in the Claude Code prompt
3. Observe: both return "(Bash completed with no output)" with no stdout or stderr

Expected behavior: echo "hello" should print "hello", pwd should print the current working directory

Environment details:

• Platform: win32-x64
• Shell: bash
• Package manager: winget
• Current working directory is a valid path: C:\Users\lucresia\version
• Directory is not a git repository

Additional context: This affects both the user-facing ! <command> interface and the internal Bash tool—suggesting the
issue is in the underlying bash execution layer, not the UI wrapper.
⎿ /feedback is not available when using Amazon Bedrock. Report issues at
https://github.com/anthropics/claude-code/issues

※ recap: Found that bash commands on this Windows system produce no output, even basic ones like echo. Next step is to
report this as a bug using /feedback. (disable recaps in /config)

What Should Happen?

Bash commands are executing but producing zero output in both the ! <command> prompt interface and programmatic tool
calls. Even simple commands like echo "hello" or pwd return nothing.

Steps to reproduce:

1. Run ! echo "hello" in Claude Code
2. Run ! pwd in Claude Code
3. Observe: "(Bash completed with no output)" with no stdout or stderr

****Expected behavior:

• echo "hello" → prints "hello"
• pwd → prints the current working directory****

Environment:

• Platform: Windows 11 Enterprise (10.0.26100)
• Claude Code: 2.1.116
• Backend: Amazon Bedrock
• Shell: bash
• Working directory: C:\Users\lucresia\version

Additional context:
This affects both the user-facing ! <command> interface and the internal Bash tool API, suggesting the issue is in the underlying bash execution layer, not the UI wrapper.

---
This looks like it could be a PATH issue or bash configuration problem specific to Bedrock on Windows. The GitHub
issue will get routed to the right team to debug.

Error Messages/Logs

Observe: "(Bash completed with no output)" with no stdout or stderr

Steps to Reproduce

Steps to reproduce:

1. Run ! echo "hello" in Claude Code
2. Run ! pwd in Claude Code
3. Observe: "(Bash completed with no output)" with no stdout or stderr

Using Claude Model:

Claude Haiku 4.5 (via Amazon Bedrock)

Full model ID: us.anthropic.claude-haiku-4-5-20251001-v1:0

Add that to the GitHub issue so the team knows the configuration.

Claude Model

Other

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

Claude Code: 2.1.116 - Backend: Amazon Bedrock - Shell: bash

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

Claude Haiku 4.5 (via Amazon Bedrock)

Full model ID: us.anthropic.claude-haiku-4-5-20251001-v1:0

Additional context:
This affects both the user-facing ! <command> interface and the internal Bash tool API, suggesting the issue is in the underlying bash execution layer, not the UI wrapper.