> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hexagon.autos/llms.txt
> Use this file to discover all available pages before exploring further.

# Hexagon documentation

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](https://docs.hexagon.autos/en/start/first-session.md)** · [Complete a project task](https://docs.hexagon.autos/en/start/project-task.md) · [中文](https://docs.hexagon.autos/zh-CN/index.md)

## See what completion looks like

After [installation](https://docs.hexagon.autos/en/start/install.md) 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](https://github.com/NexusFox88/docs/blob/main/resources/examples/documentation/first-session.py):

```python theme={null}
session = client.create_session(
    harness={'id': 'pi', 'version': '1.5.2'},
    sandbox_connection_id=sandbox, model_connection_id=model,
)
```

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](https://docs.hexagon.autos/en/start/first-session.md) for dependencies, Python/TypeScript execution and recovery instructions.

| Completion check | What you inspect |
| - | - |
| Identifiable work | Returned Session and Run IDs in a private journal |
| Finished task | Durable Run state is `completed`, with an actual assistant response |
| Useful artifact | Downloaded content matches `Hello from Hexagon` |
| Lifecycle completed | Session is `closed`; the exported artifact remains downloadable |

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](https://github.com/NexusFox88/docs/blob/main/resources/testing/evidence/2026-11-20-first-session-docs-cloud.json) provides an actual scoped result for the linked programs:

| Recorded observation | Python | TypeScript |
| - | - | - |
| Run / Session after cleanup | `completed` / `closed` | `completed` / `closed` |
| Exported content | 19 bytes, expected greeting verified | 19 bytes, expected greeting verified |
| Deletion record | `completed` | `completed` |
| Download after closure | Identical bytes | Identical bytes |

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

| Your goal | Primary guide |
| - | - |
| Add Agent execution to a product backend | [Backend integration](https://docs.hexagon.autos/en/build/backend-integration.md) |
| Give an Agent project files and verify its work | [Project files and context](https://docs.hexagon.autos/en/build/project-context.md) |
| Select and manage different execution combinations | [Choose integrations](https://docs.hexagon.autos/en/integrations/choose.md) |

The [complete project tutorial](https://docs.hexagon.autos/en/start/project-task.md) covers upload, fixed tests, private preview, a second modification and retained exports; [dated independent dual-SDK cloud and browser checks](https://github.com/NexusFox88/docs/blob/main/resources/testing/evidence/2026-11-20-project-docs-cloud.json) passed for the documented Vercel/Pi/Messages combination. [Use cases](https://docs.hexagon.autos/en/start/use-cases.md) explains product fit and boundaries.

## Understand where work runs

```mermaid theme={null}
flowchart LR
  A[Your application / SDK] --> C[Control plane]
  B[Console] --> C
  C --> S[Cloud Sandbox: Runtime + Harness]
  S -->|Scoped model / Tool access| C
  C --> M[Model endpoint]
  C --> T[External Tools]
```

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](https://docs.hexagon.autos/en/concepts/execution-architecture.md) and [security boundaries](https://docs.hexagon.autos/en/concepts/security-boundaries.md).

## Enter by your responsibility

| You are… | Start here | Then continue |
| - | - | - |
| Trying Hexagon | [Install](https://docs.hexagon.autos/en/start/install.md) | [First Session](https://docs.hexagon.autos/en/start/first-session.md) → [What happened](https://docs.hexagon.autos/en/start/what-happened.md) |
| Building an application | [Backend integration](https://docs.hexagon.autos/en/build/backend-integration.md) | [Events](https://docs.hexagon.autos/en/build/stream-events.md), [approvals](https://docs.hexagon.autos/en/build/approvals.md), [recovery](https://docs.hexagon.autos/en/build/recovery.md) |
| Operating a deployment | [Self-hosting](https://docs.hexagon.autos/en/operate/self-host.md) | [Networking](https://docs.hexagon.autos/en/operate/networking.md), [diagnostics](https://docs.hexagon.autos/en/operate/observability.md), [backup](https://docs.hexagon.autos/en/operate/backup-restore.md) |
| Extending the project | [Development setup](https://docs.hexagon.autos/en/contribute/development.md) | [Code map](https://docs.hexagon.autos/en/contribute/codebase.md), [tests and evidence](https://docs.hexagon.autos/en/contribute/testing.md) |

Coding Agents can use the [integration reading guide](https://docs.hexagon.autos/en/agents.md). Browse the [complete documentation directory](https://docs.hexagon.autos/en/directory.md) for all existing pages, including provider guides, concepts, extension guides and reference entries.

## Check capabilities and evidence

Start with [Sandbox capabilities](https://docs.hexagon.autos/en/integrations/sandboxes.md), [Harness contracts](https://docs.hexagon.autos/en/integrations/harnesses.md) and [model protocols](https://docs.hexagon.autos/en/integrations/model-protocols.md), then inspect [dated verified combinations](https://docs.hexagon.autos/en/integrations/verified-combinations.md). 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](https://docs.hexagon.autos/en/operate/troubleshooting.md) or [resource reconciliation](https://docs.hexagon.autos/en/operate/reconciliation.md) when progress or cleanup is uncertain.

Read [changes and upgrade notes](https://docs.hexagon.autos/en/changelog.md) before changing versions. Product docs remain drafts under active completion; the [coverage ledger](https://github.com/NexusFox88/docs/blob/main/resources/docs/product/coverage.json) identifies unfinished assets. Exact API/SDK/configuration references are still being completed; current implementation-backed details remain in the [SDK guide](https://github.com/NexusFox88/docs/blob/main/resources/sdk/README.md) and linked source. The repository's [release policy](https://github.com/NexusFox88/docs/blob/main/resources/release-policy.json) does not yet approve publication. No public hosting or download channel is implied by these local pages.

[Repository README](https://github.com/NexusFox88/docs/blob/main/resources/README.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.