← Back to the Hub
Integration pending
Exo
ecosystem:exoharness
A recursive agent and harness architecture that splits durable state from agent logic, so a run can stop, resume, fork and rewind — and the agent can rewrite the harness it runs on.
RustexternalOpen sourceIntegration pendingOwned by the agent sessions
Specification
| Category | Ecosystem watch |
|---|---|
| Language | Rust |
| How we know | exoharness/exo carries Cargo.toml and is Rust 71% by bytes; the harness layer on top is TypeScript. |
| Runtime | external |
| Interface | Local REPL and a hosted web chat |
| Source | industry watch |
| Licence | MIT |
| Continuity | Owned by the agent |
| Support | Integration pending |
| Based on | Exo (Rust core with TypeScript harnesses, MIT) |
| Last verified | 2026-09-06 |
Setup and support
Not yet runnable from SuperQode. Exo owns its own event log, sandboxes and secret broker, and its setup script pins its own node, pnpm and Rust toolchains, so a route would have to drive it as an external harness rather than embed it.
Runtime behaviour
Capabilities
Event-sourced agent stateFork and rewind runsSelf-modifying harnessSealed secretsSandboxed executionPluggable executors (Codex, Claude Code, Cursor SDK)
Tools
sandboxed shellworkspace mountssealed secretsartifactsevent logPolicies and ownership
- +Exo owns durable agent state: the event log, artifacts, forks and rewinds
- +Secrets are brokered by the harness; raw values are kept out of model context
- +Tool commands run in Exo-managed sandboxes under its own network policy
- +No commands are executed by SuperQode until a connector is built and tested
Install and authenticate
- 1
Install Exo independently
Read the script before running it. 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 the REPL
setup.sh is first-run only; afterwards ./exo.sh starts Exo and attaches the REPL.
./exo.sh
