In short: Claude Code's WebSearch sends a plain-language query to a search tool that Anthropic runs on its own servers, which can run up to eight searches per call and returns only titles and URLs. Claude reads a page with a separate WebFetch call, the results come back encrypted, and the API charges $10 per 1,000 searches.
Lately I've been running Claude Opus on medium effort for almost everything. It's good enough for most of what I throw at it, and it's fast enough that I split one topic into several tasks and send each to its own session. It can range from a couple to a dozen of terminals side by side, and I'll admit I get some pride watching Claude clauding through the clauded tasks.

If you use the CLI too, you've seen the tool calls. One of them is WebSearch, and the queries in it are quite intriguing: oddly specific, sometimes phrased like a question a person would ask. It's clearly not a regex. So what is that parameter, and what happens after Claude writes it?
What does Claude send when it searches the web?
Well, it's just a (human) sentence. Claude writes it the way you'd type into a Google search box (ah, the good ol' days), and it's not parsed on your machine. From Claude Code's tools reference:
"WebSearch runs a query against Anthropic's web search backend and returns result titles and URLs. It doesn't fetch the result pages." (Claude Code docs)
First, one WebSearch call "may issue up to eight backend searches per call, refining the search internally before returning results." The query you see is only the start of the search. Second, it only returns titles and URLs!! When you see WebFetch right after a search, that's Claude opening one of the results to actually read it.

So what is "Anthropic's web search backend", and where does the search run?





Discussion
Open on GitHub ↗Comments live in GitHub Discussions through Giscus. Loading them connects to GitHub.