OpenCode Model Control 0.2.0
·
4 commits
to main
since this release
Immutable
release. Only release title and notes can be modified.
Version 0.2.0 makes routing seamless while keeping the control plane local, bounded, and explicit.
Highlights
- Attachment-aware OpenCode plugin routing sends media-only analysis to the saved compatible vision worker before provider dispatch.
- Explicit media-assisted code changes can continue through Omc-Router, the code worker, an independent read-only reviewer, and at most one repair pass.
- Omc-Router can become the default agent when no user default exists; existing user defaults are preserved.
- The control panel now uses full-width stacked modules, a collapsible desktop sidebar, and a mobile navigation drawer.
- Update available models, Free/Paid priority, and manual runtime-access checks are clearly separated from benchmark evidence.
- Every local mutation now requires a per-process browser-session capability in addition to same-origin JSON request controls.
- Node.js 22.12.0 or newer is required; CI covers Node 22.12 and Node 24.
Install or upgrade
npm install --global opencode-model-control@0.2.0
opencode-model-control --version
opencode-model-controlAfter the panel opens, update available models, review and save the routing policy, choose Update connection (or Connect to OpenCode), then restart OpenCode.
Verification
- 213/213 automated tests passed with TypeScript checking and a production build.
- Node 22.12 and Node 24 GitHub Actions jobs passed.
- CodeQL completed without a release-blocking result.
npm audit --audit-level=highreported 0 vulnerabilities.- The exact packaged artifact passed a disposable clean install plus Connect, status, Disconnect, production startup, security-header, and read-only-session checks.
- SHA-256:
59c6094a9b7dd57b897ee59c41269b154861de408db7c138c22725d17a1e67df
Compatibility note
OpenCode 1.18.x is the tested configuration target. Isolated parser, connector, MCP-handshake, and plugin acceptance passed on macOS. A fresh Linux installation and a current-tree live provider response remain separate acceptance items and are not claimed by this release.
See the changelog, support matrix, and security policy for the full boundaries.