logoalt Hacker News

apt-apt-apt-aptyesterday at 5:35 PM3 repliesview on HN

I'm finding that unexpected cache rewrites cost me huge.

I have 1h cache TTL set, and do nothing to cause rewrite (response in time, no model/effort/tool changes).

At 400K tokens in, I'll write a message, and /usage shows only a small increase in cache write. On the next message, cache writes shows 800K, and by the end, I often hit 2M cache writes with no explanation.

This seems to happen when: using /btw, asking it to review code, other random times. Anyone know what's going on?


Replies

AlexErrantyesterday at 6:59 PM

To not answer your question, I have a claude stop hook that my status line uses to tell me how close my cache is to expiring https://pastebin.com/JLXUG16Q

_entirely_ vibecoded don't @ me.

Esrasyesterday at 10:47 PM

You may be running into a "known" bug with Claude Code: https://github.com/anthropics/claude-code/issues/63930

show 1 reply
radladyesterday at 7:40 PM

I have long suspected but not confirmed that /btw uses a lower tier model like Haiku.

Depending on how you're triggering reviews, you may be using a sub-agent?

show 1 reply