Skip to content

[BUG] "Upstream idle timeout exceeded" #28957

Description

@VENAXIS

I don't know what's causing it, but it seems to be coming from the session itself timing out when using the "writing-plans" skill.

OS: macOS Tahoe 26.5 (recently updated)
CPU: Apple M4
More info: "The upstream connection between the client and the model service idled out. This is an infrastructure timeout, not a model error. The model had finished gathering context and was about to produce output, but the connection dropped before the response could be transmitted."

Is this a server error for the model on OpenCode GO?

Image

Activity

  1. changed the title [-]"Upstream idle timeout exceeded"[/-] [+][BUG] "Upstream idle timeout exceeded"[/+] on May 23, 2026
  2. github-actions commented on May 23, 2026

    @github-actions
    Contributor

    Thanks for updating the issue! The OS info, error context, and details about the writing-plans skill are helpful. Your report now meets our contributing guidelines.

  3. RoyaltyInTraining commented on May 28, 2026

    @RoyaltyInTraining

    I also have the same issue with MiMo v2.5 Pro on openrouter. It has been happening for weeks now. Getting it to write large plans always triggers the timeout.

    Fedora Linux 44, KDE edition

  4. Wydady13 commented on Jun 8, 2026

    @Wydady13

    i also have same issue with Nemotron 3 Ultra Free High
    v1.16.2

  5. VincenzoUrso commented on Jun 8, 2026

    @VincenzoUrso

    confirm the issue with Nemotron 3 Ultra Free High

  6. ranaharoon3222 commented on Jun 10, 2026

    @ranaharoon3222

    i also have same issue with mimo pro

  7. joshuac-dev commented on Jun 10, 2026

    @joshuac-dev

    I am having the same issue with Qwen Coder Next

  8. cryptodappdeveloper commented on Jun 10, 2026

    @cryptodappdeveloper

    All Nemotron models i tried always ended up with "Upstream idle timeout exceeded" when the model trying to use "Writing command"

  9. aalzubidy commented on Jun 11, 2026

    @aalzubidy

    Same issue with DS4 Flash/Pro

  10. leonardocordeiro commented on Jun 12, 2026

    @leonardocordeiro

    same issue with Nemotron 3 Ultra Free High here

  11. rashidiansanawi commented on Jun 12, 2026

    @rashidiansanawi

    same issue but only with Nemotron 3 Ultra Free High. Mimo v2.5 free still okay. current workaround is asking them to write in smaller batches. v1.16.2. using ubuntu linux. terminal alacraty

  12. mansoorahmadhh commented on Jun 13, 2026

    @mansoorahmadhh

    I have this Issue with MiniMax M3 Opencode {"code":504,"message":"Upstream idle timeout exceeded","metadata":{"error_type":"timeout"}}

    OpenCode 1.17.4 - Macbook Pro Mx

  13. steinathan commented on Jun 13, 2026

    @steinathan

    having the issue with MiMo V2.5

    Image
  14. namcho commented on Jun 14, 2026

    @namcho

    same issue but only with Nemotron 3 Ultra Free High. Mimo v2.5 free still okay. current workaround is asking them to write in smaller batches. v1.16.2. using ubuntu linux. terminal alacraty

    This trick worked for me "small batch writing" for Nemotron 3 Ultra.

  15. Germanized commented on Jun 15, 2026

    @Germanized

    $ErrorActionPreference = "Stop"
    $chunkTimeoutMs = 2147483647
    $stamp = Get-Date -Format "yyyyMMdd-HHmmss"

    Close OpenCode processes if any are still alive.

    Get-Process -ErrorAction SilentlyContinue | Where-Object {
    $.ProcessName -like "opencode" -or
    ($(try { $
    .Path } catch { "" }) -like "opencode")
    } | Stop-Process -Force -ErrorAction SilentlyContinue

    Start-Sleep -Seconds 2

    Reset the bloated Desktop GUI store, but keep a backup.

    $desktopDir = Join-Path $env:APPDATA "ai.opencode.desktop"
    $store = Join-Path $desktopDir "opencode.global.dat"

    if (Test-Path $store) {
    Rename-Item -LiteralPath $store -NewName "opencode.global.dat.$stamp.bak"
    Write-Host "Backed up GUI store: opencode.global.dat.$stamp.bak"
    }

    Get-ChildItem -Path $desktopDir -Filter "opencode.global.dat.tmp-*" -ErrorAction SilentlyContinue |
    Remove-Item -Force -ErrorAction SilentlyContinue

    Create/update OpenCode global config for OpenRouter timeout.

    $cfgDir = Join-Path $env:APPDATA "opencode"
    $cfg = Join-Path $cfgDir "opencode.json"

    New-Item -ItemType Directory -Force -Path $cfgDir | Out-Null

    if (Test-Path $cfg) {
    Copy-Item -LiteralPath $cfg -Destination "$cfg.$stamp.bak" -Force
    $data = Get-Content -LiteralPath $cfg -Raw | ConvertFrom-Json
    } else {
    $data = [pscustomobject]@{}
    }

    function Set-Prop($obj, [string]$name, $value) {
    if ($obj.PSObject.Properties[$name]) {
    $obj.PSObject.Properties[$name].Value = $value
    } else {
    $obj | Add-Member -NotePropertyName $name -NotePropertyValue $value
    }
    }

    function Ensure-Obj($obj, [string]$name) {
    if (-not $obj.PSObject.Properties[$name] -or $null -eq $obj.PSObject.Properties[$name].Value) {
    Set-Prop $obj $name ([pscustomobject]@{})
    }
    return $obj.PSObject.Properties[$name].Value
    }

    Set-Prop $data '$schema' 'https://opencode.ai/config.json'
    $provider = Ensure-Obj $data 'provider'
    $openrouter = Ensure-Obj $provider 'openrouter'
    $options = Ensure-Obj $openrouter 'options'

    Set-Prop $options 'timeout' $false
    Set-Prop $options 'chunkTimeout' $chunkTimeoutMs

    $data | ConvertTo-Json -Depth 32 | Set-Content -LiteralPath $cfg -Encoding UTF8

    Write-Host "Done. OpenRouter chunkTimeout set to $chunkTimeoutMs ms."
    Write-Host "Restart OpenCode."

    This PS1 script slash chunk should help with the caching issues that makes the GUI feel really laggy especially for me and also the time out

  16. RenanOSX commented on Jun 16, 2026

    @RenanOSX

    same issue but only with Nemotron 3 Ultra Free High. Mimo v2.5 free still okay. current workaround is asking them to write in smaller batches. v1.16.2. using ubuntu linux. terminal alacraty

    This trick worked for me "small batch writing" for Nemotron 3 Ultra.

    Is not an actual fix but the prompt "Do the edits in small batches" does work as you mentioned, thanks!

  17. InfHorus commented on Jun 21, 2026

    @InfHorus

    I have the same issue, basically OpenRouter is unusable, never seen such unreliable provider, tried 10 differents models they all hit this very same error, I think for a "Router" they should at least make it usable for anything else than sending "hello world" to models.

  18. wasteofoxygen69 commented on Jun 24, 2026

    @wasteofoxygen69

    confirm the issue with Nemotron 3 Ultra Free High

    Same but even on default I get the same error. Also the continue in small baches doesn't really help much it seems.

  19. thimvanamersfoort commented on Jul 5, 2026

    @thimvanamersfoort

    Same issue here with GLM 5.2 on Openrouter. Very frustrating

  20. RenanOSX commented on Jul 9, 2026

    @RenanOSX

    To give more context to this issue, it does not seem to happen on the paid version (GO or Zen plans), only on the free tier models

  21. jimdawdy-hub commented on Jul 15, 2026

    @jimdawdy-hub

    Confirmed on Openrouter using GLM-5.2 (paid) via API plan. It's frequent and should be considered a blocker.
    OS: EndeavourOS Linux x86_64
    :+sssssssssso/. Host: HP Z640 Workstation -/ossssssssssssso/. Kernel: 7.0.14-zen1-1-zen
    -/+sssssssssssssssso+: Uptime: 3 days, 22 hours, 7 mins
    -:/+sssssssssssssssssso+/. Packages: 2524 (pacman) .://osssssssssssssssssssso++- Shell: bash 5.3.15
    .://+ssssssssssssssssssssssso++: Resolution: 1920x1080
    .:///ossssssssssssssssssssssssso++: DE: Plasma 6.7.1
    :////ssssssssssssssssssssssssssso+++. WM: kwin -////+ssssssssssssssssssssssssssso++++- Theme: Breeze-Dark [GTK2], Breeze [GTK3]
    ..-+oosssssssssssssssssssssssso+++++/ Icons: breeze-dark [GTK2/3]
    ./++++++++++++++++++++++++++++++/:. Terminal: konsole
    `:::::::::::::::::::::::::------`` CPU: Intel Xeon E5-2699 v4 (44) @ 2.879GHz
    GPU: NVIDIA GeForce RTX 5060 Ti
    Memory: 36146MiB / 80326MiB

  22. thimvanamersfoort commented on Jul 15, 2026

    @thimvanamersfoort

    I found when using the xhigh reasoning variant (GLM 5.2), this bug seems to happen much less often. Maybe this helps some of you!

  23. github-actions commented on Sep 15, 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