Skip to content

Product components and release admission

OpenAdapt is one product. Install openadapt and use openadapt flow …. The public repositories below supply the product's launcher, compiler, recorder, desktop cockpit, agent bridge, and trust surfaces.

A release appears as Production only while the current canonical record contains a live, non-revoked admission for that exact release. The browser checks the record hash and each live artifact authority. It does not use an older admission when the newest one expires, is revoked, or loses an artifact.

Product release admission and workflow qualification are separate contracts. Workflow qualification binds one exact bundle to the application and environment where it will run, including its identity, effect, and policy contracts.

Read the Production admission contract

Product components

Component Current release admission Public role
OpenAdapt No current verified Production admission. Installer, meta-package, and unified openadapt flow command.
OpenAdapt Flow No current verified Production admission. Canonical demonstration compiler and governed runtime for Browser, native Windows, native macOS, native Linux, RDP, and Citrix/VDI.
OpenAdapt Cloud No current verified Production admission. Managed control plane for organizations, exact-hash admission, browser runners, reports, billing, and usage.
OpenAdapt Desktop No current verified Production admission. Windows, macOS, and Linux cockpit for recording, compilation, qualification, replay, and local review.
OpenAdapt Agent No current verified Production admission. Governed bridge from MCP clients and Agent Skills to exact Flow bundles.
OpenAdapt Capture No current verified Production admission. Canonical native recorder for screen, mouse, keyboard, timing, window scope, and media. Windows UIA evidence is emitted with the captured action. The shared observer protocol defines the macOS Accessibility and Linux AT-SPI integration boundary. RDP and Citrix remain pixel-observed at the remote boundary.
OpenAdapt documentation No current verified Production admission. Version-bound product, operation, security, and qualification documentation at this site.

Browser recording stays in Flow because DOM identity, field geometry, source-time secret masking, and Playwright execution use one browser session contract. Flow can launch Chromium or attach to one selected local tab. The Chrome extension code in the Capture repository does not define a second compiler or direct replay path. An extension acquisition path must satisfy the same authenticated event, evidence, masking, and frame-binding contract before Flow accepts its recording.

Trust and interoperability libraries

Repository Lifecycle Public role
openadapt-privacy Experimental Optional PII/PHI sanitization for configured persistence, logs, and artifact egress.
openadapt-types Experimental Shared interoperability schemas for contributors and integrators.

Evaluation and model development

Repository Lifecycle Public role
openadapt-ml Research Optional model-training research. Recording, compiling, and replaying a workflow does not use it.
openadapt-evals Research GUI workflow evaluation research. The compiler path does not depend on it.
openadapt-grounding Research UI grounding mechanisms and model adapters.
openadapt-retrieval Research Demonstration retrieval mechanisms.

How the pieces fit

flowchart LR
    C[openadapt-capture<br/>native recording] --> F[[openadapt-flow<br/>canonical compiler]]
    B[Playwright browser<br/>recording] --> F
    F --> R[Deterministic<br/>replay bundle]
    A[openadapt-agent<br/>governed bridge] --> F
    ML[optional models] -.resolve under drift.-> F
    E[openadapt-evals] -.measures.-> F

See Qualification evidence for bounded feature and backend results. Evidence for one task and environment does not extend to another workflow.