[FEATURE] Don't re-prompt for approval on WebFetch cache hits

Resolved 💬 1 comment Opened May 26, 2026 by olejorgenb Closed Jun 27, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

When WebFetch is called twice with the same URL inside its 15-minute cache window, the response is served from cache (no new outbound request) — but the user is still prompted to approve the second call.

(Claude Code itself claims this cache exist - I have not verified)

The agent somtimes issues multiple narrow prompts against the same page during iterative exploration. Each re-fetch is a fresh LLM pass against cached content, which is cheap and safe, but the repeated approval prompts add friction and discourage the pattern.

This likely generalizes — any tool with a response cache should treat cache hits as not requiring re-approval.

Proposed Solution

If the response is served from cache, skip the permission prompt. The user already approved a fetch that produced that exact bytes-on-disk; there's nothing new to consent to.

Alternative Solutions

_No response_

Priority

Medium - Would be very helpful

Feature Category

Other

Use Case Example

_No response_

Additional Context

_No response_

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗