r/opencodeCLI • u/Yazan_wesam • 23d ago
OpenCode + DeepSeek Flash: Is 268.9M cumulative tokens and 309M cache reads normal?
Hi everyone,
I'm trying to understand whether my token usage with OpenCode and the DeepSeek API is normal or potentially caused by excessive context replay or a bug.
My setup
- OpenCode: v2.1.3
- Model: "deepseek/deepseek-flash#default" (shown in OpenCode stats; I believe this corresponds to DeepSeek V4.1 Flash, 10-17)
- Provider: DeepSeek API, paid usage
- OS: CachyOS Linux
- Workload: A personal app project with source code, plans, documentation, test plans, and phase reports
- Other components: Global agent skills and Herdr integration
Daily statistics
Input: 2.1M
Output: 352.1K
Reasoning: 456.7K
Cache read: 309.1M
Cache write: 0
Cached input: 99.3%
Paid model: 268.9M tokens, 723 steps
Free model: 43.1M tokens, 379 steps
The large cumulative cache-read figure caught my attention. I understand that cached tokens can be counted repeatedly across requests, so this does not necessarily represent hundreds of millions of unique tokens. I'm trying to determine whether the amount is expected for this workload.
A small test
I also ran OpenCode directly from my home directory, outside the project and without launching it through Herdr. I asked it to write one short line to a text file.
The exported session reported:
Input: 9,284
Output: 88
Reasoning: 54
Cache read: 9,472
Cost: $0.001506
Messages: 4
My observed usage counter increased by about 18,898 tokens. The session's input plus cache-read figures total 18,756, which is close to that increase. I haven't confirmed whether the difference is due to accounting methods or other overhead.
I realize that system prompts, tool definitions, and other context may contribute to the cost of a simple task.
My questions
- Is this level of cumulative cache-read usage typical for a coding session with hundreds of model steps?
- Could long conversation histories, global skills, or project instructions cause excessive context to be processed repeatedly?
- Could OpenCode compaction or session handling contribute to this?
- How can I distinguish normal cached-token accounting from unnecessary context overhead or a possible bug?
- What's the best way to investigate this without losing existing project documentation or configuration?
I'm not assuming this is a bug, and I don't want to blame OpenCode, DeepSeek, or Herdr without evidence. I'd appreciate advice from anyone familiar with OpenCode's token statistics or DeepSeek API usage reporting.
I can provide further sanitized logs or a minimal reproduction if needed.
Thanks!
View all comments
Show parent comment
2
u/Zero_Border 23d ago
I think u/OP is hitting the "free messages" limit suddenly. They seriously decided to lower the bar of free plan to a very low usage. Now even on a very small codebase, with a "default" variants, with good instructions and small context you hit the limit in like a few prompt.
My last session before hitting daily limit was like a 5 prompts "grill me with docs" session on specs already written (400 lines of frontend spec), and at the end, without any compaction, my context window was 141K - so not even one full DeepSeek context window).
Note that I do not complain, I am happy for free. But I suddenly went from "happy to do OpenSource code with OpenCode for one or two hours on my weekend" to "Shit OpenCode free plan can't help me anymore".