As an experiment, we gave Claude Code the OOXML spec, a concrete editor architecture, and a Playwright-based test suite. The agent iterated in a (Ralph) loop over a few nights and produced a working editor from scratch.
Core text editing works today. Tables and images are functional but still incomplete. MIT licensed.
Please auto-ban any "We gave Claude/Gemini/Grok/OpenAO/Qwen/Mistral/WhateverLLMAI the spec and..."
"and..." resolves to:
- "and now we have this impressive result you won't believe!"
100% of the time this is attention seeking, live debugging - no value at all.
Don't waste people's time. Any sound and reasonable story about results without misusing the public's eye is welcome, for example:
- One year after - 10 hard problems we found - extensive pro/contra comparison with other solutions - maintaining such a AI app for one year
Otherwise: please auto-ban.
Also, it's effortless. Not interesting at all if you can't share any insight about the project, because you don't know how it works under the hood and how many architectural problems were solved (or not)
FWIW the bug I found is that your comment parser assumes the w:date attribute represents a useful timestamp of when comments are made. It does not - a bug in Word causes it to save it as ISO8601 local time but _without timezone_, rendering it useless if more than one user across different timezone edits the document. Instead, you need to cross reference the comment with a newer comment part and find a dateUtc attribute. The above is, of course, completely undocumented.
For now, we mostly rely on testing with our own and customer docs. In practice, we were seeing solid results after a couple of days of keeping Claude working in the loop and giving lots of feedback: .docx files along with screenshots annotated to highlight what didn’t work.
Does it become exponentially harder to add the missing features or can you add everything else you need in another two days? I'm guessing the former but would be interested to see what happens.
Are you going to continue trying? I ask because it's only been two days and you're already on Show HN. It seems like if you waited for it to be more complete, it would have been more impressive.
1. I don't know what the "Docxtemplater" button does, but it eats my document without warning and that's annoying.
2. It would be nice if the page came with some example .docx files we could see it work on.
The threshold for caring about experiments is exponentially higher in 2026 thanks to half baked vibe slop.
Non-functioning software and demoware comes fast and cheap, regardless of author.
> we gave Claude Code the OOXML spec
Having used the former a lot and read the latter in detail, uhhh…
Trim down the claims here, clarify the editor subset you plan to be supporting, and map the “last 90%”’s to honestly reflect the product you are pushing.
If “tables” and “images” aren’t there I’m quite skeptical about content controls and other key OOXML constructs being addressed meaningfully. The full OOXML footprint chokes OpenOffice out of procurements, rich OOXML documents choke half-way-there implementations (which was the whole point of the format).
As is pointed out elsewhere in the thread - there are fundamental constraints that have kept Google, Apple, and others from pursuing this route. Relatively simple docs are one thing, but OOXML is full of dragons and parity with Word has eluded more than a few tech giants.
I'm yet to dig the code on how pagination is implemented but if the page breaks mimick word's - this is huge!
Every other JS DOCX editor I found was either abandoned or commercial. I couldn't find a solid MIT-licensed option.
There’s stuff like diagrams.net, but that’s not compatible.