{"version":"2.1.232","anchor":"web-fetching-can-be-routed-through-a-built-in-agent","canonical_anchor":"web-fetching-can-be-routed-through-a-built-in-agent","heading":"Web fetching can be routed through a built-in agent","tier":"soon","area":"Web Fetch","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/web-fetching-can-be-routed-through-a-built-in-agent","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Web fetching can be routed through a built-in agent\n\nFetches can be handed to a dedicated agent, but the server flag defaults off.\n\n**What**\n\nInstead 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.\n\n**Details**\n\n- When active, a hook that denies a fetch gets extra guidance explaining that web pages can only be fetched through that agent.\n- Structured output from the subagent can carry a record of files the harness saved from the fetch.\n\n**Evidence**\n\n`CLAUDE_CODE_WEB_FETCH_AGENT`\n\n- Flag `tengu_clever_orbit`: Off in both readings (read for one account on one subscription tier against v2.1.232; this account: off, anonymous baseline: off, compiled default: off) 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.\n- Area: Web Fetch\n- Names: `CLAUDE_CODE_WEB_FETCH_AGENT`, `CLAUDE_CODE_SIMPLE`\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}