OpenMAIC
Open Multi-Agent Interactive Classroom, Get an immersive, multi-agent learning experience in just one click
Runssource: GitHubTypeScriptMITcommit d4ef5faa7636
TypeScript, MIT licensed.
OpenMAIC runs. An Argusic agent installed it in 21 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Dependencies install and build succeed. Test suite runs 7147/7249 passing with 1 trivial assertion mismatch (scannedChars). The Next.js dev server starts and answers HTTP 200 on localhost:3000.
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.
- Node.js v18.19.1 installed but project requires >=20.9.03 minutes
- pnpm not available - npm install -g pnpm failed (EACCES)2 minutes
- rolldown binding-linux-x64-gnu optional dependency not installed - node_modules missing native binary2 minutes
- Install time
- 21 minutes
- Cold machine to finish
- 26 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- pnpm test exited 0: 649 passed, 7147 passed, 1 failed, 9 skipped; curl -s -o /dev/null -w '%{http_code}' localhost:3000 returned 200 after pnpm dev booted Next.js 16.1.2
- Model tokens used
- 82,216
- Exact commit tested
- d4ef5faa7636
- 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.
tokens used 82,216 Here's my full report: **Errors encountered:** 1. **Node.js version too old (v18.19.1, required >=20.9.0)** — Fixed by downloading and using Node … 2. **pnpm not installed** — Fixed via the `get.pnpm.io` install script, then symlinked the native b… 3. **`@rolldown/binding-linux-x64-gnu` optional dependency missing** — Lockfile had it as optional,… **What works:** - `pnpm install` — all dependencies install, all workspace packages build (DSL, generation, storage… - `pnpm test` — 649 test files passed, 7147 tests passed, 1 test failed (a trivial assertion mismat… - `pnpm build` — `next build` succeeds, all routes compiled (API routes, pages, middleware) - `pnpm dev` — dev server starts and `curl http://localhost:3000` returns HTTP 200
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 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 3 times, so the result is not a one-off.
What did not, or is not known
- Took 21 minutes to install, slower than the median of the 5 comparable projects Argusic has measured.
Of the 6 TypeScript projects Argusic has installed and timed, OpenMAIC was the 6th fastest to reach a running state, and 5 of 6 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.
Run history
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/openmaic)Questions
- Does OpenMAIC run?
- Yes. OpenMAIC runs. Argusic installed and launched it on a clean machine in 21 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test OpenMAIC?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit d4ef5faa7636. 3 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test OpenMAIC?
- The run that produced this verdict cost $0.08: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does OpenMAIC take to install?
- 21 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 OpenMAIC need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing OpenMAIC?
- 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.
- How does OpenMAIC compare with the alternatives?
- Of the 6 TypeScript projects Argusic has installed and timed, OpenMAIC was the 6th fastest to reach a running state, and 5 of 6 reached one at all.
- Where is the evidence for OpenMAIC?
- All 3 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.