Show HN: Agent Caching in Fiddler

Posted by zlatkov on Tuesday March 17, 2026 @01:19PM
from the show-hn dept.

https://www.telerik.com/blogs/stop-paying-same-answer-twice-agent-cache-fiddler-everywhere

Hi HN!

We’re the team behind Fiddler, and we recently built an Agent Cache feature.

It works by capturing an LLM request/response pair and, once caching is enabled, serving subsequent matching calls locally so duplicate requests never hit the provider.

It’s meant to reduce three pains that show up together in agent development: token cost, feedback-loop latency, and output non-determinism.

We’d love to hear your thoughts.

( 2 comments | 2 points | on HN )

Re:Show HN: Agent Caching in Fiddler by sachamorard on Wednesday March 18, 2026 @06:34AM (#47423846)

Cool idea. I have had rather a bad experience with semantic caching. Do you have benchmarks that demonstrate the effectiveness?

[ Parent | on HN ]

Re:Show HN: Agent Caching in Fiddler by teodorasgenova on Wednesday March 18, 2026 @11:51AM (#47427308)

This is dev‑time exact replay, not semantic caching. In early development, a lot of iteration seems to be about validating the flow rather than the quality of the model’s response.

Semantic caching feels more relevant later on, when reuse across similar inputs starts to matter. In dev-time context, an exact cache is often good enough. So that's what we looked to solve with Agent Cache.

I’m curious what's your experience with repeated llm calls during dev.

[ Parent | on HN ]