[BUG] Search tool and Explore subagent always interrupted on WSL
Resolved 💬 5 comments Opened Mar 18, 2026 by GustavoSantosgfs Closed Apr 16, 2026
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?
The Search tool and Explore subagent are immediately interrupted every time they run on WSL. The message "Interrupted · What should Claude do instead?" appears after every Search or Explore call, making codebase searching completely broken.
What Should Happen?
Search and Explore should complete normally and return results, just like the Bash and Read tools do.
Error Messages/Logs
● Search(pattern: "boletim", path: "/home/gustavo/projects/comum/comum")
⎿ Interrupted · What should Claude do instead?
● Explore(Find menu reference)
⎿ Interrupted · What should Claude do instead?
Steps to Reproduce
- Install Claude Code on Windows with WSL (Ubuntu)
- Open Windows Terminal with Ubuntu/WSL profile
- Navigate to any project directory in the WSL filesystem (~/projects/...)
- Run: claude
- Ask any question that triggers a Search or Explore — e.g. "find all PHP files referencing boletim"
- Observe that every Search/Explore call is immediately interrupted
Claude Model
Opus
Is this a regression?
Yes, this worked in a previous version
Last Working Version
2.1.6
Claude Code Version
2.1.78
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Terminal.app (macOS)
Additional Information
- The Bash and Read tools work perfectly — only Search and Explore are affected
- Workaround: adding "NEVER use the Search tool or Explore subagent" to CLAUDE.md forces Claude to use bash grep instead, which works fine
- Downgrading to 2.1.6 alone does NOT fix it — the CLAUDE.md workaround is still needed on 2.1.6 too
- The interrupt happens instantly (5-12ms), suggesting the tool is aborted before it even runs
- Reproducible 100% of the time
This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗