Hexagon
[ HEADLESS AGENT API / OPEN SOURCE ]

Your agent fleet.
Embedded anywhere.

Your interface. Your infrastructure stack.
Embed agents into the product you already build.
Many Sandboxes. Many Harnesses. Many tools.

[ Apache-2.0 ] Self-managed. Developer preview.
01 / REQUEST

One request. A fleet behind it.

Your backend turns one release review into separate Sessions and Runs.

YOUR PRODUCT
[ / ] RELEASE WORKSPACEReview this release.POST /your-backend/review →
Release review ready.✓ Code review✓ Research brief✓ Operations summary
YOUR BACKEND / OWNS FAN-OUT + RESULTS
HEXAGONSESSION / RUN / EVENTS
E2BBOX A
SESSION A / CODE AGENT
Pi Harness
RUNTIME SUPERVISES EXECUTION
ModalBOX B
SESSION B / RESEARCH AGENT
OpenCode
RUNTIME SUPERVISES EXECUTION
VercelBOX C
SESSION C / OPERATIONS AGENT
Codex
RUNTIME SUPERVISES EXECUTION
SCOPED TOOL CALLS
GitHubLinear
GitHub / Linear
SCOPED TOOL CALLS
ExaNotion
Exa / Notion
SCOPED TOOL CALLS
SlackYour API
Slack / Your API
MODEL + TOOL ACCESS IS BROKERED
PROVIDER KEYS STAY IN THE CONTROL PLANE
request → your backend
SCROLL TO FOLLOW THE REQUEST ↓ILLUSTRATIVE FLOW / NO LIVE EXECUTION
Skip the story ↓

Headless execution. Native to your product.
All Harnesses. All Sandboxes. Your tools.

PYTHONTYPESCRIPTREST APIYOUR UI
[ 01 / EMBED THE CAPABILITY. OWN THE EXPERIENCE. ]

An agent feature.
Not another destination.

A button, a workflow, a background job. Keep your interface and your users. Add agent execution through your backend.

YOUR PRODUCT 01
[ / ]ACME / CODE REVIEW
PULL REQUEST #128

Ship with a second pair of eyes.

+ billing/reconcile.ts +42 −8
Your review appears here, inside your product.

Your UI. Your brand. Your users.

YOUR BACKEND 02
SERVER-SIDE SDK / RESTsession = createSession(…)run = submit(…)
HEXAGON API
SESSION → RUN → EVENTS

Stream events. Deliver results.
Keep credentials server-side.

YOUR AGENT FLEET 03
E2B / SANDBOX A[01]
CODE AGENTPi Harness
CALLS →GitHubLinear
MODAL / SANDBOX B[02]
RESEARCH AGENTOpenCode Harness
CALLS →ExaNotion
VERCEL / SANDBOX C[03]
OPERATIONS AGENTCodex Harness
CALLS →SlackYour API
ILLUSTRATIVE FLOW / NO LIVE EXECUTION

Each box has its own execution boundary. Tools use configured, scoped connections. Exact combinations depend on Harness, provider and permissions.

Embed an agent in your backend ↗
[ 01 — THE PLATFORM ]

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 ↗
[ 02 — BUILT WITH BOUNDARIES ]

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 APPLICATION Python / TypeScript / REST
│
▼
HEXAGON CONTROL PLANESessions · Runs · Events · Access
│
▼
│
▼
CLOUD SANDBOXRuntime + selected Harness
SCOPED ACCESSYour models & connected tools
Local or hosted control plane. Cloud Sandbox execution.
[ 03 — SMALL API. REAL EXECUTION. ]

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.

  1. 01 Start your control plane
  2. 02 Connect a Sandbox and model
  3. 03 Bring the code into your application
Read the setup guide ↗
EXAMPLE / CONNECTION IDS REQUIRED↵

Submission returns a Run, not a completed answer. The complete guide covers result polling, artifacts and cleanup.

[ 04 / CHOOSE YOUR FORMATION ]

Many combinations.
One execution API.

The fleet above is one illustration. Choose compatible Sandbox, Harness and tool connections for your own application.

SANDBOX
E2BModalVercelBlaxelSpritesFly MachinesUpstashInstaboxFreestyleBoatAgent37
HARNESS
PiOpenCodeCodexHermesOpenClawAiderClaude CodeDeepSeekCustom OCI
TOOLS
GitHubLinearSlackNotionExaFirecrawlGoogle DriveMCPYour API

Each Session pins its own configuration. Catalog availability does not imply that every combination is supported. View verified combinations ↗

[ 05 — NOTHING HIDDEN BEHIND THE API ]

Headless by design.
Visible when it matters.

Configure connections. Inspect the request. Follow a Run through execution. Console is your operations surface.

HEXAGON / API PLAYGROUNDPRODUCT CAPTURE
Hexagon API Playground with Sandbox, model and Harness configuration beside generated SDK and REST requests
One control plane. The same API in your code and in Console.
[ 06 — BEFORE YOU SHIP ]

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.

YOUR STACK. YOUR BOUNDARIES. YOUR CONTROL.

Your product.
Now with an agent fleet.

Start building ↗Explore the source ↗