Skip to content

OpenCode plugin 0.1.3

Choose a tag to compare

@beastlabai beastlabai released this 30 Oct 22:02
· 225 commits to master since this release

The OpenCode Multi-LLM plugin now includes the current master runtime, including commit-range review and guarded fix workflows, sharper review prompts, and detached-log fixes. Shared version: 0.1.3.

Requires OpenCode 1.19.5 or newer and uv on PATH. Change your exact plugin pin and restart OpenCode:

{ "plugin": ["opencode-multi-llm@0.1.3"] }

Confirm it loaded with opencode debug config and check that command["multi-llm"] exists. Existing provider configuration is preserved. File-route users should first run uninstall-host opencode from their original installation to remove its command shim.

The full local gate passed rows 1–9 and 5b on OpenCode 1.19.5, including all five installed-package container scenarios. Release source: c9ae61b027a9e7bac4db216353495077f9c1d6f2. Committed gate record. The publisher preserves GitHub-certified source metadata and requires its rebuilt package digest to equal the independently gated release tag. The dispatch-source rebuild at cfe445b4543b733b9754df807f1e7c224fb15de7 matches that digest exactly. The OIDC publication succeeded with npm 11.5.1 and Node 22.23.4. Its accepted provenance identifies the correct repository, .github/workflows/publish-opencode-plugin.yml, and certified dispatch source cfe445b4543b733b9754df807f1e7c224fb15de7; the published subject digest matches the registry package. Publishing run.

A fresh stock-container install passed all nine later-release criteria, including exact installed-tree equality with the tag, first-use dependencies, offline operation with the network cut, restart, and an actual upgrade from 0.1.1 executing the new payload. Committed registry install/upgrade proof.

Integrity: sha512-b4rfpMp/eLCeYMx506jEyRbCIXzgfg9DKChejXIyxHAFMDUZH/01Jw4wWkHiOLdqNDojfV08K16/gaybJQxpYg==.

The gate record, registry proof, source-equivalence proof, and provenance verification are attached. Raw supporting logs remain local because they contain machine-specific paths. All package and install checks used local stubs; no paid model calls were made.