Tech
How coding agents like Cursor quietly cut input costs by reusing KV states across turns — and what actually breaks the cache
Why my Cursor bill looked weird
I was poking around my usage dashboard in Cursor and noticed a metric I'd never paid attention to before: Cache Read .
Date Type Model Tokens
May 2, 06:50 PM Included auto 898K → Cache Read
May 2, 06:49 PM Included auto 1.4M → Cache Write
May 2, 06:47 PM Included auto 346.8K → Input / Output
Almost 99% of my input tokens for that session were served from cache. That sent me down a rabbit hole on w...
Read the full discussion on Dev.to
This article was aggregated from Dev.to. Click to join the conversation.
View on Dev.to
Related Trends in Tech
Two Secret Scanners Found 5 of 7 Exposed Credentials Each, but Missed Different Secrets
Tokenized Deposits Could Become Blockchain’s Killer Enterprise Use Case
Pressing Enter Doesn’t Make You a Creator
6 User Mindsets That Should Shape Your B2B Onboarding Strategy
How to Build a B2B Lead Generation Strategy Across Multiple Channels
What Would It Take to Prove That an AI Is Conscious?