Hacker News new | ask | show | jobs
by wren6991 5 days ago
The minimum fix would be to read it once per user turn, rather than once per tool call turn. As it is, if you tell an agent to update the file and it decides to do multiple edits on separate turns, you take a full cache miss per edit. If you're waiting 5-10 minutes on each miss (deep into a window, which is when you'd usually want to update notes) then you notice the difference.

The post is pretty explicit about it happening on every SSE turn, but I realise if I write something that is (to put it mildly) a rant, then I shouldn't expect people to read it charitably.

I also wouldn't mind being prompted before invalidating so I can decide whether to keep my cache, like most editors will prompt you if a file is edited externally.

1 comments

yeah, I think per user turn makes sense. But I am more inclining to only include it at session start.