Breaking Down Claude Code Costs: A Personal Analysis of 66 Sessions
claude reasoning
| Source: Dev.to | Original article
Claude Code bills reveal surprising spending patterns. Median sessions reuse only 24% of spend as cached context.
As we reported on May 30 in our article "Should we allow Claude Code write access to our Gitlab/Github/AzureDevOps/etc. projects, or just pro", the cost and efficiency of using Claude Code have been under scrutiny. A recent experiment has shed more light on where the money goes when using Claude Code. By parsing local logs of 66 real sessions, a user found that the median session only re-sends about 24% of its spend as cached context. However, when pooled, this number jumps to 60%, indicating that costs are concentrated in a few long sessions.
This breakdown matters because it helps developers and businesses understand the true cost of using Claude Code and make informed decisions about their budgets. With the rising popularity of AI coding tools, it's essential to have a clear picture of the expenses involved. The findings also highlight the importance of optimizing sessions to minimize unnecessary costs.
As the AI coding landscape continues to evolve, it will be interesting to watch how Claude Code and its competitors respond to these findings. Will they implement changes to reduce costs or provide more transparent pricing models? The recent leak of Claude Code's own full source code, as reported by Extremetech, may also lead to new developments and alternatives in the market. As we move forward, it's crucial to monitor the developments in AI coding tools and their implications for the tech industry.
Sources
Back to AIPULSEN