Unclear It is not clear whether remembering approvals and retrying before asking also depend on the switch, or apply to everyone.
What
WebFetch is the tool Claude uses to read a web page. When it is not allowed to fetch a URL on its own, it asks you for permission. This prompt flow was reworked:
- Approved URLs are remembered while prompts are pending. Origins (the site part of a URL) are also remembered when your answer adds allow rules.
- A denial clears the remembered approvals.
- A request that waits behind another prompt and finds its URL or origin already approved is fetched again without asking (
served_without_prompt). - Earlier prompts left unanswered shorten the next prompt's timeout. A request can end as
expired_in_linewhen waiting in the queue uses up its time, and the model is told: "The user did not answer an earlier permission request in time, so the request for this URL was not sent to them." The model is told to ask the user to include the URL. - With
tengu_orderly_lanterntrue, prompts are serialised through a lock (s.acquire), so only one is shown at a time. With it false, the new outcome handling exists but nothing is serialised. The compiled fallback is false, and nothing has been read about this gate yet.
Before, there was a single prompt with a fixed timeout, outcomes were limited to suppressed_*, timed_out, approved, denied and retry_denied, and nothing was remembered.
The stock WebFetch description captured under this release is unchanged.
Why
When Claude fetches several pages at once, you may see fewer stacked prompts and not be asked twice about a site you just approved. The one-at-a-time behaviour applies only where the flag is on.
tengu_orderly_lantern 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.292: 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.
Read once, for one account on one subscription tier, against v2.1.292. It isn't a statement about your account. What a flag value here can and cannot tell you
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.
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.
It is not clear whether remembering approvals and retrying before asking also depend on the switch, or apply to everyone.
New in this build: tengu_orderly_lantern