You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I upgraded to 1.17.8 and was developing all day. when I checked my usage, I am at 25%!! it seems that there were no cache hits, and apparently some kind of bug. I just had my opencode go subcription renew today, only to watch 25 percent disappear.
Every prompt I send costs 160–170K input tokens because the full conversation history gets re-sent each turn with no caching. Tested in a brand new empty folder — even "hello" costs ~8K tokens (that's OpenCode's fixed system prompt + tool definitions overhead, apparently normal). The real problem: after a long session there's zero cache reduction. No "cache read" field in the UI, no cost savings between turns.
DeepSeek V3/V4 supports native prompt caching so the model can do it. The issue seems to be OpenCode not sending cache_control in its API requests.
Steps to reproduce is empty — please describe what you were doing when you noticed the cache miss behavior (e.g., which model/provider configuration, session length, etc.)
OpenCode version is missing — please include the exact version (you mentioned 1.17.8 in the description, add it to the field)
Operating System and Terminal fields are empty — system info helps diagnose environment-specific issues
Please edit this issue to address the above within 2 hours, or it will be automatically closed.
This issue might be a duplicate of existing issues. Please check:
Thanks for updating the issue! It now includes a clear description, reproduction steps, version info, OS, terminal, and screenshots. Everything looks good — the compliance flag has been removed.
Activity
github-actions commentedon Jun 23, 2026
This issue doesn't fully meet our contributing guidelines.
What needs to be fixed:
Please edit this issue to address the above within 2 hours, or it will be automatically closed.
This issue might be a duplicate of existing issues. Please check:
If you believe this was flagged incorrectly, please let a maintainer know.
github-actions commentedon Jun 23, 2026
Thanks for updating the issue! It now includes a clear description, reproduction steps, version info, OS, terminal, and screenshots. Everything looks good — the compliance flag has been removed.
axetroy commentedon Jun 30, 2026
A simple self-introduction consumed 9K tokens.
github-actions commentedon Aug 30, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.