Significant Pre-Execution Delay (~210s) When Calling Bash Tool on Windows

Description:

When using the Bash() tool within Claude Code on a Windows environment, I consistently observe a substantial delay (approximately 200-210 seconds) before the actual Bash command begins execution and before the permission prompt appears.

Steps to Reproduce:

1. On a Windows 10/11 system (with Git Bash installed and its path correctly added to environment variables).
2. Launch Claude Code from a PowerShell terminal (or a Git Bash tab within Windows Terminal).
3. Ask Claude Code to execute any simple Bash command, e.g.:

• Bash(echo "Hello")
• Bash(pwd)
• Bash(ls -la)

1. Observe that Claude Code displays Bash(...) Running... or Waiting... on the command line, and this state persists for about 200-210 seconds.
2. Only after this prolonged delay does the "Do you want to proceed?" permission prompt appear.
3. The Bash command then actually executes only after the permission is granted.

Expected Behavior:

• Bash commands should start executing immediately (or after a very brief setup time) upon being called.
• The permission prompt should appear instantly before command execution, not after a significant delay.

Actual Behavior:

• Every call to the Bash() tool, even for the simplest commands, consistently hangs for approximately 200-210 seconds before the command begins execution and before the permission prompt is displayed.
• This makes the Bash() tool virtually unusable on Windows due to the extreme waiting times for every single operation.

Potential Cause (Speculation):

I suspect this may be related to an underlying compatibility or process management issue within Claude Code when it attempts to launch and manage external Bash processes on the Windows platform. It appears to experience a long-term block or timeout while interacting with Windows process APIs.