Current main (unreleased)
mainbranch after v0.7.1. Do not assume these contracts exist in the 0.7.1 binary or container. Pin a commit only for evaluation and wait for the next tagged release before depending on them in production.1.0 authoring and distribution
Current main publishes versioned OpenAPI and recursive sequence JSON Schema contracts, adds schema_version, format upgrades, an OpenAI-compatible generate-and-repair loop, and a reusable GitHub workflow gate. Release distribution now includes Windows, checksum-verifying npm and pipx launchers, and automated Homebrew formula publishing. See the authoring guide.
Local-to-hosted workflow
orch8 dev starts the persistent SQLite-backed Studio by default. The same line adds cloud template pulling, connector catalog search and installation, a crash-recovery demo, deploy manifests, MCP authoring tools, and signed package publishing and search.
Embedding and operations
napi-rs and PyO3 bindings expose the shared Rust validator to Node.js and Python. The Grafana pack gains alert-ready assets, and the stability, migration, tunnel, authentication, and framework-adapter contracts are now documented alongside the implementation.
Durable Agent Handoff Protocol
Current main adds a framework-neutral agent handoff contract above the continuity engine: portable work offers, runtime passports, execution receipts, placement-policy compilation, and HTTP, MCP, process, and mobile gateway manifests. The orch8 portablecommands inspect the protocol, wrap existing agents, compile policies, and evaluate conformance evidence. These commands are unreleased.
The matching versioned HTTP surface includes protocol discovery, offer and gateway validation, receipt verification, trust-boundary profiles, and server-signed conformance certificates. A certificate requires the fixed mandatory checks; an incomplete evidence set cannot establish conformance. A manifest cannot grant itself attested trust.
See the engine's agent continuity guide and checked-in examples for request contracts and local evaluation. The stable continuity features remain documented in the 0.7 continuity guide.
Worker claim fencing
Each task claim now carries a monotonic claim_epoch. Heartbeat, completion, and failure requests must echo it so a delayed process from an expired lease cannot mutate a newer owner's task. Attempt history is available atGET /workers/tasks/{id}/attempts.
Transactional event-batch intake
POST /api/v1/events/batch accepts up to 100 PostgreSQL-outbox events. producer_event_id is deduplicated by tenant and event name, allowing a producer to retry an unknown delivery result safely.
Worker stream protocol v2
The negotiated gRPC worker stream adds the fencing metadata and hardened connect/acknowledgement behavior while the REST pull protocol remains available for any-language workers.
Control-plane and mobile hardening
The same development line adds push-wake governance, cluster drain and tenant storage-placement migrations, plus stricter mobile and managed control-plane validation. Consult the OpenAPI document generated by the exact commit you run for request and response schemas.
Ready to try Orch8?
One command to install. Then run your first local sequence.
curl -fsSL https://orch8.io/start.sh | sh