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

Claude Code v2.1.286 ·

WebFetch permission prompts record how long they waited and how many were open

WebFetch approval prompts now track wait time, how many prompts were showing, and whether a subagent raised them; a redirect bug is fixed

Group of 2 Under the hood Internal Changes
JSON All of v2.1.286
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
Web FetchArea: what it touches
Internal ChangesKind: in v2.1.286,
Internal ChangesSection of the release

Unclear It is unclear what uses this timing information.

What

WebFetch is the tool Claude Code uses to read web pages. When a fetch needs your approval, for example after a redirect to a different address, Claude Code asks you first. That ask now records more detail.

  • The result now carries a wait object with upAtRaise, upAtEnd and waitedMs: how many prompts were showing when the ask appeared, how many when it ended, and how long it waited.
  • A promptsUp counter tracks how many prompts are open at once.
  • The timed_out, approved and denied outcomes all carry this timing. Before, only the outcome and the denial message were kept.
  • The logged record also notes whether the ask came from a subagent, a helper agent that Claude Code starts to handle part of a task.
  • The redirect handling no longer mixes up the wrong values.

Why

Nothing about the prompt you see changes. The recorded timing shows how often these approval prompts pile up or wait behind each other, and the redirect fix makes the retry after a redirect use the right values.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is unclear what uses this timing information.

See this entry in the whole of v2.1.286 →

Feedback