Skip to content

**Title:** [OpenCode Go] All Go models generate at ~2 tokens/s after updating to v2.0.32 #56733

Closed as not planned

Description

@Hemenguelbindi

Description

Description

I'm a paying OpenCode Go subscriber. After updating to v2.0.32, every Go model became extremely slow: generation speed is around 2 tokens/s, roughly 25x slower than before the update and far below what other Go users report (~50 t/s even with the recent throttling mentioned in community threads).

This is not limited to one model — every Go model I tried is affected. The client is effectively unusable for real work: simple prompts take minutes to complete.

Free Zen models also fail for me on the same version (OpenCode's free tier can only be used from within OpenCode), which may be related to #56701 / #56324, but my main concern is the paid Go plan, which I'm paying for and currently can't use.

Before the update (v): Go models responded at normal speed.
After the update (v2.0.32): ~2 t/s on all Go models.

Things I've checked:

  • Selected model is a Go model, not opencode/*-free (verified in /models)
  • Re-authenticated via /connect → OpenCode Go
  • Tested without VPN/proxy
  • Rolled back to v — result: <fast / still slow>

Possibly related: #52294 (slow after upgrade to v2), #33466 (Go-specific slowdowns), #56678 (Go Anthropic endpoint defaulting to dynamic reasoning).

Plugins

<none / list of plugins>

OpenCode version

2.0.32

Steps to reproduce

  1. Subscribe to OpenCode Go and log in via /connect
  2. Update OpenCode to v2.0.32
  3. Select any Go model, e.g. <model name>
  4. Send a simple prompt such as "hello" or "give me an overview of the project"
  5. Observe generation speed of ~2 tokens/s (first token after seconds, full reply after seconds/minutes)

Operating System

Windows 11

Terminal

Windows Terminal

Plugins

No response

OpenCode version

No response

Steps to reproduce

No response

Screenshot and/or share link

No response

Operating System

v2.0.32

Terminal

No response

Activity

  1. opencode-agent commented on Oct 18, 2026

    @opencode-agent
    Contributor

    Thanks for the report, and sorry Go has been so slow for you. Several parts of the issue still have template placeholders in them, so we can't yet tell whether OpenCode 2.0.32 is causing this or the Go service is slow. Could you fill in the following, in your own words?

    • Model(s): the exact Go model(s) you tried, as shown in /models (e.g. opencode-go/...)
    • Previous version: the last version where Go was fast for you, and how you installed OpenCode (npm, installer, scoop, etc.)
    • Rollback: does going back to that version make it fast again? You can test with npm i -g @opencode/cli@<version>. This is the most useful thing to know.
    • Other providers: on 2.0.32, is a non-Go provider (e.g. your own API key) also slow, or only Go?
    • Timings: for a simple prompt like "hello", roughly how long until the first token, and how long until the reply finishes?
    • Network: does this happen with no VPN or proxy?
    • Plugins: any plugins you have installed, or "none"
    • Logs: the log for a slow session, if you can get it. To make one, run opencode --print-logs --log-level DEBUG, reproduce the problem, and paste the relevant lines (remove any secrets first).

    You can reply here with the details or edit the issue. If you edit it, please also leave a comment saying you've updated it, so we know when you're done.

    These issues may be related. The list is ordered from most to least likely, so please check whether one of them already covers your problem:

  2. Hemenguelbindi commented on Oct 18, 2026

    @Hemenguelbindi
    Author

    Thanks for the quick reply! Here's what I have:

    • Model(s):
      • MiMo-V2.6-Pro (Go) — works, but extremely slow: ~2 tokens/s
      • DeepSeek-v4.1-flash (Go) — doesn't respond at all, returns error 500
    • Previous version: unfortunately I don't remember the exact version — I accepted the in-app update prompt. It was a 1.x/pre-2.0.32 release where Go models ran at normal speed. Installed via <npm / installer / scoop>.
    • Rollback: <not tested yet / tested with @opencode/cli@<version> — result: ...>
    • Other providers: I don't have another provider API key to compare with, so I can't test a non-Go provider right now.
    • Timings: very long — <first token after ~N s, reply finished after ~N min> on MiMo-V2.6-Pro.
    • Network: <reproduced with no VPN or proxy / I use a VPN — will retest without it>
    • Plugins:
    • Logs: will attach a debug log from opencode --print-logs --log-level DEBUG <below / shortly>.

    The 500 error on DeepSeek-v4.1-flash may be related to #56717 and #56713, which were opened today with the same error on v2.

  3. opencode-agent commented on Oct 18, 2026

    @opencode-agent
    Contributor

    Thanks for the details, that helps.

    The 500 on DeepSeek V4.1 Flash doesn't look specific to your setup. Several reports opened today show the same error, and people commenting on them think it's a problem on the service side:

    Please follow those issues for the 500 rather than this one.

    The ~2 tokens/s on MiMo-V2.6-Pro may be caused by the same service trouble rather than by OpenCode 2.0.32. Could you test again once the 500s above are resolved? Then reply with:

    • Speed: whether MiMo-V2.6-Pro is still around 2 tokens/s
    • Timings: for a simple "hello", roughly how many seconds until the first token, and how long until the reply finishes. Your comment still has the placeholders there.
    • Install method: npm, the installer or scoop
    • Network: whether it happens with no VPN or proxy
    • Plugins: any plugins you use, or "none"
    • Log: the log from opencode --print-logs --log-level DEBUG for a slow reply, with any secrets removed

    About the previous version: if it was a 1.x release, that is a separate implementation from v2, so the comparison only helps if you know the exact version. If you can find it, testing the same prompt on it would show whether the client makes a difference.

    You can reply here or edit the issue. If you edit it, please also leave a comment so we know you've updated it.

  4. opencode-agent commented on Oct 18, 2026

    @opencode-agent
    Contributor

    Thanks for the report. We can't act on this as filed: the issue and follow-up still contain template placeholders, with no previous version, timings, rollback result or logs. If you still see unusually slow generation on a current build, please open a new issue with real timings for a simple prompt and a --print-logs --log-level DEBUG excerpt.

  5. opencode-agent commented on Oct 21, 2026

    @opencode-agent
    Contributor

    We haven't heard back with the details we asked for, so we're closing this issue for now. We were waiting for a retest of MiMo-V2.6-Pro on OpenCode Go once the service-side HTTP 500 problems were resolved, along with timings and a debug log (opencode --print-logs --log-level DEBUG). Without those, we can't tell whether the slowness comes from OpenCode 2.0.32 or from the Go service.

    For the 500 on DeepSeek V4.1 Flash, please follow #56721 (and #56713 / #56717 / #56724).

    If Go models are still very slow for you now that the service has recovered, please reopen this or open a new issue with those details, and we'll look into it. Thanks!

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions