Package and repository lifecycle¶
OpenAdapt the product (the demonstration compiler) is what most people need. Underneath it sits a set of open-source libraries and infrastructure that the compiler and its research build on. This section is for contributors and integrators who want to use those pieces directly.
Product first
If you want to compile and run a workflow, start with Get started. The libraries below are the building blocks behind OpenAdapt, not the way most users interact with it. Each links to its source repository, where its own README is the source of truth.
Lifecycle labels¶
These labels describe the public role of a repository, not the quality of every module inside it:
- Beta: current product surface; validate per workflow.
- Experimental: implemented but not a supported production contract.
- Research: evidence or model work, not required by deterministic replay.
- Deprecated: retained for history or migration; no new integrations.
Product and optional components¶
| Repository | Lifecycle | Public role |
|---|---|---|
| OpenAdapt | Beta | Installer/meta-package and unified openadapt flow dispatcher. |
| openadapt-flow | Beta | Canonical compiler and governed runtime. Browser is the reference path; other backends have separate maturity labels. |
| openadapt-cloud | Beta launch candidate | Control plane for managed browser workflows. Its bounded non-regulated recorder is live-provider qualified; the full paid purchase-to-run lifecycle remains pending. |
| openadapt-desktop | Experimental | Desktop authoring and teaching companion. Native artifacts and the release pipeline are qualified, but no complete native prerelease is published and the full operator lifecycle is not yet proven. |
| openadapt-capture | Experimental / pre-alpha | Optional cross-platform recording library. Its standalone package still documents the earlier data-collection topology. |
| openadapt-privacy | Experimental | Optional PII/PHI scrubbing used on configured persist, log, and upload paths. |
| openadapt-types | Experimental | Shared interoperability schemas; contributor-facing, not an end-user product. |
Research components¶
| Repository | Lifecycle | Public role |
|---|---|---|
| openadapt-ml | Research | VLM training, inference, and demonstration-conditioning work. Not required by the healthy compiler path. |
| openadapt-evals | Research | GUI-agent and demonstration-conditioning evaluation infrastructure. |
| openadapt-grounding | Research | UI grounding experiments and model adapters. |
| openadapt-retrieval | Research | Demonstration retrieval experiments. |
Deprecated¶
| Repository | Lifecycle | Public role |
|---|---|---|
| openadapt-agent | Deprecated | Superseded execution direction being folded into openadapt-flow; do not build new integrations on it. |
How the pieces fit¶
flowchart LR
C[openadapt-capture<br/>optional recording] --> F[[openadapt-flow<br/>canonical compiler]]
F --> R[Deterministic<br/>replay bundle]
ML[openadapt-ml<br/>grounding / identity models] -.optional on-prem appliance.-> F
E[openadapt-evals<br/>benchmarks] -.measures.-> FThe compiler is the product. Capture can feed it demonstrations, the ML layer can supply optional on-prem models, and evals measures adjacent research. This page intentionally does not expose internal developer tools as product components. See What works today for integrated feature and backend maturity.