{"version":"2.1.269","anchor":"webfetch-permission-check-extracted-into-a-reusable-checkper","canonical_anchor":"webfetch-permission-check-extracted-into-a-reusable-checkper","heading":"WebFetch permission check extracted into a reusable checkPermissions function","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/webfetch-permission-check-extracted-into-a-reusable-checkper","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### WebFetch permission check extracted into a reusable checkPermissions function\n\nWebFetch's permission logic is now a reusable function that can re-check permissions after a redirect\n\n**What**\n\nThe `WebFetch` tool's permission check is now a standalone `checkPermissions` function rather than being computed inline once. When a fetch is redirected or denied for provenance reasons, the retry flow can now call `checkPermissions` again against the new URL (via `precheck`\/`ask` callbacks) before asking the user for permission a second time.\n\n**Why**\n\nThis lets `WebFetch` re-evaluate permission for the actual destination URL after a redirect, rather than only checking the originally requested URL.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}