duncanmcqueen opens Mike to OpenCode Go's open-model catalogue

Mike users can now choose from another subscription-backed route to capable open coding models, without loosening control of who can use them.

integrationworkflow

OpenCode Go is a low-cost subscription gateway for open models, and duncanmcqueen has added it as Mike's third route for AI models alongside the existing options. The change reaches both the web app and Word add-in, so a firm's model choices need not diverge between drafting contexts.

Live model catalogue: users can browse the gateway's available models from within Mike.
Bring-your-own-key settings: firms can use their own gateway credentials, kept server-side.
Saved model choices: users can keep preferred models selected across sessions.
Usage controls: only models a user has explicitly enabled can be requested, including when a shared organisational key is in use.

This matters to legal-product teams and legal ops leaders weighing model choice against spend controls and predictable governance.

So what Worth a GitHub look for teams that want broader model access without turning model selection into an unmanaged free-for-all.

View this fork on GitHub →

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

4 commits from duncanmcqueen/mike, oldest first. Source extracted verbatim from the harvested git log.

SHA	Subject	Author	Date
`23b41c5a`	feat: add OpenCode Go as a third model router	duncanmcqueen	2026-08-20	↗ GitHub
commit body OpenCode Go (opencode.ai's low-cost hosted gateway for open coding models - GLM-5, Kimi K3, Qwen3.8 Max, MiniMax-M3, DeepSeek V4) joins OpenRouter and the Vercel AI Gateway as a router, reusing the existing router plumbing end to end rather than adding a parallel one: - opencode-go/<model> ids stream through the shared router adapter against https://opencode.ai/zen/go/v1, with OPENCODE_GO_BASE_URL as the usual proxy/test override. OpenRouter's attribution headers and reasoning payload stay OpenRouter-only. - New opencode-go user API key (OPENCODE_API_KEY env or encrypted per-user storage) with a Settings > API Keys field and a migration widening the user_api_keys provider CHECK. - GET /models/opencode-go returns the live catalog with the key kept server-side; Settings > Routers gains an OpenCode Go picker, and the saved selection gates requests through the same user_router_models choke point that stops a hand-crafted request from spending the operator's env key on an arbitrary gateway model. - Both model pickers and the Word add-in gain an "OpenCode Go" group. Router slugs, model-id prefixes and API-key provider names are one string per router, so routerForModelId, the selection lookups and the profile payload are now driven by ROUTER_SLUGS instead of a hard-coded pair. The one place the routers genuinely differ is catalog-id shape: OpenCode Go publishes bare model names ("glm-5"), so id validation is per-router. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
`da8ed0e5`	fix(llm): gate OpenCode Go models by protocol	willchen96	2026-08-21	↗ GitHub
`3ec6d060`	feat(llm): support OpenCode Go Messages models	willchen96	2026-08-21	↗ GitHub
`0f006e2c`	refactor(settings): clarify bring your own keys navigation	willchen96	2026-08-21	↗ GitHub

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-1274.md from inside the repo you want the changes in.

⬇ Download capture-thread-1274.md