audit 2026-11-08 (window 11-07): cron claim loss in gateway restart drain (2 runs orphaned, 2 incident rows unalerted); Hermes 0.22.5->0.23.0 (snapshot skipped), camofox plugin 1.1.0, conduit 0.134.4, hq-push 0.9.42, opencode-go key expired; skills 302->299 (4 archived); freshness 0/126/3 of 129
This commit is contained in:
+27
-2
@@ -3,8 +3,8 @@ title: OpenCode Go
|
||||
type: system
|
||||
status: active
|
||||
created: 2026-07-29
|
||||
updated: 2026-10-20
|
||||
verified_on: 2026-10-20
|
||||
updated: 2026-11-08
|
||||
verified_on: 2026-11-08
|
||||
confidence: high
|
||||
tags: [opencode, provider, models, subscription, limits]
|
||||
sources: [https://opencode.ai/docs/go/]
|
||||
@@ -137,6 +137,31 @@ With Go, you pay $10/month and they aim to give you **6x that in usage** ($60).
|
||||
| Qwen3.6 Plus | `qwen3.6-plus` | same | same |
|
||||
| Hy3 | `hy3` | `https://opencode.ai/zen/go/v1/chat/completions` | @ai-sdk/openai-compatible |
|
||||
|
||||
## 2026-11-08 00:0x-00:5x AWST — the stored credential is expired (401 `api_key_expired`)
|
||||
|
||||
**Status: `active` as a configuration, `dead` as a credential.** Two independent live probes in this window
|
||||
both returned **HTTP 401** on the Go endpoint:
|
||||
|
||||
probe 1 (this audit, 2026-11-08 00:2x): zen_go_http=401
|
||||
{"error":{"type":"authentication_error","code":"api_key_expired",
|
||||
"message":"This API key has expired. Create a new API key in OpenCode Console and
|
||||
replace it in your client or secret store. …"}}
|
||||
— the same 401 for `https://opencode.ai/zen/go/v1/models`, and `~/.local/share/opencode/auth.json`
|
||||
still lists an *OpenCode Go api* entry (the CLI's own store).
|
||||
probe 2 (2026-11-07): provider=opencode-go (fields `key`, `type`) → HTTP 401, body
|
||||
`{"error":{"type":"authentication_error","code":"api_key_expired", …}}`
|
||||
|
||||
- This is **upstream expiry, not a Hermes fault**: the key was issued by the OpenCode console and has run
|
||||
out. Hermes is still configured for the provider (`opencode-go/<model-id>`, per the table above), and
|
||||
router bridges exist (`ollama-opencode-go-deepseek-v4-flash`, `-glm-5*`, `-grok-4_6`, `-kimi-k2_5`, …).
|
||||
- **No 2026-11-07 execution failed on an auth error** — the day's three failures were all the gateway
|
||||
restart drain ([[incidents/2026-11-07-cron-claim-loss-in-gateway-restart-drain]]), so nothing in the fleet
|
||||
was actually consuming this provider in-window. The risk is latent: anything pinned to it fails on first
|
||||
use.
|
||||
- **To restore:** mint a new key in the OpenCode console, then replace it in **both** stores — the Hermes
|
||||
provider entry and `~/.local/share/opencode/auth.json` — and re-probe `…/zen/go/v1/models` for a 200.
|
||||
(Keys live in the vault; this page records only their state — [[references/hermes-api-vault]].)
|
||||
|
||||
**Config format:** `opencode-go/<model-id>` (e.g. `opencode-go/kimi-k3`)
|
||||
|
||||
**Model list API:** `https://opencode.ai/zen/go/v1/models`
|
||||
|
||||
Reference in New Issue
Block a user