[BUG] web search not working (Did 0 searches in 7s)
Status Closed — not planned
Maintainer reply None cached
Activity 12 comments · opened Nov 10, 2025 · closed Feb 21, 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?
● Looking at the current state, I need to determine how to create vector indexes in Memgraph MAGE and then re-run the complete ingestion pipeline with all 537 chunks.
Let me first check the Memgraph MAGE documentation for vector index creation:
● Web Search("Memgraph MAGE vector index create procedure 2024")
⎿ Did 0 searches in 7s
What Should Happen?
I expected to have some search results
Error Messages/Logs
Steps to Reproduce
make claude code do a web search
Claude Model
Sonnet (default)
Is this a regression?
No, this never worked
Last Working Version
_No response_
Claude Code Version
2.0.36 (Claude Code)
Platform
Google Vertex AI
Operating System
Ubuntu/Debian Linux
Terminal/Shell
Other
Additional Information
_No response_
Showing cached comments. Read the full discussion on GitHub ↗
10 Comments
I got the same issue. Though I am using customized model from aws bedrock. Not sure if that is the reason.
I'm facing the same issue!
Every time I got:
⏺ Web Search("abc")
⎿ Did 0 searches in 220ms
I'm using Claude Code 2.0.50 with a custom model
Hi @acking-you ,
Are you using a custom model in Claude Code?
If that is the case, this behavior could be expected. For custom models you need to install an MCP to replace the Web Search tool. Typically the model vendor will provide the specific MCP for that particular model.
So if i am using claude code with litellm, the webseach will fail right?
I am using LiteLLM to proxy requests sent to the Claude model on AWS Bedrock, and I am currently being prompted that Web Search is not supported in Claude Code.
I use Minimax coding plan, facing the same problem
This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.
Closing for now — inactive for too long. Please open a new issue if this is still relevant.
the issue is still occurring
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.