Skip to main content
Hexagon is a self-hostable, open-source Agent control plane. Your application creates a continuing Session, runs tasks in cloud Sandboxes, observes durable events, and retrieves results and artifacts. For example, upload a Web project, ask an Agent to implement filtering, inspect its tests and preview, then continue in the same workspace. Create your first Session · Complete a project task · 中文

See what completion looks like

After installation and connection setup, the first tutorial creates a direct Session; saving an Agent template is optional. This excerpt is taken from the complete Python program:
The complete program persists a submission key and Session/Run IDs, submits a task, polls its result, downloads artifacts, closes the Session and reads an artifact after closure. The excerpt alone does not include those steps. Use the tutorial for dependencies, Python/TypeScript execution and recovery instructions. These are the tutorial’s expected checks, not fabricated output or a claim of a fresh cloud run. A model saying “done” does not replace them. Cloud/model usage is billed through your configured accounts. The 2026-11-20 first-Session record provides an actual scoped result for the linked programs: Both used Vercel Sandbox, Pi 1.5.2 and the configured Messages endpoint with deepseek-ai/DeepSeek-V4-Flash. This dated result covers the first task and retained artifact; it does not establish Tools, approvals, preview or other combinations. Original resource IDs stay in private journals. The complete example is the runnable entry point; copying only the creation excerpt leaves an open Session to manage.

Choose your next task

The complete project tutorial covers upload, fixed tests, private preview, a second modification and retained exports; dated independent dual-SDK cloud and browser checks passed for the documented Vercel/Pi/Messages combination. Use cases explains product fit and boundaries.

Understand where work runs

The control plane owns Session/Run state, durable events, credentials and cloud resources. Runtime supervises Harness processes inside the cloud Sandbox. Original provider/model/Tool credentials stay in the control plane; the guest receives scoped access. “Local” and “hosted” describe the control plane’s location, not local versus cloud task execution. See execution architecture and security boundaries.

Enter by your responsibility

Coding Agents can use the integration reading guide. Browse the complete documentation directory for all existing pages, including provider guides, concepts, extension guides and reference entries.

Check capabilities and evidence

Start with Sandbox capabilities, Harness contracts and model protocols, then inspect dated verified combinations. Registration, supported capability and real execution evidence are separate facts; there is no blanket guarantee for every cross-product. A client disconnect does not cancel a Run. Explicitly close unused Sessions and reconcile unknown operations before claiming cleanup. Use troubleshooting or resource reconciliation when progress or cleanup is uncertain. Read changes and upgrade notes before changing versions. Product docs remain drafts under active completion; the coverage ledger identifies unfinished assets. Exact API/SDK/configuration references are still being completed; current implementation-backed details remain in the SDK guide and linked source. The repository’s release policy does not yet approve publication. No public hosting or download channel is implied by these local pages. Repository README