OpenScribe
OpenScribe is an open-source AI scribe that records patient encounters and generates structured clinical notes automatically. You keep full control over data, workflows, and patient privacy with no vendor lock-in.
Runssource: GitHubhomepageTypeScriptMITcommit dddf1c30fcf8
TypeScript, MIT licensed. The project labels itself: ai, clinical, clinical informatics, ehr, electron, healthcare, healthcare application and healthtech.
OpenScribe runs. An Argusic agent installed it in 12 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The monorepo installs, TypeScript compiles, and 260 unit tests pass across all packages. The Next.js web app builds and serves HTTP 200. Three source files were patched to fix crypto availability in Node --test workers.
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 100 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.
- crypto.randomUUID() not available as bare global in Node --test workers3 minutes
- globalThis.crypto unavailable in Node 18 test workers, causing Web Crypto API errors in secure-storage.ts2 minutes
- Node.js 18.19.1 too old for Next.js 16 (needs >=20.9.0)1 minute
- @tailwindcss/oxide native binary missing (pnpm install ran under Node 18)1 minute
- Install time
- 12 minutes
- Cold machine to finish
- 16 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- pnpm run test: exit 0, all 260 tests pass; npx next build apps/web: build succeeds; npx next dev: HTTP 200 on /
- Model tokens used
- 616,061
- Exact commit tested
- dddf1c30fcf8
- 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
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 1, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
**Test verification:** `pnpm run test` (full suite): 260 individual tests across 33 test files, all… **App build:** `npx next build apps/web` succeeds. App starts with `npx next dev` on port 3099 and … 2026-10-29T19:32:30.517323Z ERROR codex_core::session: failed to record rollout items: thread 01a18… tokens used 616,061 All tests pass. Let me compile the final report: **Install:** `pnpm install` succeeded. Needed Node.js >=20.9.0 for Next.js 16; installed Node 20.18… **Fixes applied:** 1. `packages/storage/src/audit-log.ts` and `packages/storage/src/encounters.ts` – `crypto.randomUUI… 2. `packages/storage/src/secure-storage.ts` – `getCrypto()` threw "Web Crypto API is not available"… **Test verification:** `pnpm run test` (full suite): 260 individual tests across 33 test files, all… **App build:** `npx next build apps/web` succeeds. App starts with `npx next dev` on port 3099 and …
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.
- Recovered from all 4 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.
What did not, or is not known
- Took 12 minutes to install, slower than the median of the 236 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 237 ai projects Argusic has installed and timed, OpenScribe was the 180th fastest to reach a running state, and 168 of 237 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
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)
aiclinicalclinical-informaticsehrelectronhealthcarehealthcare-applicationhealthtechllmlocal-firstmedtechopen-sourceprivacyself-hostedtypescript
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/openscribe)Questions
- Does OpenScribe run?
- Yes. OpenScribe runs. Argusic installed and launched it on a clean machine in 12 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test OpenScribe?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit dddf1c30fcf8. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test OpenScribe?
- The run that produced this verdict cost $0.12: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does OpenScribe take to install?
- 12 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 OpenScribe need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing OpenScribe?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does OpenScribe compare with the alternatives?
- Of the 237 ai projects Argusic has installed and timed, OpenScribe was the 180th fastest to reach a running state, and 168 of 237 reached one at all.
- Where is the evidence for OpenScribe?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.