Your agent fleet.
Embedded anywhere.
Your interface. Your infrastructure stack.
Embed agents into the product you already build.
Many Sandboxes. Many Harnesses. Many tools.
One request. A fleet behind it.
Your backend turns one release review into separate Sessions and Runs.
PROVIDER KEYS STAY IN THE CONTROL PLANE
Headless execution. Native to your product.
All Harnesses. All Sandboxes. Your tools.
From a model call
to a system you can operate.
The interesting part starts after the prompt. Give your agents a workspace, continuity and scoped access — with a clear record of what happened.
Execute on your terms.
Bind a Sandbox, a versioned Harness and a model endpoint to each Session. Your application owns the experience.
Session lifecycle ↗Access without handing over keys.
Keep original provider and upstream credentials in the control plane. Give task code scoped authority through protected connections.
Understand the boundary ↗Disconnect. Reconnect. Continue.
Observe durable Run events and resume from a committed cursor. Losing the client connection does not cancel the work.
Execution and recovery ↗A control plane.
Not another black box.
Lifecycle above. Execution below.
Choose a layer to see what belongs where.
Lifecycle is infrastructure.
Sessions, Runs, cloud resources and durable events live in the control plane. PostgreSQL persists the state. Your application connects through one headless API.
▼
▼│
▼
Your backend.
Meet your agent fleet.
Embed execution with Python, TypeScript or REST. Create a Session, submit a Run, and deliver its events and results through your own application.
- 01 Start your control plane
- 02 Connect a Sandbox and model
- 03 Bring the code into your application
Submission returns a Run, not a completed answer. The complete guide covers result polling, artifacts and cleanup.
Many combinations.
One execution API.
The fleet above is one illustration. Choose compatible Sandbox, Harness and tool connections for your own application.
Each Session pins its own configuration. Catalog availability does not imply that every combination is supported. View verified combinations ↗
Headless by design.
Visible when it matters.
Configure connections. Inspect the request. Follow a Run through execution. Console is your operations surface.

Clear boundaries.
Fewer surprises.
Is Hexagon a Sandbox provider?
No. Hexagon orchestrates execution on your connected cloud Sandbox accounts. Local versus hosted describes the control plane, not where agent execution runs.
Do I need to use a particular agent?
Choose a compatible versioned Harness. Built-in Pi and OpenCode are available, alongside OCI adapters and templates. Check the exact provider, distribution and model protocol before running.
What happens when my application disconnects?
The Run continues. Reconnect with the original Run identity to inspect durable events. Cancellation and closing a Session are explicit operations.
Is this production-ready?
Hexagon is in developer preview. Real-cloud evidence is scoped to specific combinations; it is not a universal compatibility guarantee or a stable-release SLA. Review the support ledger before deployment.
Read the support ledger ↗Who pays for execution?
Your connected cloud and model accounts fund execution. Lifecycle behavior and idle billing depend on the provider. Close unused Sessions and confirm resource cleanup.