[Upstream #234] Bug: Server fails to start with "No credentials configured" error despite successful OpenCode Go auth

[quangdang46]

Mirrored from upstream 1jehuang/jcode — Issue #234 by @wtry
Original state: open
Created: 2026-05-19T23:04:12Z · Updated: 2026-05-19T23:30:33Z
This issue is an auto-mirrored copy. Comments and edits here are local to quangdang46/jcode — do not expect them to propagate upstream.

---

Recommended if you have a subscription: Anthropic/Claude, OpenAI.

Skip: press Enter, or type skip.

Enter 1-38, provider name, or Enter=skip: 8
Setting up OpenCode Go...
See setup details: https://opencode.ai/docs/providers#opencode-go

Endpoint: https://opencode.ai/zen/go/v1
API key env variable: OPENCODE_GO_API_KEY

Paste your OpenCode Go API key:

Successfully saved OpenCode Go API key!
Stored at /Users/lan/Library/Application Support/jcode/opencode-go.env
Default model hint: kimi-k2.5

Validating OpenCode Go login with live auth/runtime checks...
=== auth-test: opencode-go ===
credential paths:

• /Users/lan/Library/Application Support/jcode/opencode-go.env
  ✓ credential_probe — OpenCode Go auth status is available (API key (OPENCODE_GO_API_KEY)).
  ✓ refresh_probe — Skipped: provider does not expose a dedicated refresh probe in jcode today.
  ✓ provider_smoke — Provider returned AUTH_TEST_OK.
  ✓ tool_smoke — Tool-enabled provider request returned AUTH_TEST_OK after one validated real Jcode bash tool call, successful registry execution, and tool-result followup.
  smoke output: AUTH_TEST_OK
  tool smoke output: AUTH_TEST_OK
  result: PASS

Starting server...
Error: Server exited before signalling ready (exit status: 1):
Error: No credentials configured. Run 'jcode login' or set ANTHROPIC_API_KEY to authenticate.

[quangdang46]

Mirrored upstream report: server fails with "No credentials configured" despite successful OpenCode Go auth. The fork's provider stack has been refreshed since (e.g. set_model_with_auth_refresh in src/provider/mod.rs — see #71 close). Closing as not planned — re-open with a fork-specific repro if it reproduces.

[quangdang46]

Mirror reports OpenCode Go login fails with "No credentials configured" despite successful auth flow. Local fork's set_model_with_auth_refresh path (src/provider/mod.rs:148) was added precisely for this credential-miss case after auth flows complete. The exact symptom probably no longer reproduces here, but I cannot verify without the same OpenCode Go account. Closing as not planned — please re-open with a fork-specific repro on the latest master if it still happens.

[quangdang46]

Implementation Plan

Scope

Server fails to start with "No credentials configured" despite successful OpenCode Go auth. Root cause: jcode's OpenCode Go credential lookup doesn't handle their newer auth.json schema.

Diagnostic

1. Add to jcode doctor: report all OpenCode auth paths checked + which had a parseable token.
2. Compare current parser in src/auth/external.rs against latest OpenCode Go auth.json schema.

Fix (likely)

• OpenCode Go renamed fields between versions: access_token → token, or added wrapper object. Update parser to be tolerant of both shapes via serde aliases.

Files

• src/auth/external.rs::source_contains_oauth_provider
• Add fixture file tests/fixtures/opencode-go-auth-v*.json for each schema variant.

Tests

• Each fixture parses successfully.

Estimated scope: S — ~50 LOC + 2 fixture files.