Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.236entry #63

Claude Code v2.1.236 ·

Web fetch agent switch moved into per-host state

The web fetch agent decision moved per session; it still defaults off unless you set the variable.

Under the hood Notable No documentation found Internal Changes
JSON All of v2.1.236
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Web FetchArea: what it touches
Internal ChangesKind: in v2.1.236,
What probably matters to youSection of the release
What

The remembered answer for whether the web fetch agent is used now lives on a state object rather than a module variable. The decision is unchanged: CLAUDE_CODE_WEB_FETCH_AGENT wins if set, otherwise the tengu_clever_orbit gate decides, defaulting to off.

Evidence

V.CLAUDE_CODE_WEB_FETCH_AGENT ?? nt("tengu_clever_orbit", !1)

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Read from
Names in the bundleCLAUDE_CODE_WEB_FETCH_AGENT
Feature flag
tengu_clever_orbit Not enough to say

Nothing 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.236: off

Read once, for one account on one subscription tier, against v2.1.236. It isn't a statement about your account. What a flag value here can and cannot tell you

What has happened since
Flag reading moved The flag server now returns off for tengu_clever_orbit, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns nothing at all, having stopped carrying it for tengu_clever_orbit, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.

See this across every release →

See this entry in the whole of v2.1.236 →

Feedback