OpenCode 2 can run Go through a connected Console API key while its separate Go key has expired. T3's limits probe ignored that Console connection and reported “OpenCode Go could not read usage.”
Read the selected public Console API key from OpenCode's database read-only, ahead of the separate Go key. Match OpenCode's credential selection order and explicit OPENCODE_DB path; skip in-memory databases. Select one connection before interpreting its credential so OAuth, inactive, or self-hosted connections cannot expose an older Console account. Retry with a distinct Go key only on 401/403, and fingerprint the key that produced the successful response. Inline auth overrides and disabled/external-instance guards remain in place. The usage guide now describes API-key Console connections.
Taken over from @Benglennon123's #21007, preserving the original commit and merging main. Compared credential ordering, database paths, and public-server metadata against the official OpenCode 2.0.28 and 2.0.32 producers. The rebuild corrects creation-order selection and explicit public Console metadata; review also caught the wrong-account risk from ignoring OPENCODE_DB.
Verification on Linux:
pnpm exec vp test run packages/provider-opencode/src/server/status.test.ts packages/provider-opencode/src/server/usage.test.ts: 35 passed in two existing files. The single added SQLite regression was rewritten without adding test cases: original PR 28 status tests, merged baseline 29, final 29. It covers Console precedence, 401/403 fallback, non-auth failures, credential exclusions, legacy ordering, inline auth, custom databases, unchanged database bytes, and successful-key identity. It fails against main; the custom-database case also fails against the first rebuild.| 1 | main: Console connected + expired separate Go key |
| 2 | requests=[legacy], unavailable=probeFailed, windows=[] |
| 3 | head: requests=[Console], unavailable=none, windows=[session:17, weekly:33, monthly:16] |
| 4 | 401/403: requests=[Console, legacy], successful-key fingerprint matches legacy |
| 5 | 500: requests=[Console], unavailable=probeFailed, no retry |
| 6 | custom DB: selects Console there even when default DB contains another account |
| 7 | inline override: requests=[inline] |
| 8 | disabled/external instance: no credential requests |
The headless pass also checked inactive/OAuth/self-hosted exclusions and :memory: handling; database files were unchanged. Screenshots do not apply to this server-only change.
Not verified: acceptance by the live Console/Go service, a running client with a real account, custom-channel OpenCode builds without an explicit database override, macOS, Windows, iOS, Android, or Electron desktop. A human should verify a real Console API-key account with an expired Go key before landing. The earlier approval discussion deferred Console OAuth; this PR adds no OAuth support, endpoint, or setting. Approval for this API-key credential path remains a human decision. No merge performed.
Tests: GPT-6 Astra; implementation: GPT-6.1 Sol; independent reviews: Claude Opus 5.5 and GPT-6 Sol; integration and preparation: GPT-6.1 Sol. Codex harness in T3 Code, with Claude used only for review.
Added 1 commit
Verdict: Needs Human Approval
Macroscope's review found this PR requires human approval — The PR narrowly restores OpenCode Go limit reporting and includes targeted regression coverage, but it changes production handling of Console API credentials by reading them from SQLite and sending them to the usage service. The authentication and sensitive-data implications require human review.
You can add or adjust custom eligibility rules. Learn more.
Warning
Only developers with an assigned seat can use this organization's usage-based review budget, and seats here are assigned manually. Ask an admin to assign a seat, or change the review continuation mode in Billing.
Next included review available in 7 minutes.
Limit details: You’ve used all 10 included reviews currently available.
Review configuration:
6b7cf157-4b2f-4ef5-a461-e6ed3653f7d2Reviewing files that changed from the base of the PR and between 3cb5b4f9f49332a6e7e204df49c991bc56b251c9 and 31a3f3267891780e8a5a12a03d48a5908cca5962.
docs/user/usage.mdpackages/provider-opencode/src/server/status.test.tspackages/provider-opencode/src/server/usageLimits.tsNo actionable comments were generated in the recent review. 🎉
0a505897-5a85-40b9-b002-84c98589bc07Reviewing files that changed from the base of the PR and between 13aa882c22d584de5388dfce3b3ca413387ba059 and 3cb5b4f9f49332a6e7e204df49c991bc56b251c9.
docs/user/usage.mdpackages/provider-opencode/src/server/status.test.tspackages/provider-opencode/src/server/usageLimits.tsIncluded review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 9 remain after this review.
The OpenCode Go usage probe can read a Console API key from OpenCode’s local database. It tries that key before the Go API key and falls back to the Go key after HTTP 401 or 403. The usage guide clarifies which credentials are accepted.
Changes: OpenCode Go usage credentials
| Layer / File(s) | Summary |
|---|---|
Read Console credentials from SQLite packages/provider-opencode/src/server/usageLimits.ts | The code reads eligible opencode key records from the local database. It excludes records with a server override and handles database errors without returning a Console key. |
Use Console credentials with Go-key fallback packages/provider-opencode/src/server/usageLimits.ts, packages/provider-opencode/src/server/status.test.ts, docs/user/usage.md | The probe tries the Console key first and retries with the Go key after HTTP 401 or 403. Tests cover credential selection and fallback. The usage guide clarifies the accepted credentials. |
Priority: ➖ Normal
Estimated code review effort: 2 (Simple) | ~12 minutes
Change: Bug fix
| 1 | sequenceDiagram |
| 2 | participant GoUsageProbe |
| 3 | participant OpenCodeDatabase |
| 4 | participant UsageEndpoint |
| 5 | GoUsageProbe->>OpenCodeDatabase: Read an eligible Console key unless inline auth overrides lookup |
| 6 | OpenCodeDatabase-->>GoUsageProbe: Return the Console key or no key |
| 7 | GoUsageProbe->>UsageEndpoint: Request usage with the Console key when available |
| 8 | UsageEndpoint-->>GoUsageProbe: Return usage or HTTP 401/403 |
| 9 | GoUsageProbe->>UsageEndpoint: Retry with the Go key after HTTP 401/403 when it differs |
Suggested reviewers: maria-rcks, nexxeln
3cb5bNo issue identified that should block merging the Console API-key usage fix after normal checks.
3cb5bThe change uses an additional local credential source but retains the existing HTTPS destination, local-instance restrictions, and read-only behavior. No new credential-disclosure or authorization-bypass path was established. Compatibility with all supported OpenCode credential formats remains unverified.
Retained concerns No architecture-level concerns identified.
Security Blast Radius
Trust Boundaries and Controls
Resilience and Maintainability Implications
Hardening Proposals
Failed Failed checks: 1 warning
| Check name | Status | Explanation | Resolution |
|---|---|---|---|
| Description check | Warning | The description fully explains the problem, implementation, scope, verification results, limitations, and test evidence. However, the required maintainer approval for the Console API-key path is not p… | Add a link to explicit maintainer approval of the direction and scope, including the approval comment. If the change qualifies as an obvious focused fix without prior approval, explain why it qualifies under the repository requirements. |
| Check name | Status | Explanation |
|---|---|---|
| Linked Issues check | Passed | Check skipped because no linked issues were found for this pull request. |
| Out of Scope Changes check | Passed | Check skipped because no linked issues were found for this pull request. |
| Title check | Passed | The title clearly and concisely identifies the main change: restoring OpenCode Go limits for Console API keys. |
Explanation
The description fully explains the problem, implementation, scope, verification results, limitations, and test evidence. However, the required maintainer approval for the Console API-key path is not provided; the description states that approval remains a human decision.
Resolution
Add a link to explicit maintainer approval of the direction and scope, including the approval comment. If the change qualifies as an obvious focused fix without prior approval, explain why it qualifies under the repository requirements.
Comment @coderabbitai help to get the list of available commands.
Taking over this one. I’ll verify the Console credential format and precedence, keep the reader scoped to local instances, and refresh the regression and headless proof before pushing to this branch.
Added 4 commits
