Skip to main content
Task-shaped entry points into the docs. Each page states plainly which parts of the surface work end to end today and which are shipped contract still landing; the authoritative list is what’s live today.

Quickstart

Install the CLI, sign in, create a project, and run a first sandbox.

Run a sandbox

Create from an image, inspect, execute, snapshot, and clean up.

Snapshots and branching

Save a sandbox’s state and fan out branches from one shared starting point.

Drive hiloop from an agent

Let a host-side coding agent use the CLI with a least-privilege credential.

Capture telemetry

Wrap any agent command with hiloop run and record what it did.

Query telemetry

SQL over every captured event, scoped by run and lineage.

Working today, end to end

Creating sandboxes from images, inspecting them, bounding them with TTLs, and deleting them work through the public API and CLI, as does the full telemetry loop: hiloop run capture, hiloop runs and hiloop query, annotations, and data views. Interactive SSH access to a running sandbox is complete, but it needs an endpoint that is off unless your deployment enables it. Buffered command execution, snapshotting, and branching work too: sandbox exec, sandbox snapshot create, and sandbox create --from <snapshot>. Volume publication works, but sandbox mounts remain refused until the mount transport lands. Secret bindings fail closed on deployments that have not enabled the complete proof-bound release path, and the guides above state the current behavior per verb.