[BUG] VSCode extension: Bash tool does not capture stdout (commands run in popup terminal window)

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?

When using Claude Code in the VSCode extension, the Bash tool executes commands correctly (exit codes are right, file writes work, git operations succeed) but stdout is never returned to Claude. The tool result always shows "Tool ran without output or errors" regardless of what the command prints.

Environment:

Claude Code: VSCode extension
OS: Windows 11
Shell: Git Bash (MINGW64)
What happens:

Each Bash command opens a separate terminal window briefly, shows output, then closes. That output is not piped back to Claude's context. This means:

echo "hello" # Returns nothing
git status # Returns nothing
git diff HEAD # Returns nothing
nonexistentcommand123 # Returns nothing (no error either)
Even stderr is swallowed — failed commands return no output at all.

Workaround:

Redirect to a file and use the Read tool:
git status > c:/Users/me/out.txt 2>&1

then Read the file

This works but adds friction to every shell operation.

Impact:

Every shell command that produces output requires a file-redirect workaround. This makes git operations, build output, test results, and type-check output all significantly more cumbersome to work with.

What Should Happen?

Expected behavior:

Stdout and stderr from Bash commands should be returned in the tool result, consistent with how the CLI version of Claude Code behaves.

Error Messages/Logs

Steps to Reproduce

echo "hello" # Returns nothing
git status # Returns nothing
git diff HEAD # Returns nothing
nonexistentcommand123 # Returns nothing (no error either)

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.63

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

_No response_