Upstream request failed: Invalid credential #56646

Activity

1. opencode-agent commented on Oct 18, 2026

   

   opencode-agentBot

   on Oct 18, 2026 – with OpenCode Agent

   Contributor

   More actions

   Thanks for the report! The issue body is empty, and several different problems produce Upstream request failed: Invalid credential. To tell which one this is, could you share:

   1. Your OpenCode version (opencode --version), your OS, how you installed it, and whether you use the TUI, opencode run, the desktop app or something else.
   2. The provider and model you're using (e.g. opencode/... free models, opencode-go/..., or another provider), and whether every model fails or only some.
   3. How you're authenticated: the output of opencode auth list with keys and emails removed, whether OPENCODE_API_KEY is set (just yes or no, please don't paste the value), and any provider/providers entry in your opencode.json/opencode.jsonc (keys removed), especially a baseURL.
   4. What you did right before the error appeared and when it started (for example, after an update or after opencode auth login/logout).

   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 existing issues show the same error. They're ordered from most to least likely, so please check whether one of them already covers your problem:

   • all models "Error: Upstream request failed: Invalid credential" #54833: every model fails with this error on 2.0.27, even when not signed in. The cause was on the service side (a new inference endpoint). Some users fixed it by setting "provider": { "opencode": { "options": { "baseURL": "https://opencode.ai/zen/v1" } } } in opencode.json
   • baseURL ignored in recent versions #56064: a custom baseURL for opencode-go is ignored on 2.0.31, so requests still go to opencode.ai and fail with this error
   • providers: stale wellknown API-key wiring in the shared service sends an empty key after auth login/logout #54645: after opencode auth login/logout, the background service keeps sending an empty API key
   • desktop: "Connect OpenCode Go" runs Console sign-in instead of the Go API-key flow, then reports success and fails with "Invalid credential" #52243: in the desktop app, "Connect OpenCode Go" runs Console sign-in instead of the API-key flow, then fails with this error
   • 1.18 CLI: fresh 'opencode run' fails 'Invalid credential'; 'auth login opencode' fails 'fetch() URL is invalid' #50593: on the v1.18 CLI, a fresh opencode run fails with this error
2. opencode-agent

   added

   triaging

   on Oct 18, 2026
3. opencode-agent

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

   

   opencode-agentBot

   on Oct 21, 2026 – with OpenCode Agent

   Contributor

   More actions

   We're closing this for now. The issue only has a title, and we haven't heard back since we asked for your version, provider/model and auth setup. Several different problems cause Upstream request failed: Invalid credential, so we can't tell which one this is without those details.

   If you're still seeing it, these may help:

   • all models "Error: Upstream request failed: Invalid credential" #54833: every model fails with this error. Some users fixed it by setting "provider": { "opencode": { "options": { "baseURL": "https://opencode.ai/zen/v1" } } } in opencode.json
   • baseURL ignored in recent versions #56064: a custom baseURL for opencode-go is ignored
   • providers: stale wellknown API-key wiring in the shared service sends an empty key after auth login/logout #54645: an empty API key is sent after opencode auth login/logout

   If none of these match, reply here with your opencode --version, OS, provider and model, and what you did before the error. We can reopen it then, or you can open a new issue with those details.