← Back to the Hub
Integration pending
Exo
ecosystem:exoharness
An MIT-licensed recursive harness with durable event-sourced state, forks, rewinds, sealed secrets, and sandboxed execution.
RustexternalOpen sourceIntegration pendingOwned by the agent sessions
Specification
| Category | Ecosystem watch |
|---|---|
| Language | Rust |
| How we know | exoharness/exo carries Cargo.toml; the harness layer also includes TypeScript. |
| Runtime | external |
| Interface | Local REPL and web chat |
| Source | industry watch |
| Licence | MIT |
| Continuity | Owned by the agent |
| Support | Integration pending |
| Based on | Exo (Rust and TypeScript, MIT) |
| Last verified | 2026-09-27 |
Setup and support
SuperQode guides Exo setup but does not run its remote setup script. Exo owns its event log, sandboxes, secrets, and agent lifecycle; a native connector requires a stable machine interface beyond its interactive REPL.
Runtime behaviour
Capabilities
Event-sourced agent stateFork and rewind runsSelf-modifying harnessSealed secretsSandboxed execution
Tools
sandboxed shellworkspace mountssealed secretsartifactsevent logPolicies and ownership
- +Exo owns durable state, forks, rewinds, sandboxes, and tool execution
- +Secrets are brokered by Exo and kept out of model context
- +SuperQode never downloads and executes Exo's setup script automatically
Install and authenticate
- 1
Download and review Exo's installer
SuperQode will not execute the downloaded script. Exo requires Git and Docker and pins its own Node, pnpm, and Rust toolchains.
curl -fsSL https://raw.githubusercontent.com/exoharness/exo/main/setup.sh -o setup.sh - 2
Start Exo after setup
The setup script is first-run only; exo.sh starts the REPL afterwards.
./exo.sh
