2026-05-11 — Integrate OpenCode

Labels to apply (manual): integration-proposal, auto-generated, urgent
Status: DRAFT — auto-generated by weekly-landscape-scan routine. Needs human review before promoting to "approved."
Landscape score: 10 / 12 — urgent (score ≥ 10)

Why this is urgent

OpenCode (opencode.ai) is the leading open-source, provider-agnostic terminal coding agent with 120,000 GitHub stars and ~5M monthly developers — HN #1 in March 2026. It natively supports MCP. codetalker has integration guides for 13 agents already (Cursor, Goose, Continue, Windsurf, Zed, Codex CLI, etc.) but not OpenCode. This is the single largest uncovered distribution gap.

What to do

1. Add docs/integrations/opencode.md (install, MCP config, verification)
2. Update README.md and docs/integrations/README.md
3. (Stretch) OpenCode custom commands for codetalker controls

Config snippet (protocol-compatible, no code changes)

{
  "mcpServers": {
    "codetalker": {
      "command": "python",
      "args": ["-m", "claude_code_talker.mcp_server"],
      "env": {}
    }
  }
}

Effort: Small (~2–4 hours, documentation only)

Open questions

• Config file precedence: ~/.config/opencode/config.json vs .opencode/config.json?
• Does OpenCode's SSE transport work with codetalker-mcp's stdio server?
• Should custom commands expose codetalker-voice, codetalker-character, codetalker-mute?

Full draft spec

docs/superpowers/specs/2026-05-11-integrate-opencode.md — committed locally on branch docs/landscape-report-2026-05-11 (see push note below).

Push note: The weekly-landscape-scan routine committed all files locally on branch docs/landscape-report-2026-05-11 but could not push to GitHub remote (HTTP 403 — integration lacks branch-write permissions). The commit and all 7 spec files exist locally. A human with push access should run: git push -u origin docs/landscape-report-2026-05-11 to publish the branch and open the PR.

Auto-generated by weekly-landscape-scan routine on 2026-05-11.