Skip to content

Opencode Go/Deepseek V4 flash #33473

Closed as not planned
Closed as not planned

Description

@tthoele89

Description

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.

What do I do next? Is this fixed in 1.17.9?

Plugins

No response

OpenCode version

1.17.8

Steps to reproduce

The bug has been tested in this Reddit thread:

https://www.reddit.com/r/opencodeCLI/comments/1u9grix/opencode_not_using_prompt_caching_with_deepseek/

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.

Screenshot and/or share link

Image Image

Operating System

Debian Trixie

Terminal

Tabby Terminal

Activity

  1. github-actions commented on Jun 23, 2026

    @github-actions
    Contributor

    This issue doesn't fully meet our contributing guidelines.

    What needs to be fixed:

    • 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:

    If you believe this was flagged incorrectly, please let a maintainer know.

  2. added
    needs:complianceThis means the issue will auto-close after 2 hours.
    and removed
    needs:complianceThis means the issue will auto-close after 2 hours.
    on Jun 23, 2026
  3. github-actions commented on Jun 23, 2026

    @github-actions
    Contributor

    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.

  4. axetroy commented on Jun 30, 2026

    @axetroy
    Image

    A simple self-introduction consumed 9K tokens.

  5. github-actions commented on Aug 30, 2026

    @github-actions
    Contributor

    To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions