Supported releases
Use the OpalSpan Downloads page and the verified release record below to select current artifacts. Components have independent versions.
Capable Windows CLI 0.39.12, Linux CLI 0.39.11 and Mac-preview CLI 0.39.11 are published, with Daemon/Rescue 0.24.19 and Bridge 1.21.265. Windows/Linux legacy CLI remains 0.17.9. Independently published Diagnostics remains 0.16.3 on Windows/Linux and 0.18.6 on Mac; the Windows03912 package deliberately retains its original signed Windows Diagnostics0.16.2 companion.
Canonical Mech configuration and prospective native-credit naming preserve existing provider bindings, purchased rights and signed history. The compatible Bridge reader was verified before the new naming defaults were selected; effective settings remain unchanged.
Canonical native origins and versioned machine identities retain old-profile and signed-history compatibility. Fresh Windows, Linux XDG and macOS profiles use OpalSpan defaults; existing state moves only through explicit quiesced migration with current-value rollback and original provider/refresh custody. Compatible transport-helper readers retain historical helper output. Bridge packages the canonical private Mech runner with a same-byte legacy alias for explicit operator paths. Windows03912 adds canonical OpalSpan Host/Diagnostics executable aliases and complete identical-byte sidecars, with signed legacy anchors and original service/installation identities retained. Its actual newly signed setup passed isolated install/repair/uninstall and public readback without changing ordinary profiles; exact Windows delivery. Windows/Linux packages passed isolated signed lifecycle qualification and all four native catalogs passed public readback. Mac remains build/static-only technical preview; publication does not claim native Keychain/lifecycle or fleet-wide installed adoption. See the current delivery and Mac preview limits.
Retained Full-v3 telemetry evidence
Explicit Full-v3 telemetry adds OS-reported CPU limiting evidence to the per-logical-processor utilization, busiest processor and interval/coverage feed through CLI and Mech. Present restrictions, interval events, historical firmware records, configured policy and system pressure retain source/time/known-reason meanings. Missing sources remain unavailable; temperature/clocks/activity alone do not prove thermal or power throttling. Old Full-v1/Full-v2 grants and defaults remain unchanged; new collection is an explicit selected-device instruction. Existing aggregate CPU meaning, grants, defaults, sampling cadence and time-series storage remain. Utilization is evidence, not a diagnosis or throttling claim.
Installed Windows and Linux supervisor/worker adoption, real CLI/Mech readback and complete24/24and2/2logical-processor interval coverage passed. Linux daemon cgroup counters reported zero increments only in their covered source intervals; missing hardware indicators did not establish thermal state. Windows CLI0.39.6 installed signature/hash was verified. Mac publication has compile/static signature and public-readback evidence only, not native lifecycle or installed acceptance. See the verified delivery and limits.
Observed macOS coverage
Earlier coverage is historical, not general availability or a claim every Mac/OS has passed native lifecycle acceptance. Match each package to the hardware where it executes. Mac startup duration remains unsupported. Preserve Gatekeeper, quarantine and privacy permissions; no bypass to make a preview work.
Versioned signed records and retained legal/public generations keep exact source/ hash identity. Current feature code does not prove provider/local-consent activation. See getting started and troubleshooting.