chio start

Start the HTTP sidecar with zero-configuration defaults and durable receipts, so an SDK or a harness can reach a kernel locally.

On this page

Start the Chio sidecar with sensible zero-config defaults.

All command families · Global flags

Usage

Command synopsistext

chio start [OPTIONS]

--listen <LISTEN> Address to listen on. Defaults to 127.0.0.1:9090 to match chio-sdk-python’s ChioClient.DEFAULT_BASE_URL. Pass 127.0.0.1:0 to bind an ephemeral port; the bound address is then printed in the startup banner. Default 127.0.0.1:9090.
--receipt-store <RECEIPT_STORE> Optional SQLite receipt store path for a durable audit log.
--allow-ephemeral-receipts Permit in-memory receipts, whose audit evidence is lost on every restart. Required to boot without --receipt-store. For local development only.
--print-config Print the chio-hermes config snippet (env vars + slash commands) on startup so users can copy/paste into their shell before running their agent. Off by default to keep the banner short.
--trust <FILE> Trust file whose issuer pins admit presented capabilities. Defaults to ~/.chio/trust.toml. Reads CHIO_TRUST.

Additional behavior

Convenience alias for chio api protect aimed at SDK quickstart and chio-hermes integration users. It runs the same axum router (capability mint/release/validate, receipt verify, tool-call evaluate, HITL approval endpoints) but with:

no upstream proxy (the catch-all /{*path} 502s loud).
durable receipts by default (pass --allow-ephemeral-receipts for the in-memory quickstart that leaves no on-disk artifacts).
a friendly startup banner that prints the bound address.

chio api protect remains the canonical name for production deployments that need --upstream, --spec, and persistent stores.