excel
Online Collaboration Excel
Runssource: GitHubhomepageTypeScriptMITcommit 0a7763aa39b4
TypeScript, MIT licensed. The project labels itself: collaboration, excel, react, spreadsheet, xlsx and yjs.
excel runs. An Argusic agent installed it in 2 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
All 116 test suites (1077 tests) pass across all three packages (excel-collab, demo/frontend, demo/backend). Dependencies installed. vite dev server and backend runtime require Node 20+ and yjs peer dependencies respectively.
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.
- lerna CLI uses import.meta.filename (undefined in Node 18) and require() of ES module2 minutes
- yarn install triggers postinstall script that runs lerna build with Node 20+ features1 minute
- vite 8.3.0 requires Node ^20.19.0 || >=22.12.0 — server/build unavailable on Node 18
- demo/backend requires @y/y peer dependency for websocket — cannot launch
- Install time
- 2 minutes
- Cold machine to finish
- 11 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- npx jest --forceExit --detectOpenHandles --no-cache in packages/excel-collab: 111 suites, 982 passed ; packages/demo/frontend: 2 suites, 32 passed ; packages/demo/backend: 3 suites, 63 passed, total 116 suites, 1077 tests passed
- Model tokens used
- 59,480
- Exact commit tested
- 0a7763aa39b4
- 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.
Test Suites: 111 passed, 111 total Tests: 982 passed, 982 total All tests confirmed. Let me now produce the final structured result. All test output verified: - excel-collab: 111 suites, 982 tests passed - demo/frontend: 2 suites, 32 tests passed - demo/backend: 3 suites, 63 tests passed tokens used 59,480 All tests confirmed. Let me now produce the final structured result. All test output verified: - excel-collab: 111 suites, 982 tests passed - demo/frontend: 2 suites, 32 tests passed - demo/backend: 3 suites, 63 tests passed
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 2 minutes, faster than the median of the 4 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.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 5 collaboration projects Argusic has installed and timed, excel was the 2nd fastest to reach a running state, and 5 of 5 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 2 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)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/excel)Questions
- Does excel run?
- Yes. excel runs. Argusic installed and launched it on a clean machine in 2 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test excel?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 0a7763aa39b4. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test excel?
- The run that produced this verdict cost $0.11: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does excel take to install?
- 2 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 excel need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing excel?
- 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 excel compare with the alternatives?
- Of the 5 collaboration projects Argusic has installed and timed, excel was the 2nd fastest to reach a running state, and 5 of 5 reached one at all.
- Where is the evidence for excel?
- 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.