Claude Code Freezes on Windows Running Bash Commands — find, ls, grep Hang

What this error means

Claude Code freezes every time it runs shell commands on Windows — find, ls, grep hang indefinitely is a Claude Code failure pattern reported for developers trying to fix claude code hanging when running shell commands (find, ls, grep) on windows. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

Claude Code freezes every time it runs shell commands on Windows. Commands like find, ls, grep, and ./gradlew hang indefinitely with no output. Only recovery is pressing x to kill the process. Verified on Windows with PowerShell.

Common causes

• Claude Code completely unusable on Windows; all shell commands hang indefinitely with no output; only recovery is pressing x to kill
• Claude Code freezes every time it runs shell commands on Windows. Commands like find, ls, grep, and ./gradlew hang indefinitely with no output. Only recovery is pressing x to kill the process. Verified on Windows with PowerShell.

Quick fixes

1. Confirm the exact error signature matches Claude Code freezes every time it runs shell commands on Windows — find, ls, grep hang indefinitely.
2. Check the Claude Code account, local tool state, and provider configuration involved in the failing workflow.
3. Compare the failing environment with a known working setup, then change one configuration value at a time.

Platform/tool-specific checks

• Verify the command, editor, extension, or API client that produced the error.
• Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
• Avoid deleting credentials, local model data, or project settings until the failing scope is clear.

Step-by-step troubleshooting

1. Capture the exact error message and the command, editor action, or request that triggered it.
2. Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
3. Review the source evidence below and compare it with your environment.
4. Apply one change at a time and rerun the smallest failing action.
5. Keep the working fix documented for the team or deployment environment.

How to prevent it

• Keep provider/tool configuration documented.
• Record non-secret diagnostics such as tool version, provider name, model name, and command path.
• Add a lightweight check before CI or production workflows depend on the tool.

Sources checked

• https://stackoverflow.com/questions/79908414

Evidence note: Claude Code freezes every time it runs shell commands on Windows. Commands like find, ls, grep, and ./gradlew hang indefinitely with no output. Only recovery is pressing x to kill the process. Verified on Windows with PowerShell.

Related errors

• Claude Code Windows shell hang
• Claude Code PowerShell freeze

FAQ

What should I check first?

Start with the exact Claude Code freezes every time it runs shell commands on Windows — find, ls, grep hang indefinitely text and the smallest action that reproduces it.

Can I ignore this error?

No. Treat it as a failed Claude Code workflow until the root cause is understood.

Is this guaranteed to have one fix?

No. The imported evidence supports the troubleshooting path above, but tool behavior can vary by account, plan, version, provider, and local configuration.

How do I know the fix worked?

Rerun the same command, editor action, or request. The fix is working when that action completes without Claude Code freezes every time it runs shell commands on Windows — find, ls, grep hang indefinitely.