Claude Code allocates 96.8% of tokens to re-reading history, user input accounts for just 0.01%
claude
| Source: Dev.to | Original article
Claude Code spends most tokens re-reading history. User input accounts for a tiny fraction.
A recent analysis has shed light on how Claude Code allocates its tokens. The findings indicate that a staggering 96.8% of tokens are spent re-reading history, while a mere 0.01% is dedicated to user input. This discovery is significant as it highlights the potential for inefficiency in the system.
As we previously reported, Anthropic's Claude has been making waves in the coding community, with its ability to understand codebases, edit files, and run commands. However, this new information suggests that users may be wasting a substantial number of tokens due to the system's tendency to re-read history. This is not an isolated issue, as another user reported wasting 98.5% of their tokens on re-reading history, only to find that using the /clear command between tasks could significantly mitigate the problem.
Moving forward, it will be interesting to see how Anthropic addresses this issue and whether they will implement changes to optimize token allocation. Users can expect potential updates to the system, such as more efficient logging mechanisms or improved token management features. As the coding community continues to rely on tools like Claude Code, it is crucial to monitor developments and best practices to maximize the utility of these innovative technologies.
Sources
Back to AIPULSEN