OpenCode v1.19.0 (Oct 11) adds opencode upgrade --major and a TUI /update command to move 1.x installs to OpenCode 2 (tagged up to v2.0.26), stops auto-installing updates, and hardens PTY connection validation. The official V2 migration guide lists three intentional breaking changes: plugin API, server API/clients, and terminal client config.

Key Takeaways

  • ✓v1.19.0 shipped 2026-10-11: opencode upgrade --major or TUI /update moves to OpenCode 2; updates are no longer auto-installed
  • ✓OpenCode 2 tags run from v2.0.0 (2026-09-11) to v2.0.26 (2026-10-08); the repo has ~212K GitHub stars
  • ✓Three intentional breaking changes: new plugin API, new server API and clients (@opencode/client), and layered tui.json replaced by one global cli.json
  • ✓V1 plugin implementations do not run on V2 and must be ported; existing agents, commands, skills and opencode.json keep working
  • ✓V2 accepts lsp config but no longer runs language servers or LSP diagnostics; use lint/typecheck/compile commands instead
🧭

Turn your technical choice into a development budget

Compare 40 dev plans & simulate token costs vs $20/mo subscriptions

🔬

In-Depth Technical Analysis

OpenCode v1.19.0 (released 2026-10-11) gives 1.x users an explicit, opt-in path to OpenCode 2 via opencode upgrade --major or the TUI /update command, and stops auto-installing updates. It also allows OpenAI's ultrafast service tier and validates PTY connection origins and tickets before checking whether a PTY exists. OpenCode 2 has been tagged from v2.0.0 (Sep 11) through v2.0.26 (Oct 8).

Per the official migration guide, V2 has three intentional breaking changes: a new plugin API (V1 plugin implementations do not run), a new server API and clients (@opencode/client), and a single global cli.json replacing layered tui.json files (auto-migrated on first start). Existing opencode.json, agents, commands and skills keep working; native V2 config makes permissions an ordered array (bash becomes shell, task becomes subagent), groups MCP under mcp.servers with split catalog/execution timeouts, and writes variants as provider/model#variant. V2 accepts but no longer runs LSP. No benchmarks were published. To migrate: back up V1 config, remove a package-managed V1 install, install V2 (curl -fsSL https://opencode.ai/v2/install | bash or npm i -g @opencode/cli), verify models, permissions and MCP, then port plugins and server-API integrations.

Action HubReady to adopt this in production?

Benchmark side-by-side against alternatives, or calculate monthly token cost vs subscription break-even.

Up NextOpenCode 1.18.33: Cloudflare AI Gateway honors timeouts, MCP browser launch failures surface, debug config redacts credentials
Read Now→