What happened
Tbreak reported on 11 October 2026 that ArtCraft developer Brandon Thomas has expanded the project’s open-source software work to Microsoft Office-style applications. WordCraft targets word processing, GridCraft spreadsheets and DeckCraft presentations. The apps are free downloads, described as independent projects rather than Microsoft products, and their repositories label them alpha software. The readiness percentages in the report come from the projects’ own documentation, not from independent compatibility testing.
WordCraft estimates that it is about 60% of the way to replacing Word for real work. Its documentation describes a ribbon-led interface and features such as styles, tables, tracked changes, references and mail merge. It reads and writes DOCX and lists support for ODT, RTF, HTML and Markdown; it also offers PDF export. The project’s remaining priorities include testing on more real-world DOCX files, preserving charts and SmartArt more reliably, improving pagination and adding native printing. Those gaps matter when documents must retain their layout across applications.
GridCraft estimates about 50% readiness for real work. Its documented spreadsheet features include formulas, tables, conditional formatting, charts and PivotTables. The project says it covers 501 of Excel’s 523 worksheet functions and 89% of the ribbon commands in its catalogue. Those are measures of breadth, not a guarantee that a particular workbook will behave identically. The roadmap calls out XLSX fidelity on real files, very large workbooks, multi-threaded recalculation and deeper chart support. Its XLSB and ODS import is narrower: the report says it handles worksheet data using saved values rather than formulas.
DeckCraft puts its readiness at about 55%, despite claiming 79% feature breadth. Its repository lists slide masters, layouts, themes, shapes, pictures, tables, charts, transitions and animations, as well as opening and saving PPTX files and exporting PDFs and slide images. The report notes that a long feature list does not prove that presentations from other software will look or behave identically.
All three applications expose command-line, JSON control and MCP interfaces, so agents can invoke application actions. WordCraft lists operations for entering text, inspecting and rendering documents, and saving files; GridCraft exposes cell, formula, formatting and chart operations; DeckCraft makes more than 200 commands scriptable and supports undo. Ready-made builds are linked from the repositories, and the projects describe their code as dual-licensed under MIT or Apache-2.0. Project branding and bundled assets have separate terms.
What the archive adds
Our earlier coverage of ArtCraft’s Office alternatives framed the core distinction: a fast clone is not necessarily a dependable replacement. This report adds the developers’ readiness estimates and more specific compatibility caveats; it is a new fact on a known story, not a new launch.
Trend signal
This supports agent-ready software exposes capabilities: the applications expose commands through CLI, JSON and MCP rather than relying only on mouse-driven interfaces. The report also makes clear that exposing actions is not the same as making outcomes reliable; file compatibility and verification remain separate problems.
Why now
The report describes the current repositories as alpha and offers a more current status than earlier accounts that placed some projects at pre-alpha or approaching alpha. The change is a status update, not evidence that the remaining compatibility gaps have been resolved.
Why it matters
For teams considering alternatives to subscription office software, free downloads and broad feature lists lower the cost of experimentation, but the cost of a bad migration can still be high. A document that loses tracked changes or shifts page breaks, a workbook that silently drops formulas, or a presentation that changes layout can undermine real work. The project estimates help calibrate expectations: these are usable experiments, not proven replacements.
The command interfaces also make the projects relevant to AI workflows. Agents can act through the same underlying operations as people, which may be more robust than simulating clicks. But the report establishes access to commands, not the correctness of generated spreadsheets or decks. Teams should treat application-level verification as a separate requirement and test with representative files before trusting the tools in production.
Limits and uncertainty
The readiness percentages are self-assessments and the report provides no independent benchmark, test corpus or methodology for them. Feature counts do not establish fidelity on a team’s documents, formulas, charts or presentations. The source describes planned work and documented interfaces, but does not show that all features perform reliably in daily use, that agents complete tasks correctly, or that the applications can replace Microsoft Office across an organization. It also does not establish long-term maintenance, support guarantees or a migration path for existing teams.
Skill to build now
Build a small compatibility test pack from copies of files your team actually uses: a DOCX with tracked changes and complex layout, an XLSX with important formulas and charts, and a PPTX with media or animations. Open and edit each in the relevant ArtCraft app, save it, then reopen it in the original application and compare the result. That catches practical fidelity failures before anyone considers a wider switch.
Reader takeaway
ArtCraft’s three Office-style apps already expose substantial functionality and automation interfaces, but their own teams still put real-work readiness around 50–60%. Treat them as promising alpha projects: test the files and workflows you depend on, and verify saved outputs before relying on them.