Repository navigation
Releases
OpenCode V1 Bridge v0.82.0-preview.1 — OpenCode 2.3.0 Experimental Preview
Experimental, offline-verified OpenCode 2.3.0 preview. Genuine-host acceptance has not been completed on OpenCode 2.3.0 or 2.0.27 for this candidate. Intended for isolated, trusted-local testing; not a production-stable release. Use a dedicated password-protected loopback server with a single trusted project and trusted clients.
This server-first preview adds an exact OpenCode 2.3.0 entrypoint alongside 2.0.27. Use direct tool exposure. The bridge refuses the experimental CodeMode profile on 2.3.0 because the public plugin interface cannot guarantee that the scheduler uses its gateway. The 2.3.0 adapter observes native cancellation, rejects progress or successful results after cancellation at the bridge boundaries, and excludes first-token telemetry from legacy event projection.
Offline evidence includes 444 portable Node tests, 81 focused tests per standalone Bun 1.4.2 and 1.4.3 environment, and four source-backed host-contract checks, plus JavaScript and TypeScript declaration verification. Packaging checks verified a byte-identical repack and a disposable offline install. Genuine 2.3.0 scheduler and database acceptance and a genuine 2.0.27 regression for the preview remain open. The separate Windows R10 probe remains FAIL under its cumulative Job-count criterion. It ran no OpenCode and supplies no bridge compatibility evidence.
The published beta.4 release remains the separately evidenced 2.0.27 release. Its scoped native witness ran the original Personality setMood once, verified the project write and durable result, returned that result to the next scripted request, and shut down cleanly.
Supported V1 behavior is a subset of the legacy SDK and hooks. It includes canonical direct-tool execution hooks and reduced client and event profiles. Full V1 configuration, request mutation and permission requests remain outside the preview. Read the bundled README.md, SECURITY.md, and Remaining Issues.md before installing. In particular, keep command output out of shared or remotely reachable instances. Caller ownership, after-disconnect NO-CONSUMER, the separate missing-toast-consumer test, and historical Windows TUI shutdown EPIPE remain open. The preview supplies no public toast capability. A legacy factory that never settles can block activation, and cancellation cannot undo side effects already performed by a plugin.
Verify the tarball against SHA256SUMS.txt and follow the bundled instructions for offline local installation.
OpenCode V1 Bridge v0.82.0-beta.4
OpenCode V1 Bridge v0.82.0-beta.4
OpenCode V1 Bridge is a server-first beta that loads explicitly configured, unchanged V1 plugins on stock OpenCode 2.0.27. It supports trusted plugin activation, per-plugin options and disposal, direct tools with supported schemas, selected tool hooks, reduced session and assistant events, session-scoped system text, and a small subset of legacy client operations.
Native verification
The exact beta.4 asset passed a genuine Windows scheduler test. The original opencode-personality@1.2.0 setMood ran exactly once, updated the isolated project JSON, produced a successful durable tool result, and delivered the result to the second scripted request. The server shut down naturally. The test used scripted local responses with no external provider inference.
Install
Download opencode-v1-bridge-0.82.0-beta.4.tgz and SHA256SUMS.txt. Follow the current Windows installation guide for checksum verification and offline local installation. The README in the frozen tarball and in the packaging commit still says native scheduler acceptance was pending because both were prepared before the test. The README on the current main branch and these release notes reflect the subsequent successful result.
Limits and safe use
- Use trusted plugins in a dedicated, password-protected loopback instance for one trusted project and trusted clients. Leave experimental command registration off where possible. Keep it off shared, forwarded or remotely reachable servers. The host can expose selected output to other authenticated subscribers, and the receipt does not authenticate the originating session, project principal or TUI. Workspace-scoped confirmed output is unsupported.
- V1 client coverage is incomplete. Full transcript access, faithful V1
configandchat.params, and some session and permission semantics are unavailable. The server profile does not supply V1ToolContext.ask. - TUI shutdown
EPIPE, command-output NO-CONSUMER acceptance after disconnect, and authenticated receipt ownership (Witness B) remain open. Experimental toast support is excluded. The original PersonalitysavePersonalitycan change project JSON before failing on its unsupported toast call.
See Remaining Issues, security guidance and Contributing. Reports of real V1 plugins that work or fail are welcome. Include exact versions and a minimal redacted configuration. Contributions to V1 API coverage and source-backed alternatives to the host limits are welcome.
Licensed under MIT. OpenCode-derived material retains its upstream license and attribution in the third-party notices.