Docs · Autopilot
Autopilot
Any AI agent workload, bounded and audited.
Autopilot runs agents on Hangar the way Hangar runs services: durable changes are commits that people review, and ephemeral runs are direct requests to Crossplane. An agent is one more author of git commits, held to a tier of tools, a path scope and a budget that can only narrow at runtime.
- Defining or running an agent? Start with the user guide.
- Installing or operating the gateway? See the admin guide.
- Design, plan, decisions and diagrams live in Hangar’s
docs/autopilot/: the roadmap (M0 to M5), the design, 37 one-page diagrams and the decision log. - The mark and its files: brand.
What is here
| Piece | What it is |
|---|---|
| The AI gateway | src/autopilot/engine/ (moved from clearance v0.26.1 with its history, R-3a, Built): the MCP surface, sessions, the run tree, budgets and requested limits, the tool registry and dispatch, the model proxy, agent definitions and their schema, the runtime catalog, the human inbox, person controls, run results and trigger history. engine/core.py is its one link to Clearance: from R-3b (Built) the Clearance core’s HTTP API through its generated client, with the outage policy and the outbox; the gateway’s runtime state is in its own database (admin/gateway-database.md) |
| Clearance | Policy (CEL), path, repo and field scope, the hash-chained evidence and its Postgres store, authentication, the deployment gate, provenance and clearance-api (its own repo, https://github.com/jfillman/clearance): from R-3b a service, the Clearance core, which the gateway calls over HTTP (its client pinned in pyproject.toml); it imports nothing from Hangar and carries no Hangar names; Hangar’s policy for the Glidepath and Airframe tools is a bundle that ships here (policy/hangar/) and the core loads from configuration |
| Autopilot code | src/autopilot/: the Glidepath and Airframe tool backends, the AgentRun manifest, triggers, Preflight, and the builder of the Hangar Gateway (gateway.py: the engine plus the Hangar pack and backends) |
| Agent definitions | agents/: durable, schema-validated, one per workload shape |
| Preflight | preflight/cases/: cases that score an agent definition before it is promoted |
| AppSpec planner | Turns one statement of intent into an ordered change set across the tenants, app and gitops repos |
AgentRun |
built in airframe (XRD, composition, function-agentrun) and the cluster repos (grants, agent-sandbox); airframe-drafts/README.md points there |
Status: running on hangar-dev (gateway-v0.4.0 calling clearance v0.29.0’s core, with autopilot-api serving the
runtime’s reads, since the R-4 cutover on 2026-11-03). Releases are the image tags
(gateway-v*, runtime-v*, runtime-<name>-v*); the Python package itself is not versioned. See the README for
what is built and tested, and what is not.