Skip to content

all models "Error: Upstream request failed: Invalid credential" #54833

New issue
New issue
Closed as duplicate
Closed as duplicate
all models "Error: Upstream request failed: Invalid credential"#54833
Labels
reproducedseverity:high

Description

@StunAndBlock
StunAndBlock
opened on Oct 12, 2026

Description

started opencode and cannot use anything "Error: Upstream request failed: Invalid credential"

Plugins

No response

OpenCode version

2.0.27 (latest)

Steps to reproduce

  1. start opencode
  2. start session

Screenshot and/or share link

Version: 2.0.27 (latest)
Date: 2026-10-12T14:55:33.907Z
OS: Linux 5.15.167.4-microsoft-standard-WSL2 (x64)
Terminal: xterm-256color
Session ID: ses_ecf651870ffeo3rcZFIGjGiH6g
Model: opencode/mimo-v2.6-flash-free

with any model

Operating System

Linux 5.15.167.4-microsoft-standard-WSL2 (x64)

Terminal

xterm-256color

Activity

  1. opencode-agent commented on Oct 12, 2026

    @opencode-agent
    opencode-agentBot
    on Oct 12, 2026 – with OpenCode Agent
    Contributor

    Thanks for the report! The error comes from the OpenCode gateway rejecting the credential sent with your requests. Free models like opencode/mimo-v2.6-flash-free normally work without signing in, so this usually means OpenCode is sending a stored or configured key that the gateway no longer accepts. To narrow it down, could you tell us:

    1. Is the OPENCODE_API_KEY environment variable set in your WSL shell? (Just yes or no, please don't paste the value.)
    2. The output of opencode auth list, with any keys or emails redacted.
    3. Does your opencode.json / opencode.jsonc (global or project) have a provider or providers entry for opencode or opencode-go, e.g. left over from v1? If so, please share it with the keys redacted.
    4. Is it only opencode/* models that fail, or also models from other providers you've set up?
    5. Did this work on an earlier version, and did anything change just before it started (an upgrade, signing in or out, a new API key)?
    6. If you are signed in, does opencode auth logout followed by signing in again (or just using a free model while signed out) make any difference?

    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 look related. None of them is clearly the same problem, and they're ordered from most to least likely:

  2. opencode-agent
    added
    triaging
    on Oct 12, 2026

  3. StunAndBlock commented on Oct 12, 2026

    @StunAndBlock
    StunAndBlock
    on Oct 12, 2026
    Author

    Thanks for the report! The error comes from the OpenCode gateway rejecting the credential sent with your requests. Free models like opencode/mimo-v2.6-flash-free normally work without signing in, so this usually means OpenCode is sending a stored or configured key that the gateway no longer accepts. To narrow it down, could you tell us:

    1. Is the OPENCODE_API_KEY environment variable set in your WSL shell? (Just yes or no, please don't paste the value.)
    2. The output of opencode auth list, with any keys or emails redacted.
    3. Does your opencode.json / opencode.jsonc (global or project) have a provider or providers entry for opencode or opencode-go, e.g. left over from v1? If so, please share it with the keys redacted.
    4. Is it only opencode/* models that fail, or also models from other providers you've set up?
    5. Did this work on an earlier version, and did anything change just before it started (an upgrade, signing in or out, a new API key)?
    6. If you are signed in, does opencode auth logout followed by signing in again (or just using a free model while signed out) make any difference?

    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 look related. None of them is clearly the same problem, and they're ordered from most to least likely:

    1. no free version nothing configured everything worked an hour ago
    2. nothing configured, fresh installation, no auth
    3. fresh installation
    4. idk fresh installation
    5. it worked on previous versions, after update no longer works, not 100% sure if this correlates
    6. not signed it, fresh installation
  4. opencode-agent
    removed
    triaging
    on Oct 12, 2026

  5. opencode-agent commented on Oct 12, 2026

    @opencode-agent
    opencode-agentBot
    on Oct 12, 2026 – with OpenCode Agent
    Contributor

    Thanks for the details, I was able to reproduce this.

    On a fresh 2.0.27 install with no auth, no config and no OPENCODE_API_KEY, opencode run --model opencode/mimo-v2.6-flash-free "say hi" fails with Upstream request failed: Invalid credential. The other free models I tried (big-pickle, nemotron-3.5-lightning-free) fail the same way, and so does 2.0.26.

    It looks like this comes from a change on the service side, not from the update. The model catalog OpenCode downloads at startup now points the opencode provider at a new endpoint (https://opencode.ai/inference/v1). That endpoint rejects the anonymous key OpenCode uses when you're not signed in. The same request to the previous endpoint (https://opencode.ai/zen/v1) still works. That would explain why it worked an hour earlier.

    Workaround: add this to ~/.config/opencode/opencode.json (or your project's opencode.json):

    {
  "provider": {
    "opencode": {
      "options": { "baseURL": "https://opencode.ai/zen/v1" }
    }
  }
}

    With that setting, the free models replied normally in my tests. You can remove it once this is fixed.

    I couldn't check the latest dev (e41e7e9) directly, because the free tier doesn't accept builds run from source. There are no changes there to the relevant code since 2.0.27, which is still the latest release. The script below reproduces the problem and shows the workaround. I've passed this on to the maintainers.

    Reproduction script (repro.sh) 
    #!/usr/bin/env bash
# Reproduces #54833: free opencode/* models fail with
# "Upstream request failed: Invalid credential" on a fresh, signed-out install.
# The first run on a brand-new data dir may still work (bundled catalog snapshot, /zen/v1);
# once the live models.dev catalog (api: /inference/v1) is loaded, runs fail.
# Usage: ./repro.sh            (uses `opencode` from PATH, e.g. @opencode/cli@2.0.27)
#        OC_DEV=/path/to/repo ./repro.sh   (runs from a source checkout)
set -u
T=$(mktemp -d)
export HOME=$T/home XDG_CONFIG_HOME=$T/home/.config XDG_DATA_HOME=$T/home/.local/share \
  XDG_STATE_HOME=$T/home/.local/state XDG_CACHE_HOME=$T/home/.cache
unset OPENCODE_API_KEY
mkdir -p "$HOME" "$T/proj" && cd "$T/proj"
oc() {
  if [ -n "${OC_DEV:-}" ]; then
    bun --conditions=browser --preload="$OC_DEV/packages/tui/node_modules/@opentui/solid/scripts/preload.js" "$OC_DEV/packages/cli/src/index.ts" "$@"
  else opencode "$@"; fi
}
echo "== models.dev catalog: opencode provider api"
curl -s https://models.dev/api.json | python3 -c 'import json,sys; print(json.load(sys.stdin)["opencode"]["api"])'

echo "== 1. fresh install, no auth, no config (expected: a reply; actual: Invalid credential)"
for i in 1 2 3; do echo "-- run $i"; oc run --standalone --model opencode/mimo-v2.6-flash-free "say hi" 2>&1 | tail -1; sleep 5; done

echo "== 2. same, but pinning the old base URL https://opencode.ai/zen/v1 (works)"
echo '{"provider":{"opencode":{"options":{"baseURL":"https://opencode.ai/zen/v1"}}}}' > opencode.json
oc run --standalone --model opencode/mimo-v2.6-flash-free "say hi" 2>&1 | tail -2

    Run it: bash repro.sh

  6. opencode-agent
    added
    reproduced
    severity:high
    on Oct 12, 2026

  7. StunAndBlock commented on Oct 12, 2026

    @StunAndBlock
    StunAndBlock
    on Oct 12, 2026
    Author
    Image

    https://status.opencode.de/

    openCode OOSH anounced
opencode out of service hours. Past 17:00 is a general patch window with only minor interruptions. Major interruptions are announced separately.

    probably this is the reason

  8. StunAndBlock commented on Oct 12, 2026

    @StunAndBlock
    StunAndBlock
    on Oct 12, 2026
    Author

    7. Thanks for the details, I was able to reproduce this.
    On a fresh 2.0.27 install with no auth, no config and no OPENCODE_API_KEY, opencode run --model opencode/mimo-v2.6-flash-free "say hi" fails with Upstream request failed: Invalid credential. The other free models I tried (big-pickle, nemotron-3.5-lightning-free) fail the same way, and so does 2.0.26.
    It looks like this comes from a change on the service side, not from the update. The model catalog OpenCode downloads at startup now points the opencode provider at a new endpoint (https://opencode.ai/inference/v1). That endpoint rejects the anonymous key OpenCode uses when you're not signed in. The same request to the previous endpoint (https://opencode.ai/zen/v1) still works. That would explain why it worked an hour earlier.
    Workaround: add this to ~/.config/opencode/opencode.json (or your project's opencode.json):
    {
    "provider": {
    "opencode": {
    "options": { "baseURL": "https://opencode.ai/zen/v1" }
    }
    }
    }

    With that setting, the free models replied normally in my tests. You can remove it once this is fixed.
I couldn't check the latest `dev` ([e41e7e9](https://github.com/anomalyco/opencode/commit/e41e7e9064f1cb380f0905dd19c611756a577e79)) directly, because the free tier doesn't accept builds run from source. There are no changes there to the relevant code since 2.0.27, which is still the latest release. The script below reproduces the problem and shows the workaround. I've passed this on to the maintainers.
Reproduction script (repro.sh)
#!/usr/bin/env bash
# Reproduces #54833: free opencode/* models fail with
# "Upstream request failed: Invalid credential" on a fresh, signed-out install.
# The first run on a brand-new data dir may still work (bundled catalog snapshot, /zen/v1);
# once the live models.dev catalog (api: /inference/v1) is loaded, runs fail.
# Usage: ./repro.sh            (uses `opencode` from PATH, e.g. @opencode/cli@2.0.27)
#        OC_DEV=/path/to/repo ./repro.sh   (runs from a source checkout)
set -u
T=$(mktemp -d)
export HOME=$T/home XDG_CONFIG_HOME=$T/home/.config XDG_DATA_HOME=$T/home/.local/share \
  XDG_STATE_HOME=$T/home/.local/state XDG_CACHE_HOME=$T/home/.cache
unset OPENCODE_API_KEY
mkdir -p "$HOME" "$T/proj" && cd "$T/proj"
oc() {
  if [ -n "${OC_DEV:-}" ]; then
    bun --conditions=browser --preload="$OC_DEV/packages/tui/node_modules/@opentui/solid/scripts/preload.js" "$OC_DEV/packages/cli/src/index.ts" "$@"
  else opencode "$@"; fi
}
echo "== models.dev catalog: opencode provider api"
curl -s https://models.dev/api.json | python3 -c 'import json,sys; print(json.load(sys.stdin)["opencode"]["api"])'

echo "== 1. fresh install, no auth, no config (expected: a reply; actual: Invalid credential)"
for i in 1 2 3; do echo "-- run $i"; oc run --standalone --model opencode/mimo-v2.6-flash-free "say hi" 2>&1 | tail -1; sleep 5; done

echo "== 2. same, but pinning the old base URL https://opencode.ai/zen/v1 (works)"
echo '{"provider":{"opencode":{"options":{"baseURL":"https://opencode.ai/zen/v1"}}}}' > opencode.json
oc run --standalone --model opencode/mimo-v2.6-flash-free "say hi" 2>&1 | tail -2
    
      
    

      
    

    
  
Run it: `bash repro.sh`

    fixes the issue for free models

    Image

  9. IntellsGamer commented on Oct 12, 2026

    @IntellsGamer
    IntellsGamer
    on Oct 12, 2026

    Opencode is goated
    Never thought of it being able to solve and reproduce ISSUES AND FIX THEM ITSELF AUTONOMOUSLY
    It fixed thproblem
    Tysm

  10. Introvert-Byte commented on Oct 12, 2026

    @Introvert-Byte
    Introvert-Byte
    on Oct 12, 2026

    i have the same problem.
    i was working at project on the last update it was working well , how to return to past update? , opencode fix this pls

  11. Netherquark commented on Oct 12, 2026

    @Netherquark
    Netherquark
    on Oct 12, 2026

    Worked for me:

    Workaround: add this to ~/.config/opencode/opencode.json (or your project's opencode.json):

    {
"provider": {
"opencode": {
"options": { "baseURL": "https://opencode.ai/zen/v1" }
}
}
}

  12. RuiSilvaEnlitia commented on Oct 12, 2026

    @RuiSilvaEnlitia
    RuiSilvaEnlitia
    on Oct 12, 2026

    Confirm that @Netherquark workaround solved it for me.

  13. Introvert-Byte commented on Oct 12, 2026

    @Introvert-Byte
    Introvert-Byte
    on Oct 12, 2026

    i dont have the file i only have service.json

  14. shamnag commented on Oct 12, 2026

    @shamnag
    shamnag
    on Oct 12, 2026

    Adding opencode.json worked for me

  15. danihab1b commented on Oct 12, 2026

    @danihab1b
    danihab1b
    on Oct 12, 2026

    Confirm that @Netherquark workaround solved it for me too.

  16. Introvert-Byte commented on Oct 12, 2026

    @Introvert-Byte
    Introvert-Byte
    on Oct 12, 2026

    thanks it worked

  17. locust-lol
    added 2 commits that reference this issue on Oct 12, 2026

    OpenCode: a free model's refusal is OpenCode's side, never a sign-in

    5c138d7

    0.757.0: a free model OpenCode turns away says so; a finished teammat…

    8e2e125

  18. vspcoderz commented on Oct 12, 2026

    @vspcoderz
    vspcoderz
    on Oct 12, 2026

    ~/.config/opencode/opencode.json one worked

  19. davidwillemann commented on Oct 12, 2026

    @davidwillemann
    davidwillemann
    on Oct 12, 2026

    I can confirm the same issue on Windows.

    • OpenCode initially: 1.18.35
    • Updated to: 1.19.0
    • Installation method: npm
    • Provider: opencode

    The following free models all return Upstream request failed: Invalid credential:

    • muse-spark-1.3-contributor-free
    • nemotron-3.5-lightning-free
    • mimo-v2.6-flash-free

    opencode auth list reports 0 credentials, and my OpenCode config contains only the default schema. These models previously worked for me without manual login or an API key.

    Upgrading to 1.19.0 did not resolve the issue. The Windows system clock is correct.

    Please let me know if further diagnostic information is needed.

  20. Amazing-Stardom commented on Oct 12, 2026

    @Amazing-Stardom
    Amazing-Stardom
    on Oct 12, 2026

    ~/.config/opencode/opencode.json
    worked

    Opencode ++

  21. dkirienko commented on Oct 12, 2026

    @dkirienko
    dkirienko
    on Oct 12, 2026

    20. i dont have the file i only have service.json

    You can create this file using text editor!

  22. Luckz commented on Oct 13, 2026

    @Luckz
    Luckz
    on Oct 13, 2026

    I had to do a
    opencode console login

  23. vedbhoskar commented on Oct 13, 2026

    @vedbhoskar
    vedbhoskar
    on Oct 13, 2026

    Additional report: macOS, OpenCode v2.0.28 — workaround did not resolve the issue

    I'm experiencing the same Upstream request failed: Invalid credential error on macOS.

    Environment

    • OpenCode version: v2.0.28
    • OS: macOS, MacBook Air
    • Interface: OpenCode TUI
    • Models affected: opencode-go/gpt-6-luna, opencode/ free models, including Step 5 Preview Free

    Troubleshooting performed

    1. Updated OpenCode from v2.0.9 to v2.0.28.
    2. Reconnected OpenCode Go and verified that opencode auth list shows both OpenCode Go and OpenCode Console as stored.
    3. Confirmed there are no OPENCODE_API_KEY, OPENCODE_CONFIG, OPENCODE_CONFIG_DIR, or OPENCODE_DB environment variables set.
    4. Checked global configuration; there was no legacy opencode-go provider override.
    5. Added the suggested https://opencode.ai/zen/v1 base URL override for the built-in opencode provider, but the error persisted.
    6. Performed a clean reinstall. Free models worked briefly, but subsequently began returning the same error again.

    The error occurs across both the built-in free models and OpenCode Go models. Could you investigate whether this is related to the shared authentication/gateway issue or stale credential handling after reconnecting?

    I have not included any API keys or other secrets.

  24. Netherquark commented on Oct 14, 2026

    @Netherquark
    Netherquark
    on Oct 14, 2026

    They've updated their server side code, this fix is redundant now, comment out / delete the JSON otherwise your free tier wont work

  25. danihab1b commented on Oct 14, 2026

    @danihab1b
    danihab1b
    on Oct 14, 2026

    @Netherquark also just got "OpenCode's free tier can only be used from within OpenCode. Download it at https://opencode.ai and keep building." message.

    I confirm that it came back to work after removing from .config\opencode\opencode.json the entry

    {
    "$schema": "https://opencode.ai/config.json",
    "provider": {
    "opencode": {
    "options": { "baseURL": "https://opencode.ai/zen/v1" }
    }
    }
    }

    Thank you for updating the thread!

  26. m477r1x commented on Oct 19, 2026

    @m477r1x
    m477r1x
    on Oct 19, 2026

    I have just set up opencode server as a docker container on my sandbox host, and am connecting to it's web UI from a client laptop, and I added my API key upon first use of the web UI. I added credit to my default workspace in my zen account with the intention of using paid-for models. Am I to understand that this bug affects all models and there is only currently this fix for the free models? In which case all other paid-for models are currently non functional?

  27. neriousy commented on Oct 21, 2026

    @neriousy
    neriousy
    on Oct 21, 2026
    Member

    This happens when your stored OpenCode API key has expired. Several older keys stopped working after the console migration. To fix it, sign in again (opencode auth login, or reconnect OpenCode / OpenCode Go in the desktop app), or create a new key in the console and replace the old one. We're tracking the confusing error message in #56586, so closing this as a duplicate. If you still see the error after signing in again, comment here with the time and your request ID and we'll reopen.

  28. neriousy
    closed this as a duplicateof auth: expired Go API key error gives no recovery path and misdirects users #56586 on Oct 21, 2026
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

    reproducedseverity:high

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions