Rule candidate for review
Test the proposed rule against representative and fault cases before approval.
The method
Compile once, govern every repair
Record a bounded, repeated task once. OpenAdapt compiles the trace into a deterministic local program, replays it with zero per-run model cost, and resolves, repairs, or halts under interface drift. Here is what each step produces and where the loop deliberately stops.
How it works
From demonstration to verified operation
One lifecycle connects qualification, execution, evidence, and governed change.
- 1
Demonstrate and qualify
Show one bounded task. Review its program, risks, identities, effects, fault cases, and supported environment before certifying it.
- 2
Deploy in your boundary
Run approved browser workloads in managed execution or keep sensitive desktop, RDP, Citrix, private-network, and restricted-egress work customer-controlled.
- 3
Execute, verify, and repair
Healthy runs use no generative-model calls. OpenAdapt proves the declared effect, halts on uncertainty, and subjects every candidate repair to the workflow contract.
From trace to program
A demonstration compiles into a program you can inspect.
A single demonstration can become a governed loop that runs once per record in a worklist: bounded, identity-gated, and effect-verified per record, halting on ambiguity instead of guessing. One recorded path becomes governed execution over a queue.
openadapt-flow for-each my-bundle --records worklist.csv --out queue-bundleCompiled-program visualizer
See what a demonstration compiled into.
A recording under-specifies intent. The compiler turns it into a program you can read before it runs: each step, the resolution ladder, where an identity gate is armed, which writes carry an effect check, and every point the run can halt. Render it from the CLI as a self-contained page or Mermaid, or open the same graph in Cloud.
openadapt-flow visualize my-bundle --format html -o graph.html
Workflow catalog & halt map
Read the whole portfolio, halt by halt.
The catalog is a read-only view of compiled workflows in the workspace. Review the current workflow state before you run it.
Qualification · Human judgment
Capture the policy behind the action.
During qualification, your team can show how an institutional exception should be handled. OpenAdapt records the reviewed choice and the authority behind it. One answer never becomes policy by itself.
Permanent human decision node
Keep the choice with an authorized role whenever policy or discretion requires it.
More examples required
Collect contrasting cases when the available evidence does not justify a stable rule.
UI drift
What “repair” means, and where it stops
OpenAdapt is not an unconstrained agent. Drift ends in one of four explicit outcomes, each visible in the run report.
Automatic
Deterministic re-resolution
Structure, templates, OCR, and geometry try to re-find the recorded target. No model is required. A changed anchor is saved as an auditable bundle diff.
Optional
AI-assisted proposal
If deterministic evidence is insufficient and a model is configured, it can propose a target or confirm limited visual state. The model can be wrong, so identity, policy, and postcondition gates still decide whether execution continues.
Operator path
Human teaching and resume
A halt produces evidence for an operator. The CLI can teach a correction, and durable mode can checkpoint verified progress for authenticated approval and resume.
Unsupported drift
Refuse instead of improvise
If no configured path can establish the target or expected result, the workflow stops. OpenAdapt does not claim general adaptation to arbitrary application changes.
Availability and refusal depend on retained evidence and configuration. Identity checks cover armed steps only; system-of-record verification requires declared effects and a configured verifier. Read the measured limits.
Remote execution modes
Two ways into managed Citrix, RDP, and VDI estates
Where policy permits software inside the managed session, the runner executes in-session. Where it does not, the external lane drives the local remote-desktop client window from outside, so nothing is installed in the remote environment. Both modes keep the same identity, policy, verification, and halt contracts.
In-session
The runner is installed inside the managed session, when your policy permits it.
Managed session (Citrix / RDP / VDI)
OpenAdapt runner
Runs beside the application with native accessibility and visual evidence.
native control and evidence
Target application
The system-of-record UI inside the session.
Requires software inside the session image, so it fits estates where you control the image or policy allows an installed agent.
External black-box
The runner drives the local Citrix or RDP client window. Zero install inside the remote session.
Your workstation
OpenAdapt runner (outside the session)
Operates through pixels, keyboard, and mouse with a two-phase lease: re-resolve on a fresh frame, refuse if anything changed before delivery.
pixels, keyboard, mouse
Local Citrix / RDP client window
The vendor client you already run.
the vendor's own remote protocol
Managed session (remote)
Untouched: no agent, driver, or install inside the session.
Fits locked-down estates where nothing may be installed in the managed environment.
Real application footage
Watch the same governed loop in real applications
Choose an application, compare the recorded demonstration with its compiled replay, and open the evidence behind the result.
OpenAdaptObservingStep 1 of 33Observing the application
0:00 / 0:00Evidence
Guided view synchronized to the exact retained runtime timeline; raw footage remains unchanged.
- 1DemonstrateCapture the task and its evidence.
- 2ExecuteReplay the compiled workflow locally.
- 3Verify or haltProve the effect, or stop for review.