{"version":"2.1.299","anchor":"subagent-web-fetch-permission-denials-now-give-a-do-not-ret","canonical_anchor":"subagent-web-fetch-permission-denials-now-give-a-do-not-ret","heading":"Subagents told not to retry when a web fetch is not approved","tier":"notice","area":"Subagents","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/subagent-web-fetch-permission-denials-now-give-a-do-not-ret","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Subagents told not to retry when a web fetch is not approved\n\nWhen a subagent's web page fetch is not approved, it is now told not to retry and to report the blocked address\n\n**What**\n\nA subagent is a helper Claude Code starts to work on part of a task. When a subagent uses `WebFetch` to read a web page, you may be asked to approve it. If that request ends any way other than approval (it times out, expires or is denied), the subagent now gets a message written for it. The message tells it not to retry, to carry on without the page, and to report the blocked web address in its findings. Before, subagents got the same wording as the main conversation.\n\n**Why**\n\nThis stops subagents trying the same fetch again and again when there is no way to ask you about it.\n\n- Area: Subagents\n- Names: `WebFetch`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}