{"version":"2.1.286","anchor":"webfetch-provenance-prompt-telemetry-gains-queue-and-subagen","canonical_anchor":"webfetch-provenance-prompt-telemetry-gains-queue-and-subagen","heading":"WebFetch permission prompts record how long they waited and how many were open","tier":"internal","area":"Web Fetch","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/webfetch-provenance-prompt-telemetry-gains-queue-and-subagen","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### WebFetch permission prompts record how long they waited and how many were open\n\nWebFetch approval prompts now track wait time, how many prompts were showing, and whether a subagent raised them; a redirect bug is fixed\n\n**Unclear.** It is not clear whether passing the open-prompt count to the approval prompt changes what you see.\n\n**What**\n\nWebFetch 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.\n\n- 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.\n\n- A `promptsUp` counter tracks how many prompts are open at once.\n\n- The `timed_out`, `approved` and `denied` outcomes all carry this timing. Before, only the outcome and the denial message were kept.\n\n- 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.\n\n- The redirect handling no longer mixes up the wrong values.\n\n**Why**\n\nNothing 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.\n\n- Area: Web Fetch\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}