Features
Why UseAgent. The agent contract, the trust lane, the reliability story, replaceable engines, the workspace, the self-improvement loop, and the product experience, each as a deep dive.
UseAgent’s pitch fits in one sentence: a prompt becomes a durable, replayable run, executed by the coding engine of your choice inside an isolated Linux workstation, rendered live from one canonical event log, and finished with everything worth keeping captured for review.
This section unpacks that sentence one commitment at a time. Each page is a deep dive into a property the platform actually enforces, written from the shipped code rather than from aspiration.
The deep dives
The agent contract
The flagship spec. One provider-neutral event grammar with a versioned envelope, a negotiated capability map, and delivery guarantees every engine must satisfy. This is what makes engines swappable.
Trust and control
The sandbox is untrusted by design. Capability tokens, a separate gateway process on a restricted database role, one-shot human approvals, and write-only encrypted secrets.
Reliability
Runs survive backend restarts, reconnects replay exactly what live viewers saw, retries are idempotent, and releases must pass real engine journeys before they ship.
Engines
Codex, Claude, and OpenCode behind a neutral adapter. The inner loop is rented; orchestration, history, approvals, and rendering stay yours.
The workspace
A real Linux workstation per thread: repositories, terminal, a visible desktop with browser automation and recording, artifacts, and editable workpieces.
Self-improvement
Runs recall what the organization knows and propose what they learned. Every publish passes a human gate, and every recall is auditable.
Product experience
A native React surface owned end to end: one timeline grammar for every engine, a side rail of live panes, a command palette, themes, and Slack as a first-class channel.
How these pages are written
If you want the neutral reference instead of the argument, the same ground is covered dryly in Concepts, Architecture, and Product.