Free local start · MIT licensed

Record your first workflow in OpenAdapt Desktop.

Desktop gives you a visual path from permissions to a supervised run. The CLI provides the same local compiler and governed runtime for developers and CI. You don't need a Cloud account or model API for either.

Recommended first workflow

OpenAdapt Desktop

Start with one small read-only task in a real app. Use test data if the app provides it. Desktop keeps the recording, compiled workflow, run status, and evidence in one place.

  1. 1 · Grant local permissions
    Allow the screen capture and input access that Desktop needs for the app you choose.
  2. 2 · Choose a read-only task
    Pick one repeatable task that does not change application or external state.
  3. 3 · Record the demonstration
    Perform the task once while Desktop records the actions and target evidence.
  4. 4 · Review the compiled workflow
    Check the steps, inputs, targets, risks, and expected result before any replay.
  5. 5 · Run it under supervision
    Watch the first replay and inspect its result and retained evidence.
  6. 6 · Qualify unattended use
    A state-changing, unknown, consequential, or irreversible action must pass qualification before its first actuation.

Desktop is available for Windows, macOS, and Linux. A browser workflow downloads matching Chromium once. Native, RDP, and Citrix workflows use their own substrate paths.

Developer and CI path

OpenAdapt CLI

Use the command line for a repeatable installation check, exact artifact inspection, or automation in a terminal and CI environment.

1 · Install

python -m pip install --upgrade openadapt

2 · Check the installation

openadapt quickstart

3 · Inspect the report

Confirm the VERIFIED outcome and review the retained actions, result evidence, and privacy-safe receipt.

The quickstart runs a successful synthetic task. It checks the installation before you record real work. It requires Python 3.10–3.12, and the first browser action downloads matching Chromium once.

Optional after local success

Keep running locally, qualify unattended use, or connect Cloud.

Qualify the workflow

Qualify the exact application, environment, identity checks, expected result, failure cases, and deployment boundary before the first state-changing, unknown, consequential, or irreversible action.

Qualify the workflow

Connect this computer

Pair the local runtime with your Cloud workspace for approved workflow handoff, run history, and collaboration. Pairing is free; managed runs use the Cloud plan.

Connect to Cloud