HTTP API (Scalar)
The /api/v2/ control-plane API, Airflow 3.2.x-compatible, as an interactive Scalar reference generated from the OpenAPI spec.
Version v0.4.0 of the documentation is no longer actively maintained. The site that you are currently viewing is an archived snapshot. For up-to-date documentation, see the latest version.
Reference
References for every Leoflow surface — the HTTP API, CLI, Go packages, Python runtime, configuration, and MCP server.
References for every Leoflow surface. The HTTP API, CLI, Go, and Python references
are generated from source on every push, so they never drift from the code. The
Configuration page is hand-maintained against
internal/config — treat the server source as the final authority.
HTTP API (Scalar)
The /api/v2/ control-plane API — Airflow 3.2.x-compatible — as an interactive
Scalar reference.
CLI reference
Every leoflow command and flag, generated from Cobra.
Go packages (GoDocs)
GoDocs for the control plane, scheduler, executor, agent, and storage — one page per package, each symbol linking to its source.
Python runtime API
The task-runtime helpers your DAG code imports (XCom, staging paths).
Configuration
The LEOFLOW_* environment variables and config keys for the server.
MCP server
The Model Context Protocol server — resources and tools that expose Leoflow to agents.
The Glossary collects the core vocabulary (DAG, DagRun, XCom, Executor, …).
CLI reference
Every leoflow command and flag, generated from Cobra.
Go packages (GoDocs)
GoDocs for the control plane, scheduler, executor, agent, and storage — one page per package.
Python runtime API
The leoflow_runtime package that runs your task callable inside the container and bridges its return value to XCom.
Configuration
The LEOFLOW_* environment variables and config keys for the server.
Glossary
The core Leoflow vocabulary — DAG, Task, TaskInstance, DagRun, XCom, Executor, Agent — kept compatible with Airflow.
MCP server
The Leoflow MCP server — resources and tools for agents.