What happens#
The OpenCode Go spec sync failed at 05:31 UTC on 2026-11-20 with this ingest_failed error:
opencode-go: gemini-4-argon has unknown api protocol interactions
The live listing (GET https://opencode.ai/inference/go/v1/models) now gives gemini-4-argon two routes on the same base:
{"generate-content": {"base_url": "https://opencode.ai/inference/go/google/v1beta", "sdk": {"opencodeai": "@opencode/ai/providers/google"}},
"interactions": {"base_url": "https://opencode.ai/inference/go/google/v1beta", "sdk": {"opencodeai": "@opencode/ai/providers/google/interactions"}}}
GO_PROTOCOL_PATH (src/server/providers/opencode-go-facts.ts:26) has no interactions key. goListingRoutes throws on the first protocol it doesn't know, so the whole route list fails. The spec sync then keeps the stored OpenCode Go schemas, and the new model's routes are never added. This is not an upstream error: it fires every daily spec sync until the parser knows the key.
Fix#
- Add
interactions to GO_PROTOCOL_PATH. It's Google's Interactions API: POST {base}/interactions, with the model in the request body, not in the path. See gemini-video.ts, which already builds Interactions endpoints from Google's Interactions OpenAPI (#658).
- Check what
opencode-routes.ts does with a route. If it needs a request/response schema per route, reuse the Interactions schema the Gemini adapter already fetches. Don't hand-write one, and don't reuse the generateContent schema.
- Keep the throw for any other unknown protocol key (fail loud).
- Add a fixture test with the live
gemini-4-argon row.