v2.1.3: Console account connected (52 models in /api/v2/config) but opencode provider never registers #58335

Activity

1. opencode-agent commented on Oct 23, 2026

   

   opencode-agentBot

   on Oct 23, 2026 – with OpenCode Agent

   Contributor

   More actions

   Thanks for the detailed report. I tried to reproduce this on v2.1.3 and couldn't. I used a mock Console that returns a config shaped like yours (opencode with models, opencode-go with none), a stored opencode API-key credential, and opencode serve. I also tried each of these:

   • OPENCODE_API_KEY and OPENCODE_CONSOLE_TOKEN set to the same key as well
   • only the env var
   • enterprise.url plus custom V2 providers
   • a custom providers.opencode block like your second attempt

   In every case /api/provider listed both opencode-go and opencode, and /api/model had the opencode/* models.

   So something in your setup must be different. These would help narrow it down:

   1. Your config as shown by opencode debug config, with keys and URLs redacted. In particular, any setting that enables, disables or filters providers.
   2. The full output of opencode auth list. Your database shows an account row as well as the key credential, so do you also have a signed-in Console account (OAuth), and which credential is active?
   3. The server logs from startup with --log-level debug, especially any line containing failed to load OpenCode provider config. For the service, check the journal or run opencode serve in the foreground with the same environment.
   4. The JSON for opencode-go from GET /api/provider (its integrationID, activation and headers), and whether it still appears if you stop the service and run opencode serve directly.

   You can reply here, or edit the issue and leave a comment saying you've updated it.
2. cripperzprodigy commented on Oct 23, 2026

   

   cripperzprodigy

   on Oct 23, 2026

   Author

   More actions

   Update: device-flow auth succeeded, provider still absent — plus a concrete clue

   After filing this, I completed opencode auth login "OpenCode Console" --method device successfully:

   • opencode auth list now shows OpenCode Console — Default — stored (session) alongside the API key + env entries.
   • account row unchanged ([email protected], token expiry 2026-11-19).
   • Restarted the service (opencode service restart) → /api/provider still lists 10 providers without opencode; /api/model still 0 opencode/*.

   Clue — the Console config endpoint requires x-org-id for account session tokens:

   With the account access_token (st_…):

   curl -H "Authorization: Bearer $ST" https://opencode.ai/console/api/v2/config
   # 400 {"_tag":"OrgRequired","message":"x-org-id is required","code":"org_required"}
   
   curl -H "Authorization: Bearer $ST" -H "x-org-id: wrk_01KWC3KGW22QXBV0J758AHSE7G" \
     https://opencode.ai/console/api/v2/config
   # 200 → providers: { opencode: 52 models, opencode-go: 0 models }

   Note the header name differs from the inference path: the Console config API wants x-org-id, while the OpenCode docs/examples use x-opencode-org-id for inference. If the provider-sync call sends x-opencode-org-id (or omits the org), it gets org_required and the provider is silently dropped — which would match the observed behaviour exactly.

   The service key (oc_sk_…) works without any org header (200), so the failure is specific to the account-session path.

   Repro host: v2.1.3, Ubuntu 24.04, opencode serve --service, account_state.active_org_id = wrk_01KWC3KGW….
3. cripperzprodigy commented on Oct 23, 2026

   

   cripperzprodigy

   on Oct 23, 2026

   Author

   More actions

   Correction — this is not a bug; closing

   I found the actual cause on the reporting host: opencode.json contains

   "policies": [
     { "action": "provider.use", "resource": "opencode", "effect": "deny" }
   ]

   This policy deliberately disables the pay-as-you-go opencode provider (the account has no
   funds — 402 Insufficient account funds), while opencode-go remains available. The provider is
   therefore correctly absent from /api/provider and /api/model; the Console still advertising
   52 models is expected (the catalog is independent of the local policy).

   The device-flow re-auth and the x-org-id observation are still accurate data points, but they
   are not a defect. Sorry for the noise — closing as not-a-bug.
4. cripperzprodigy

   closed this as not plannedon Oct 23, 2026
5. opencode-agent commented on Oct 26, 2026

   

   opencode-agentBot

   on Oct 26, 2026 – with OpenCode Agent

   Contributor

   More actions

   I'm closing this for now because we couldn't reproduce it and haven't heard back. On v2.1.3, with a Console config shaped like yours, the opencode provider and its models showed up next to opencode-go in every setup I tried: a stored key, the OPENCODE_API_KEY/OPENCODE_CONSOLE_TOKEN env vars, enterprise.url, and a custom providers.opencode block. Without your config, opencode auth list output and server logs, we can't tell what's different on your side.

   If it still happens, please reply with the details from my earlier comment and we can reopen it:

   • opencode debug config, redacted
   • opencode auth list
   • startup logs with --log-level debug, especially any failed to load OpenCode provider config line
   • whether it also happens when you run opencode serve in the foreground instead of as a service

   Thanks for the detailed report.