Compatibility & Evidence
Match each Chio artifact to its version, the platforms it runs on, and the protocol versions it speaks.
On this page
A Chio release is a set of artifacts that speak the same protocol versions: the chio command line, the chio crate, and one SDK per application language.
Each row below is read from the package manifests at the documented release. Pick the row for your language, install it with its package manager, and the protocol table tells you which documents and wire versions it accepts.
Release artifacts
| Artifact | Version | Install | Runs on |
|---|---|---|---|
chio CLI | 0.1.0 | install.sh | macOS arm64 and x86_64, Linux x86_64 and arm64, Windows x86_64 |
Rust crate chio | 0.1.0 | cargo add chio | Rust 1.94, edition 2021 |
TypeScript @chio- | 0.1.0 | npm install @chio- | Node >=22 |
Python chio-sdk | 0.1.0 | pip install chio-sdk | Python >=3.11 |
Go chio-go | release tag | go get github. | Go 1.23.0 |
JVM world.chio:chio-sdk-jvm | 0.1.0 | Gradle or Maven | Java 17 |
.NET Backbay.Chio | 0.1.0 | dotnet add package Backbay.Chio | net8.0 |
Swift chio-swift | 0.1.0 | Swift Package Manager | iOS 15, macOS 13 |
C++ chio | 0.1.0 | vcpkg add port chio | C++17, CMake |
The Python package imports as from chio import Computer, USD. The SDK reference lists every framework adapter package with its own version.
Signed release binaries
The installer downloads the signed chio binary for the host platform and verifies it before installing. Signed binaries ship for macOS on Apple silicon and Intel, Linux on x86_64 and arm64, and Windows on x86_64; release tags are signed in backbay-labs/chio.
curl -fsSL https://chio.computer/install.sh | sh
chio --versionchio-cli 0.1.0
You should see the CLI version from the artifact table. Every terminal that runs a Quickstart or example command then uses the same binary.
Protocol and schema versions
| Document or protocol | Version | Defined in |
|---|---|---|
Capability token | chio. | |
Kernel receipt | chio.receipt.v1 | |
HTTP receipt in exported evidence | chio_ | |
Hosted MCP edge | MCP 2025-11-25 | |
Process host protocol | chio.process.v1, ABI v4 | |
Work commands | chio. |
The kernel ABI is closed and versioned by KERNEL_ABI_VERSION, and its operation IDs are never reused.
One conformance corpus checks every language
The conformance harness runs one scenario corpus against each language adapter and reports per scenario. chio certify evaluates a conformance corpus and signs a certification artifact for it.
chio conformance fetch-peers
chio conformance run --peer all --report json --output conformance.jsonPeers are js, python, go, and cpp. The fetched adapter binaries are pinned in a lockfile, and a normal fetch fails closed when every matching peer is unpublished.
Read more in chio conformance.
Recorded examples carry their own trust
Recorded examples retain the source revision and binary that produced their output. The Quickstart and the downloadable application hosts operate their own application state. The proof-room transcripts reproduce repository evidence with fixture trust, test clocks, and fixed chain inputs.
Configure proof verification for your application with trust you select independently. A captured success with fixture trust configures nothing for an artifact your application produces, and a signer included in an artifact never becomes trusted because it signed that artifact.
Source checks for the OpenAI adapter
Contributors can check the adapter's dispatch and refusal paths without provider credentials. In a clone of backbay-labs/chio, run its focused tests with the pinned toolchain:
cargo test -p chio-openai-adapter execute_tool_call_success
cargo test -p chio-openai-adapter execute_tool_call_runtime_admission_denies_before_tool_server_dispatch
cargo test -p chio-openai-adapter execute_tool_call_fails_closed_on_nonce_preflightThe first asserts tool content and a receipt. The second checks refusal before backend invocation. The third checks that a nonce preflight is never returned as completed output.
Each example governs the path it names
- The delegated document application demonstrates delegated tool authority. Signed swarm task graphs are admitted on the task graph path.
- The manifest library imports OpenAI function schemas with explicit side-effect and pricing declarations. The resulting manifest goes through the normal signing, registration, and capability lifecycle.
- Database guards recognize a specific set of tool names and markers. A custom tool name alone declares no database operation.
- Framework examples that run a custom MCP host exercise that host. The packaged wrappers carry their own invocation lifecycle, documented in Wrap an MCP Server.