genoffice
Free, open-source AI Office suite: Docs, Sheets, Slides, PDF, Markdown and HTML editors with a built-in AI agent, plus a `genoffice` CLI and agent skill so Claude Code, Codex and Cursor can create and edit real .docx/.xlsx/.pptx files locally. Bring your own key. macOS, Windows & Linux.
Runssource: GitHubhomepageTypeScriptApache-2.0commit 69b4ce0560a7
TypeScript, Apache-2.0 licensed. The project labels itself: ai, ai agent, claude code, cli, codex, cursor, docx and excel.
genoffice runs. An Argusic agent installed it in 15 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
GenOffice repository installs, builds all 6 apps, passes all ~9000+ unit tests across all 18 workspaces, and the Electron shell launches successfully in a container with no code changes required.
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 96 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 pre-installed but .nvmrc requires v22; npm complained about unsupported engine for some packages1 minute
- No Rust toolchain (cargo/rustc) on PATH — sheets xlsx sidecar requires it1 minute
- Electron SUID sandbox helper not configured (container environment)0.5 minutes
- Install time
- 15 minutes
- Cold machine to finish
- 17 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- npm test exited 0, 18 workspaces, ~9000+ JS tests + 168 Rust tests all passed; npm run build:all built all 6 apps without errors; npx electron --no-sandbox --version returned v43.3.0 and app/main process stayed up until SIGTERM timeout
- Model tokens used
- 105,766
- Exact commit tested
- 69b4ce0560a7
- 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.
**Tests:** 18 workspaces, all passed — zero failures across ~9,000+ tests and 168 Rust tests. **Build:** All 6 apps (docs, sheets, slides, pdf, markdown, shell) built cleanly with `electron-vit… **Launch:** Electron v43.3.0 starts and stays up; only dbus noise from container (expected, no syst… Three environment fixes were needed for a fresh container — standard setup, no code changes. tokens used 105,766 All tests passed, build succeeded, and the Electron app launches. Let me compile the final report. **Install:** `npm install` succeeded (only engine warnings for Node 22.12.0 vs required ^22.13.0 — … **Tests:** 18 workspaces, all passed — zero failures across ~9,000+ tests and 168 Rust tests. **Build:** All 6 apps (docs, sheets, slides, pdf, markdown, shell) built cleanly with `electron-vit… **Launch:** Electron v43.3.0 starts and stays up; only dbus noise from container (expected, no syst… Three environment fixes were needed for a fresh container — standard setup, no code changes.
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 Apache-2.0, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Took 15 minutes to install, slower than the median of the 32 comparable projects Argusic has measured.
Of the 33 agent projects Argusic has installed and timed, genoffice was the 25th fastest to reach a running state, and 25 of 33 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
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs | 100.00 | 0.05 | |
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.16 |
Topics (from GitHub)
aiai-agentclaude-codeclicodexcursordocxexcellibreoffice-alternativelocal-firstmarkdown-editormicrosoft-office-alternativeoffice-suitepdf-editorpdf-to-wordpowerpointpptxskillsspreadsheetxlsx
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/genoffice)Questions
- Does genoffice run?
- Yes. genoffice runs. Argusic installed and launched it on a clean machine in 15 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test genoffice?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 69b4ce0560a7. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test genoffice?
- The run that produced this verdict cost $0.05: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does genoffice take to install?
- 15 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 genoffice need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing genoffice?
- 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 genoffice compare with the alternatives?
- Of the 33 agent projects Argusic has installed and timed, genoffice was the 25th fastest to reach a running state, and 25 of 33 reached one at all.
- Where is the evidence for genoffice?
- 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.