Slow Responses in Opencode Go #58748

Activity

1. opencode-agent commented on Oct 24, 2026

   

   opencode-agentBot

   on Oct 24, 2026 – with OpenCode Agent

   Contributor

   More actions

   Thanks for the report, and sorry OpenCode Go has been this slow for you. Slow responses can have quite different causes, so we need a few more details to tell whether the problem is in OpenCode or in the Go service. In your own words, briefly:

   • Model: which Go model(s) you used, as shown in /models (e.g. opencode-go/...), and whether all Go models are slow or only some.
   • What you did: an example of a simple task that took 30–60 minutes, i.e. the prompt and roughly how large the session/context was.
   • Where the time goes: does it sit waiting a long time before any output appears, stream text very slowly, or keep running many tool calls/steps? Do you see any errors or retries?
   • Comparison: if you have tried another provider or your own API key for the same model, is it fast there?
   • Logs: if you can, run opencode --print-logs --log-level DEBUG, reproduce one slow request, and attach the relevant excerpt (with timestamps). Please remove any API keys or personal information 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 you're done.

   These issues may be related, ordered from most to least likely:

   • opencode-go/deepseek-v4.1-flash: 21.7–178.2 s pre-header stalls at 97.97–99.97% cache hit rate across 241k–607k context (V2 2.0.32, request-level trace) #57849: long waits before the OpenCode Go service starts responding (opencode-go/deepseek-v4.1-flash), traced to the service side
   • **Title:** [OpenCode Go] All Go models generate at ~2 tokens/s after updating to v2.0.32 #56733: all Go models generating at about 2 tokens/s (closed without enough details)
   • Extremely Slow Response Time #56345: 40 minutes for a simple reply (closed without details)
   • Go plan: very slow responses and frequent EPROTO TLS handshake failures #58376: slow Go plan responses with TLS errors, but on v1
2. opencode-agent

   added

   triaging

   on Oct 24, 2026
3. opencode-agent

   closed this as not plannedon Oct 27, 2026
4. opencode-agent commented on Oct 27, 2026

   

   opencode-agentBot

   on Oct 27, 2026 – with OpenCode Agent

   Contributor

   More actions

   We haven't heard back with the details we asked for, so we're closing this issue for now. Without the Go model, an example task, and where the time goes (waiting before any output, slow streaming, or many tool steps), we can't tell whether the slowness comes from OpenCode 2.1.4 or from the OpenCode Go service.

   If this still happens, please reply here or open a new issue with that information and a opencode --print-logs --log-level DEBUG excerpt from one slow request, with keys and personal info removed. #57849 tracks a similar problem where the Go service is slow to start responding, so it may be worth following too.