bento
Bento, the office suite that fits in a file
Runssource: GitHubhomepageTypeScriptMITcommit 01000838496e
TypeScript, MIT licensed. The project labels itself: mit license, office, office 365, office suite, office tools, office365, open source and powerpoint.
bento runs. An Argusic agent installed it in 8 minutes and hit 6 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The entire Bento monorepo builds from source with Node 24.18.0: npm install, tsc -b, vite build, and postbuild-compress produce a conformant 677KB Bento_Slides.bento.html that passes the splice-contract shell gate, while the CRDT sync convergence rig passes 45368 checks and all 30+ core test suites (slides, kernel, spaces, dash, type, i18n, offline, security) exit with 0.
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.
- test-autosave.ts fails directly from repo root - fake-indexeddb not in root node_modules0.5 minutes
- test-sanitize.ts fails directly - imports slides/src/model extensionless (TS bundler resolution)0.5 minutes
- test-slide-store.ts same extensionless-import issue0.3 minutes
- test-validate.ts same issue0.3 minutes
- test-clipboard.ts same issue0.3 minutes
- shell-gate.mjs called with wrong path (dist-single at root vs slides/dist-single)0.1 minutes
- Install time
- 8 minutes
- Cold machine to finish
- 9 minutes
- Errors hit and fixed
- 6 hit, 6 fixed with no human help
- How the result was proved
- npm run build:single completed with exit code 0 (tsc -b, vite build, postbuild-compress to 677KB); node scripts/shell-gate.mjs passed conformance gate; node scripts/test-sync.ts: ALL PASS (45368 checks); node scripts/test-preview.ts: 28/28 checks passed; dozens of additional test scripts all reported pass
- Model tokens used
- 88,925
- Exact commit tested
- 01000838496e
- 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 2, 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.
slides-theme: 10 doc-index: 11 i18n-coverage: all 8 core locales complete autosave: 8 shell-gate: passed All tests passed, all builds succeeded, no errors remaining. exec /bin/sh -lc 'echo "ALL TESTS PASSED - compiling final report..."' in /work/repo succeeded in 0ms: ALL TESTS PASSED - compiling final report... tokens used 88,925
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 8 minutes.
- Recovered from all 6 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 8 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)
mit-licenseofficeoffice-365office-suiteoffice-toolsoffice365open-sourcepowerpointself-hostedsingle-page-appslidesslideshareslideshowslideshow-galleryslideshow-makerslideshows
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/bento)Questions
- Does bento run?
- Yes. bento runs. Argusic installed and launched it on a clean machine in 8 minutes, hitting 6 errors on the way, and recorded the session.
- How did Argusic test bento?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 01000838496e. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test bento?
- The run that produced this verdict cost $0.06: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does bento take to install?
- 8 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 bento need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing bento?
- 6 things broke in the recorded run, and 6 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for bento?
- 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.