OpenAdapt

Automate the UI-only work your APIs can’t reach.

OpenAdapt is the verified execution layer for consequential work trapped behind human interfaces. It turns a demonstration into an inspectable workflow that runs across browser, Windows, macOS, Linux, RDP, and Citrix/VDI. Healthy runs use no generative-model calls. Consequential actions are identity-gated, declared results are verified, and uncertainty halts for review instead of becoming a wrong click.

Use a supported API when one fits. Use OpenAdapt when the interface is unavoidable and the outcome needs proof.

Website · Documentation · Desktop downloads · OpenAdapt Cloud · Qualify a workflow

Repository role: this is the flagship OpenAdapt project, the source of pip install openadapt, and the stable community entry point. The compiler and governed runtime are implemented in openadapt-flow. This repository provides the unified openadapt CLI and compatibility surface, not a second engine. Lifecycle: Beta.

Try it locally

OpenAdapt requires Python 3.10–3.12. Install the browser capability for the bundled tutorial:

python -m pip install --upgrade 'openadapt[browser]'

Run the complete bundled tutorial with one command. It needs no account, target application, API key, or operating-system automation permissions:

openadapt quickstart

The tutorial records and compiles a synthetic task, certifies it with the shipped clinical-write policy, and runs it under the Standard profile. A separate read-only API confirms the saved record outside the screen that performed the write. The healthy run returns VERIFIED with no model or Cloud call.

You now have:

• openadapt-quickstart/recording/: the demonstrated interaction and retained target evidence
• openadapt-quickstart/bundle/: the inspectable compiled workflow
• openadapt-quickstart/run/REPORT.md: the ordered actions, evidence, outcome, and any halt reason
• openadapt-quickstart/run/receipt.json: the privacy-safe local receipt for the synthetic verified run

Inspect the program and its deployment gaps:

openadapt flow visualize openadapt-quickstart/bundle --out graph.html
openadapt flow lint openadapt-quickstart/bundle

The bundled workflow is a tutorial, not a production certification. Qualifying a real workflow adds its application boundary, action risks, identities, effect verifiers, fault cases, and deployment policy. Continue with the five-minute walkthrough.

Record your workflow

The browser path is an explicit capability, so native and remote-only installs do not carry the Playwright driver:

openadapt flow record --backend web --url https://your-app.example --out rec
openadapt flow compile rec --out bundle --name my-workflow
openadapt flow replay bundle --url https://your-app.example --run-dir run

The first browser action downloads its matching Chromium build once. A native desktop, RDP, or Citrix workflow never downloads or imports it.

Install only the capabilities needed for native or remote work:

python -m pip install "openadapt[capture]"          # local human demonstration
python -m pip install "openadapt[capture,windows]"  # Windows UI Automation
python -m pip install "openadapt[capture,macos]"    # macOS Accessibility
python -m pip install "openadapt[capture,linux]"    # Linux AT-SPI
python -m pip install "openadapt[capture,rdp]"      # RDP transport
python -m pip install "openadapt[privacy]"          # PII/PHI scrubbing

For the visual authoring and review experience, install OpenAdapt Desktop.

Image provenance: headless synthetic fixture from Desktop PR #93 commit 1f50259ffb052776742b284a493eb9c735caa122; no live run, engine sidecar, account, customer data, or physical input. SHA-256: 5616f0b0812a5e366f58e448689600e16eeab234aaf92ec6d49133efa0be33ee. The final release hash will be updated after Desktop 0.15.

What makes it different

Verified business effects

A click succeeding is not proof that the intended transaction committed. OpenAdapt separates action delivery from outcome verification. Workflows can bind consequential writes to an independent interface, a separate read-only session, or persisted-state reacquisition before reporting VERIFIED.

Fail-closed execution

Before a consequential action, the runtime can check authorization, workflow state, record identity, target uniqueness, and the fresh application view. Afterward it waits for settled state and evaluates the declared effect. If the contract cannot be established, it returns evidence and halts.

Deterministic healthy runs

The compiler retains structural, accessibility, visual, OCR, spatial, and transition evidence from the demonstration. The runtime uses the strongest signals available on each surface. A generative model may propose a governed repair when explicitly allowed, but it is not on the healthy execution path.

Governed repair

Repairs are versioned changes, not permission to improvise. Candidate repairs can be reviewed, tested against the workflow’s qualification contract, promoted, and rolled back.

One workflow model, multiple surfaces

OpenAdapt keeps portable workflow intent separate from environment-specific bindings:

Remote execution operates from a customer-controlled runner through the visible client. It does not require OpenAdapt software inside the remote session. Every workflow is qualified against its exact application, version, environment, identity contract, and effect verifier rather than inheriting a blanket platform claim.

See the substrate model, qualification evidence, and CLI reference for the full contracts.

Local, customer-controlled, or managed

Raw recordings and live observations stay local by default. Artifacts cross a boundary only through explicit sanitization and exact-byte approval. Review the trust center before choosing a deployment.

The local launcher, compiler/runtime, Desktop application, substrate adapters, verification interfaces, and basic qualification tools are MIT licensed. OpenAdapt Cloud is the commercial multi-tenant control plane for managed operation, fleet governance, billing, and enterprise integrations. Local safety-critical verification is not paywalled.

Evidence

Read the benchmark method and comparison and the RVU audit case study. Results belong to their named task and environment; workflow qualification defines what can be claimed for a new deployment.

Project map

• This repository: installer, unified CLI, release compatibility, and stable project URL
• openadapt-flow: canonical compiler, governed runtime, CLI implementation, and conformance tests
• Documentation: installation, workflow authoring, qualification, operation, deployment, and reference material
• Desktop: native record, inspect, qualify, execute, and review application

The pre-1.0 monolith remains available under legacy/ for migration history. New product and engine development belongs in openadapt-flow.

Contributing and support

Launcher, packaging, and unified-CLI changes belong here. Compiler, runtime, verification, repair, and backend changes belong in openadapt-flow.

• Contribution guide
• Open an issue
• GitHub Discussions
• Discord community
• Report a vulnerability privately

OpenAdapt is maintained by OpenAdaptAI and released under the MIT License.