BetterOffice is an open-source office suite that edits DOCX, XLSX and PPTX files directly, with people and AI agents working in the same document. The BetterOffice editors run on Rust engines and are licensed under Apache-2.0. They are built to run in a browser, on a server or inside an agent workflow.
Editing the file itself
The project says every editor works on the file itself, with no conversion when a file opens or saves. Native OOXML editing keeps untouched file parts intact when a document is round-tripped. That matters for anyone who has watched a spreadsheet or deck lose formatting after passing through another tool.
The same Rust engines handle opening, editing, layout and rendering. In the demos, users redline a contract while an agent proposes the next clause, build a quarterly budget and see dependent formulas update, and edit a process map’s shape data before dropping it into a Word or PowerPoint report.
How agents and people share a document
As an open-source office suite, BetterOffice treats agents as first-class editors rather than add-ons.
BetterOffice treats the document as a CRDT, a data structure that lets concurrent edits merge. Every editor, human or AI agent, is a peer on that structure. Agents don’t get a sidebar. They get a cursor, the same undo and the same tracked-changes attribution as any co-author.
Several features follow from that design:
- Live cursors and selections, with co-editing over any WebSocket relay
- Offline edits that sync when peers reconnect
- Attributed agent edits that appear as tracked changes, inline diffs and before-and-after previews, which reviewers accept or reject in the editor
- Editing history where an accepted agent proposal can be undone as a single step
An agent edits through the same operations a person uses. Human review is a suggesting mode, so there’s no separate diff dialog to learn.
Packages for developers
The editors install from npm and render inside an app, with no embeds or external services, and documents never leave the page. Developers can drop in React components, build on framework-free JavaScript cores, or call Rust and Python APIs for headless processing and agent workflows.
The npm packages cover each file type:
- A DOCX core for parsing, CRDT editing, page layout and rendering, plus a React editor and viewer
- A spreadsheet core for parsing, formula calculation and rendering, plus a React editor and viewer
- A slides core for parsing, editing and rendering, plus a React editor and viewer
- Agent tools to search, read, edit and preview DOCX, XLSX and PPTX files through a TypeScript SDK or a local MCP server
Teams keep control of document storage, deployment and collaboration infrastructure. A package guide covers supported runtimes and fonts, and release notes list version-specific changes.
Who it suits
Teams that build document features into their own products are the obvious audience. They can self-host, keep documents inside their own infrastructure and avoid sending files to an outside service. Those that run agents over contracts, budgets or slide decks get attribution built in, so a reviewer can see what the agent changed and reject it.
Anyone with a large existing library of Word, Excel and PowerPoint files also benefits from the lossless approach, since the files stay in their original format.
What the benchmarks claim
The site publishes benchmarks generated by a GitHub Actions job, comparing BetterOffice commit 3a49caad with LibreOffice 26.2.3.2. One comparison reports about 40 ms a page for BetterOffice against about half a second a page for the other suite.
A second test ran the same model through 288 graded runs with two toolsets. An edit counted only if the requested change was present and nothing else in the file moved. Treat the figures as the project’s own numbers: per-document results and the methodology are on its benchmarks site, and independent testing would be the next step.
Where to start
Developers can try the editors online or read the docs for setup, APIs and format support. The open-source office suite pitch is clearest for teams building agent features into a product, who need edits that are attributed and reviewable. Check the package guide for runtime support first, then run your own documents through it before relying on the benchmark claims.
Source: BetterOffice