OpenAdapt
For EHRs, payer portals, and any app your team clicks through. A person or an agent shows the task; OpenAdapt turns it into a local program that repeats the steps with no model calls, checks each save, and stops when something doesn't match.
Runssource: GitHubhomepagePythonMITcommit 7ae7ebc02048
Python, MIT licensed. The project labels itself: agent harness, ai agents, browser automation, citrix, computer use agents, demonstration compiler, desktop automation and deterministic replay.
OpenAdapt runs. An Argusic agent installed it in 0.4 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
openadapt CLI installs and runs; tutorial flow records, compiles, certifies, and verifies a MockMed synthetic clinical workflow with VERIFIED receipts; --break-it correctly halts when the system of record rejects the write; MCP agent serve starts and serves workflows over stdio.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 90 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- onnxruntime pthread_setaffinity_np errors flood stderr during OCR/vision operations
- openadapt package has no __main__.py so `python -m openadapt` fails
- break-it tutorial run took ~10 min to complete due to container CPU constraints
- Install time
- under a minute
- Cold machine to finish
- 64 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- openadapt flow tutorial: VERIFIED receipt with 6/6 steps ok, 2/2 effects confirmed, 0 model calls, 208s. openadapt quickstart --break-it: HALTED receipt with 0/2 effects, store unchanged. openadapt-agent serve --allow-run: printed serving 1 workflow(s) over local stdio and exited 0. pytest: 288 passed, 6 skipped in 2.8s.
- Model tokens used
- 284,195
- Exact commit tested
- 7ae7ebc02048
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
284,195 Everything is done. Here's the summary: **Install**: `pip install -e .[dev]` completed in ~24 seconds with all dependencies resolved (opena… **Verification (tier1_real)**: - `openadapt flow tutorial` — ran the full 5-stage MockMed lifecycle end-to-end: record, compile, c… - `openadapt quickstart --break-it` — ran the same certified bundle against a backend that rejects … - `openadapt-agent serve --allow-run --bundles <bundle>` — started successfully, printed `serving 1… - `pytest` — **288 passed, 6 skipped** in 2.8s (no failures). **Issues encountered (all cosmetic)**: 1. ONNX Runtime `pthread_setaffinity_np` warnings flood stderr during OCR — suppressible with env v… 2. `python -m openadapt` fails due to missing `__main__.py` — the `openadapt` CLI command works fin… 3. Tutorial took longer than expected (~3-10 min per run) due to container CPU constraints on Playw…
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 0.4 minutes.
- Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 0.4 minutes after the clone.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
agent-harnessai-agentsbrowser-automationcitrixcomputer-use-agentsdemonstration-compilerdesktop-automationdeterministic-replayeffect-verificationgui-automationhealthcare-automationhuman-in-the-looplocal-firstmcprdprpaself-healing-automationui-automationworkflow-automationworkflow-compiler
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/openadapt)Questions
- Does OpenAdapt run?
- Yes. OpenAdapt runs. Argusic installed and launched it on a clean machine in 0 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test OpenAdapt?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 7ae7ebc02048. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test OpenAdapt?
- The run that produced this verdict cost $0.27: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does OpenAdapt take to install?
- 0.4 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does OpenAdapt need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing OpenAdapt?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for OpenAdapt?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.