Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The assumptions are so much worse than that:

> Methodology & assumptions: No caching

This is absolutely absurd. Claude code is of course using the cache (and this can be verified by looking at the traffic). It would be an incredibly stupid design to resend the whole input without a cache for every input, every tool use, etc..



By the way, there is caching (cache TTL is hort but during sessions it is active). E.g. Settings Status Config Usage Stats

  Session
  
  Total cost:            $15.59
  Total duration (API):  18m 3s
  Total duration (wall): 2h 13m 16s
  Total code changes:    232 lines added, 80 lines removed
  Usage by model:
       claude-opus-4-6:  1.5k input, 41.8k output, 26.4m cache read, 212.6k cache write ($15.59)


The no-caching is explained in the linked conversation. The numbers are from actual use.




Consider applying for YC's Fall 2026 batch! Applications are open till July 27.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: