open-slide
A slide framework built for agents.
Runssource: GitHubTypeScriptMITcommit 65914fea5f70
TypeScript, MIT licensed. The project labels itself: agent, react and slides.
open-slide runs. An Argusic agent installed it in 4.5 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Core framework, CLI, and demo build successfully, all 449 tests pass, lint passes, both CLIs respond to help commands, the Next.js marketing site is the only failure (OOM-killed in this resource-constrained container)
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 60 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page. 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.
- web:build (Next.js marketing site) killed by OOM (exit 137)3 minutes
- Node.js v18.19.1 too old — rolldown needs styleText from node:util, Next.js needs >=20.9.00.5 minutes
- pnpm not available with the system Node.js 180.3 minutes
- tsdown bundler failed: 'Failed to import module unrun'0.2 minutes
- Install time
- 5 minutes
- Cold machine to finish
- 5 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- pnpm test exited 0 (449 passed, 33 files); pnpm build produced core, cli, and demo dist; both CLIs respond to --help; pnpm check passed
- Model tokens used
- 23,195
- Exact commit tested
- 65914fea5f70
- 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.
23,195 All systems verified. Here's the final assessment: - **install_succeeded**: true — `pnpm install` completed, all workspace packages resolved. - **launch_succeeded**: true — `pnpm test` exited 0, and `pnpm build` succeeded for `@open-slide/co… - **errors**: 4 errors encountered: 1. Node.js v18.19.1 too old (rolldown needs `styleText` from `node:util`, unavailable in Node 18)… 2. `pnpm` not bundled with the system Node — fixed by installing pnpm 10.17.0 via `npm install -g… 3. `unrun` not installed — `tsdown` requires it as a peer dependency — fixed by `pnpm add -Dw unr… 4. `apps/web` (Next.js marketing site) OOM-killed (exit 137) during build — unfixable in this con… - **test_depth**: `tier1_real` — ran the actual test suite; 449 passed, 33 files, 0 failures. - **verified_how**: `pnpm test` exited 0 (449 passed, 33 files), `pnpm build` produced `packages/co… - **final_state**: Core framework builds, all 449 tests pass, demo static site is generated, both C…
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 4.5 minutes, faster than the median of the 51 comparable projects Argusic has measured.
- 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.
- Measured 2 times, so the result is not a one-off.
Of the 52 agent projects Argusic has installed and timed, open-slide was the 21st fastest to reach a running state, and 36 of 52 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.
- A quick evaluation: it was running 4.5 minutes after the clone.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs | 100.00 | 0.01 | |
| Argusic Runner | 1/3 | Did not run | 20.00 | 0.02 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/open-slide)Questions
- Does open-slide run?
- Yes. open-slide runs. Argusic installed and launched it on a clean machine in 5 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test open-slide?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 65914fea5f70. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test open-slide?
- The run that produced this verdict cost $0.01: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does open-slide take to install?
- 4.5 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 open-slide need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing open-slide?
- 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 open-slide compare with the alternatives?
- Of the 52 agent projects Argusic has installed and timed, open-slide was the 21st fastest to reach a running state, and 36 of 52 reached one at all.
- Where is the evidence for open-slide?
- 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.