3 ms·
Long codex sessions lead to a lot of cached token hits, esp when you resume them after a few hours.
by letitgo12345 4mo ago
Long codex sessions lead to a lot of cached token hits, esp when you resume them after a few hours.
- consumer451 4mo agoI personally don't count cached hits as $used... Neither in my harnesses, nor in the LLM-enabled apps I create. A cached token cannot be counted 1:1 as to a non-cached token, that would be silly. Wait... when some Claude 5x/20x users say they are getting "$2000 of tokens for $100," does the 2k value include cached tokens, counted at the same $/token either way? We cannot be this dumb as a community, can we? I must be wrong/misunderstanding..
- SatvikBeri 4mo agoI'm a fairly moderate user, never hit any kind of usage limits, but I used 44 million cache create tokens and 1.5 billion cache read tokens, which ccusage estimates would have cost $990, and calculates the different categories separately.