Fetches can be handed to a dedicated agent, but the server flag defaults off.
The web-fetch agent needs CLAUDE_CODE_WEB_FETCH_AGENT or tengu_clever_orbit plus a capability, and the flag defaults off.
tengu_clever_orbit Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.232: on
These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.
Read once, for one account on one subscription tier, against v2.1.232. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
Instead of calling the WebFetch tool directly, Claude Code can hand fetches to a dedicated built-in agent. It is off unless CLAUDE_CODE_WEB_FETCH_AGENT is set or the tengu_clever_orbit server flag turns it on, and it additionally needs the allow_web_fetch capability, a non-coordinator session, CLAUDE_CODE_SIMPLE unset, and a subagent depth below the limit. The server flag defaults to off.
- When active, a hook that denies a fetch gets extra guidance explaining that web pages can only be fetched through that agent.
- Structured output from the subagent can carry a record of files the harness saved from the fetch.
CLAUDE_CODE_WEB_FETCH_AGENT
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.236
Web fetch agent switch moved into per-host state
Both mention fetch agent
-
v2.1.239
Data-loss-prevention blocks are marked separately from fetch failures
Both mention fetch