4 ms·
The response doesn't even make sense and appears to be written by AI. > The March 6 change makes Claude Code cheaper, not more expensive. 1h TTL for every requ
by hrimfaxi 6mo ago
The response doesn't even make sense and appears to be written by AI.
> The March 6 change makes Claude Code cheaper, not more expensive. 1h TTL for every request could cost more, not less
Feels very AI.
> Restore 1h as the default / expose as configurable? 1h everywhere would increase total cost given the request mix, so we're not planning a global toggle.
They won't show a toggle because it will increase costs for some unknown percentage of requests?
- stingraycharles 6mo agoSounds like a decision I would make when memory is expensive and you want to get rid of the very long (in time) tail of waiting 1h to evict cache when a session has stopped. There must be a better way to do this. The consumer option is the pricing difference. If they’d make cache writes the same price as regular writes, that would solve the whole problem. If you really want to push it, use that pricing only for requests where number of cache hits > 0 (to avoid people setting this flag without intent to use it), and you solved the whole issue.
- zozbot234 6mo agoMemory is expensive? If reads are as rare as they claim you can just stash the KV-cache on spinning disk.
- stingraycharles 6mo agoAren’t those latency sensitive though?