Skip to content

Latest commit

 

History

History
80 lines (57 loc) · 13.1 KB

File metadata and controls

80 lines (57 loc) · 13.1 KB

Support matrix

This matrix describes implemented 0.4.1 behavior and dated compatibility evidence. Source verification, final installed-artifact acceptance, and public-channel verification are separate claims. See Releasing for the final-byte gates and the release index for published versions.

0.4.1 platform and public artifact evidence

Final CI run 36647447813 passed all seven jobs at source commit 306caba5dc6d000fd19d694c8e497f59acfd49f0. It produced one final tarball from clean main, SHA-256 9a04514bc7bf2ab251b027f9da18b03a3f8d786c84f95d8b4245e645a12bd2e5, and tested those exact bytes under all four OS/Node combinations.

OS/kernel Architecture Node versions executed OpenCode versions executed
Linux 6.17.0-1022-azure x64 22.12.0 and 24.21.0 1.18.22 and 1.18.28 under each Node version
macOS / Darwin 25.6.0 arm64 22.12.0 and 24.20.0 1.18.22 and 1.18.28 under each Node version

Each job passed 18 package checks, both real hosts (20 scenarios and 57 synthetic loopback requests per host), and 14 production browser scenarios with zero failures, skips, or flakes. Deliberately corrupted plugin and UI tarballs were rejected on Linux/Node 22.12.0. Each package run made 114 loopback requests and zero real-provider inference requests; the live public metadata smoke remains a separate check.

On 2026-09-29 (America/New_York), credential-free public npm and GitHub downloads matched that final SHA-256, and npm registry SHA-512 integrity matched. The GitHub release is immutable and its tag points to the source commit above. A clean version-pinned npm name install reported CLI 0.4.1 and matched all 84 package files.

Each public download separately passed all 18 package checks, both OpenCode hosts (20 scenarios and 57 synthetic loopback requests each), and all 14 production browser scenarios with zero failures, skips, or flakes. These public-channel runs used Linux x64 kernel 7.0.0-31-generic and Node 24.21.0, separately from the final CI matrix above. Each made 114 synthetic loopback requests and zero real-provider inference requests. See the public verification receipt, full npm verification evidence, and package ledger. Later documentation commits do not rebuild that artifact.

Historical 0.4.0 platform and artifact evidence

Final CI run 34688784337 passed on 2026-09-12 at source commit 942a94c5eb354da877b22ddc6eb37b098a598f7c. All four Linux x64/macOS arm64 and Node 22.12.0/24.20.0 jobs consumed one tarball, SHA-256 1ee2d3ab864f2615ec3f8c750a400694ac8587129bdef78b0d1b275793f0828b.

Each installed-package run passed 18 package checks, both OpenCode hosts (20 scenarios and 57 synthetic loopback requests each), and 14 production browser scenarios with zero failures, skips, or flakes. The matrix covered current installation, 0.3.0 Free/Paid upgrades, legacy 0.2.1 upgrades, private exact migration backups, connection updates, MCP, restart and disconnect recovery. Real-provider inference requests were zero. The immutable release contains the final acceptance evidence.

On 2026-09-12, the public npm download matched that SHA-256 and registry integrity. A clean version-pinned npm install matched all 83 package files, and the downloaded artifact passed the same package and browser checks on Linux/Node 24.14.0 with both hosts. See public npm verification and the package ledger.

Historical 0.3.0 platform and artifact evidence

Final CI run 34146977662 passed all seven jobs on 2026-09-07 at source commit bcd228a349627523382dda65017bab6fb0a4856c. The final 0.3.0 tarball was built once from that clean protected-main commit, and every installed-artifact job consumed the same bytes: SHA-256 26a532b44c96d643c0543a78d2fef1ab2c1a3b83886e6715cef0ab683d3413ab.

OS/kernel Architecture Node versions executed OpenCode versions executed
Linux 6.17.0-1022-azure x64 22.12.0 and 24.20.0 1.18.22 and 1.18.28 under each Node version
macOS / Darwin 25.6.0 arm64 22.12.0 and 24.20.0 1.18.22 and 1.18.28 under each Node version

Each OS/Node job passed all 16 package checks, both real-host matrices (19 scenarios and 56 loopback provider requests per host), and all 12 interactions with the installed production UI, with zero failures, skips or flakes. Evidence binds host execution to the installed core/service/plugin and browser execution to the packaged HTML/JS/CSS hashes. The package flow also checks production startup without Vite, current install, actual prior-0.2.1 upgrade, private v3 migration, MCP, token rotation, read-only rejection, Connect/Disconnect and config restoration. Intentionally broken plugin/UI tarballs were rejected while healthy checkout source remained present.

These were 112 synthetic loopback provider requests per package run and zero real-provider inference requests. Public Models.dev metadata smoke is separately labeled and makes no inference/quality claim. Linux source verification also passed all 293 tests, typecheck and build on both Node versions; source tests alone do not establish installed-package behavior.

The immutable GitHub release contains final matrix evidence and public npm verification. On 2026-09-07, credential-free npm and GitHub downloads matched the final SHA-256 above; npm registry SHA-512 integrity also matched.

Each downloaded tarball passed all 16 package checks, both OpenCode hosts (19 scenarios and 56 loopback requests each), and all 12 production browser interactions with zero failures, skips or flakes. Each public-channel run used Linux x64 kernel 6.8.0-138-generic and Node 22.12.0, separately from the final CI matrix above, with 112 synthetic loopback requests and zero real-provider inference requests.

A clean version-pinned npm name install reported CLI 0.3.0 and all 74 package files matched the public tarball. Exact download links and checksums are in the package ledger; the public verification receipt records both channels and issue closure.

Surface Status Boundary
Node.js >=22.12.0 Package engine contract The exact 22.12.0 minimum and 24.20.0 were executed above; other versions are not individually proven.
Linux x64 / macOS arm64 Final 0.3.0 artifact verified Only the recorded OS/kernel/runtime matrix is proven; this is not every distribution or architecture.
OpenCode 1.18.22 / 1.18.28 Actual final-artifact dispatch verified All owned roles, both media lanes, ordinary task/background resumes, retained repair/revocation, missing host models, endpoint conflicts, unrelated agents and owned slash summaries.
Other OpenCode versions/configuration majors Unverified Require explicit compatibility acceptance.
OpenCode TUI/server host Tested through actual host APIs/events Managed agents require a fresh host after initial Connect or a managed-surface update.
Headless HTTP-only callers Limited error guidance Missing-host errors may be generic UnknownError; consume the same-directory instance event stream for the reload toast text.
OpenCode desktop Unverified separately CLI/server evidence does not prove desktop application behavior.
WSL / native Windows / other architectures Unverified No new platform support claim is made.
npm / GitHub final 0.3.0 artifacts Public downloads and installed acceptance verified Both downloaded tarballs match the final SHA-256 and passed the separate Linux/Node 22.12.0 acceptance described above; GitHub release is immutable.

Implemented behavior

Surface Contract Boundary
All-provider discovery Plugin-aware opencode models --verbose, no provider filter Host-listed beta and enabled alpha models remain available. Incomplete discovery preserves omitted routes and unchanged bindings; fresh endpoint changes invalidate bindings. OpenCode may normalize its own $schema line.
Metadata refresh Stale startup, every 15 minutes while active, or manual Update Cross-process coalescing; separate attempted/successful timestamps; no inference or inferred settings/config writes.
Pricing Exact provider/model/API match; complete rates across every supported supplied billing dimension Positive rates mean paid. Zero rates on identified plan-specific slots remain unknown; other complete valid zero public rates can establish free pricing. Malformed/conflicting/expired pricing cannot authorize Free or legacy verified-price Paid. Configured Paid uses eligible host connection evidence without requiring an estimate. No free-name roster.
Pricing freshness 24-hour expiry evaluated at routing time Successful 200/304 renews public evidence; failed requests do not. Neither the source nor OMC guarantees future billing.
Capabilities Effective OpenCode report plus separate supplemental public report Unknown differs from false; full modalities/tools/reasoning/options/structured-output/limits retained. Supplemental metadata cannot expand effective restrictions.
Inclusion Default-on auto-include follows saved Free/Paid policy Explicit disables win. Configured Paid permits future eligible configured models; explicit enables cannot bypass hard gates.
Saved intent v4 policy/enabled/disabled controls, billing declarations and role bindings; private legacy backups Preserve absent pins, disables and Paid policy; revision-aware Save prevents lost updates; refresh/conflicts retain drafts.
Live owned-role routing Stable model-free agents, coherent saved state and pre-inference revalidation Loaded A → B changes need no reconnect; explicit C absent from host inventory blocks until an explicit reload. No automatic disposal.
Media handling Tool-free vision analysis; explicit user-authored code intent may retain router Classifier reads at most 4,000 user-text characters and attachment type/MIME only; no attachment payload/location inspection.
Delegation and repair Bounded worker → independent read-only reviewer → one authorized repair Current runtime guards and exact completion evidence; synthesis remains model-guided; no restart-durable workflow claim.
Owned slash summaries Narrow exact-message one-shot grant after matching child completion Changed parent pin blocks the stale inherited summary; no general synthetic-message bypass.
Connect/Disconnect Receipt-owned managed surface 3, exact MCP preflight, private backup, conflict refusal Preserves unrelated JSONC/plugins/defaults; receipt is ownership evidence, not package authenticity.
Usage Fixed local aggregate query, 7/30/90-day or all-time windows OpenCode-recorded cost is not an invoice. Captured records retain historical billing and binding, nullable token/cost fields and currency; no prompt/content projection. Quota and estimates remain unreported without evidence.
Runtime access check Explicitly acknowledged bounded synthetic OpenCode run OpenCode may retry; can incur real costs/retention; never automatic or quality evidence.
Ranking and benchmark qualification Existing ranking and curated restrictions retained No new winner, benchmark campaign, or quality promotion.
Provider authentication integrations Deferred OpenCode retains credentials/authentication authority; no direct OpenRouter account/catalog integration.

“Free” does not imply private inference, unlimited use, entitlement, uptime, or perpetual pricing. Model names and availability can change. The running catalog, current connection evidence and saved policy govern eligibility. Free and legacy verified-price Paid additionally require unexpired exact pricing evidence; no hardcoded free-model list authorizes access.