Skip to main content
Hexagon is an open-source, self-hostable Agent control plane for applications. Your application submits work; Hexagon manages cloud execution resources, task state, Tool calls, events, and artifacts around a continuing work context. Read this page when evaluating where Hexagon fits or when encountering Session, Run, and Harness for the first time.

Four outcomes for your application

A Harness is the engine that runs the Agent loop: it interprets the task, interacts with a model and chooses execution steps. Hexagon supplies the surrounding task and resource lifecycle. Its Console is useful for configuring and investigating that lifecycle; your application normally integrates through the Python SDK, TypeScript SDK or HTTP API.

Follow a project task

Suppose your application lets users upload a Web project and ask an Agent to add filtering:
  1. Configure, validate, and enable a cloud Sandbox connection and model connection.
  2. Choose a compatible Harness, create a Session, and upload project files.
  3. Submit the change request and retain its Run ID.
  4. Hexagon executes in the cloud Sandbox. Your application observes durable events and presents progress.
  5. The Agent edits files, runs tests, and places deliverables in the Run’s artifact directory.
  6. Retrieve results and artifacts, optionally exposing an authorized private Web preview.
  7. Submit follow-up work as another Run in the same Session.
  8. Close the Session and confirm cloud cleanup; exported artifacts and completed records remain queryable.
Each step depends on the selected combination’s capabilities and evidence. Inspect actual test results rather than accepting the Agent’s statement that tests passed.

Responsibilities

This diagram shows responsibility boundaries; actual request paths depend on connection type. Provider credentials remain in the control plane. Protected model/Tool credentials use scoped access. Values you explicitly put into Session env or variables are readable by Sandbox code.

Three core objects

Session is a continuing context with conversation, workspace, and pinned configuration. It is not one physical machine; recovery strategies can replace underlying resources. Run is one submission’s execution record. A Session currently permits one active Run. Client disconnection does not cancel it. Agent template is optional reusable configuration. Create Sessions directly; use templates when you need configuration reuse/versioning. Template edits do not overwrite existing Session configuration.

Deployment and execution locations

Local and hosted refer to the control plane. A local control plane uses a local database/private configuration, while real Agent tasks still execute in cloud Sandboxes. Local Docker is not required as a replacement for actual cloud execution. The control plane retains execution records and exported artifacts. Workspace, process, and memory preservation vary by provider/lifecycle action. A durable Session does not imply an immortal process. Next: use cases or local installation. Sources: architecture, acceptance journey.