Model-Task Routing (OpenCode Go)
Concrete model ID → task-type mapping for the OpenCode Go subscription. Companion to Model Tier Routing (which covers abstract tier discipline). All heuristics are community-sourced unless marked confirmed.Task → Model Mapping
Per-Model Profile
deepseek-v4-pro — Opus analog. Reliable for planning and structured tasks. Confirmed in pi delegate and pueue usage. 0.87 per M tokens.
kimi-k2.6 — Superseded by kimi-k2.7-code in active agent config. Still available as opencode-go/kimi-k2.6.
deepseek-v4-flash — Haiku analog. Fast, very cheap. Use for read-only, boilerplate, rote subagent work. 0.28 per M tokens.
glm-5.2 — Assigned role: plan-writer agent (sequential plan file decomposition). Community niche confirmed: structured planning from spec, not general orchestration. Lower hallucination rate than Kimi K2.6 for implementation per “AA bench” (source: one r/opencodeCLI commenter — benchmark name uncited, unverified). Fast in OpenCode Go. “Opus-comparable” claim is overstated: a separate commenter rates it “around k2.6 level, maybe slightly worse”; DeepSeek V4 Pro outperforms it for issue analysis in direct comparison. Most expensive model in roster at 4.40 per M tokens.
glm-5.1 — Older version, still available as opencode-go/glm-5.1. Prefer 5.2.
qwen3.6-plus — Good for review/analysis per community. ID opencode-go/qwen3.6-plus confirmed. opencode-go/qwen3.7-max and opencode-go/qwen3.7-plus also available (newer, uncharacterized).
kimi-k2.7-code — Code-specialized successor to k2.6. Active Sonnet-tier model in all agent configs as of 2026-06-19. ID opencode-go/kimi-k2.7-code confirmed.
mimo-v2.5-pro — Used in community spec→plan workflow. ID opencode-go/mimo-v2.5-pro confirmed. opencode-go/mimo-v2.5 (base) also available.
minimax-m3 — Successor to m2.7. ID opencode-go/minimax-m3 confirmed. Uncharacterized.
Community Workflow Pattern
Multiple r/opencodeCLI users converged on this multi-model pipeline for complex tasks:opencode models (2026-06-19). kimi-k2.7-code now active in agent config in place of kimi-k2.6.
Key insight from the thread: “each model has significant strengths and weaknesses. Unlike Opus, you do not want to use just one model for everything.” — look (8 upvotes)
Why this matters for agent design: the Go subscription enables a specialist pipeline rather than a single-model loop. The delegator’s role shifts from “pick the best one model” to “sequence the right model for each phase.”
Thinking Budget Suffixes
Model IDs accept an effort suffix that controls extended thinking:
Example:
opencode-go/kimi-k2.7-code:high for a deep grill-me session.
Benchmark Tracking
Manually updated as benchmark data is gathered. No live source yet.Fallback Chain (per provider)
When a Go model is rate-limited or missing, demote within Go before crossing providers. See Model Tier Routing#Missing Model Fallback for the full rule. Go-specific order:- Opus slot:
deepseek-v4-pro→kimi-k2.6→ cross-provider - Sonnet slot:
kimi-k2.6→deepseek-v4-pro→ cross-provider - Haiku slot:
deepseek-v4-flash→ demote todeepseek-v4-flash:off→ cross-provider
Related Pages
- Model Tier Routing — abstract tier discipline (Haiku/Sonnet/Opus)
- OpenCode Go — subscription pricing, full model roster
- Pi Agent (pi-mono) — CLI that consumes these model IDs