From Tuesday Brief · Tuesday, October 13, 2026 · 5 min read
Free Adobe and Microsoft products, with AI writing most of the code
ArtCraft is giving away thirteen open source replacements for Adobe and Microsoft Office apps. The commit log shows Claude Opus 5.5 co-authored four out of five commits on some of them. Installers are live, nothing is finished, and the method is the real story.
Somebody rebuilt Photoshop, Word, Excel, PowerPoint and InDesign, gave them away for free, and let an AI write most of the code.
The project is called ArtCraft, and the developer behind it is Brandon Thomas. It is real, the code is public, and I went and counted it myself rather than trust the coverage. Then the part that matters: none of it is finished, and the way it was built is more useful to you right now than the software is.
What actually exists
ArtCraft lists thirteen apps. The ones a publication would care about:
- PhotoCraft for Photoshop, LightCraft for Lightroom
- DesignCraft for InDesign, PdfCraft for Acrobat
- VectorCraft for Illustrator
- FilmCraft for Premiere, EffectCraft for After Effects
- WordCraft, GridCraft and DeckCraft for Word, Excel and PowerPoint
All free. All open source under the MIT or Apache 2.0 license, which matters more than the price does: you may use them commercially, and nobody can take them back or start charging you for the copy you already have.
Installers for Windows, Mac and Linux sit on GitHub, posted the day before I wrote this. People are taking them. PhotoCraft's Windows installer had just under 34,000 downloads, WordCraft's just over 30,000, and PhotoCraft has collected more than 55,000 stars from other developers. For scale, that is more attention in a week than most open source projects get in a decade.
How it was made
This is the part worth your twenty minutes.
The commit log is public. In WordCraft, 343 of 427 commits name Claude Opus 5.5 as a co-author. In DeckCraft it is 116 of 140. I counted both by hand, start to finish, because the figures going around came from somebody else's estimate.
Every one of those code repositories also carries two plain text files at the top: CLAUDE.md and AGENTS.md. Those are instruction files written for an AI rather than for a person. Which means you can read over the developer's shoulder and see exactly what he contributed.
He did not describe features. He wrote rules, then let the machine work inside them. Three of those rules explain the entire project.
Never crash. The file says it plainly: people trust a word processor with their writing, and a crash loses their work, so this outranks feature work. Then it gets specific. It bans the exact programming shortcuts that cause crashes, and requires a test with every crash fix so the same one cannot come back.
Clean room. Microsoft Word is installed on the build machine, and the AI is allowed to run it, watch how it behaves, and screenshot its window. It is flatly forbidden from reading, disassembling or copying anything inside the installed program.
That third rule is the answer to the question everybody asks first, which is how any of this is legal. Rebuilding a program by watching what it does, instead of copying how it does it, is called clean room work, and it has a long history in software. The file formats come from published standards rather than from anybody's source code: .docx, .xlsx and .pptx are an open specification that anyone can read, and PhotoCraft's Photoshop file support was written from the specification Adobe publishes itself. The rules go further and forbid copying code from the free competitors too, because that code carries license terms the project did not want.
There is one more rule I would steal outright. Progress is measured by a script, not by anybody's opinion. The project keeps a list of every Word ribbon feature, checks off the ones that work, and enforces a floor that can only go up. The AI cannot talk its way into saying it finished something.
So the lesson is not that AI can write a word processor. The lesson is that the human wrote the rulebook, the hard limits and the scoreboard, and the machine did the typing. If you have read anything I have written about automating our own weekly video, that will sound familiar. The value was never in the typing.
Why it is not ready
The project says so itself, which I respect more than I would a launch video.
WordCraft calls itself alpha. By its own measurement it covers 88 percent of Word's ribbon commands, but the authors estimate it is only about 60 percent of the way to replacing Word for real work, and about 55 percent of the way for a typical professional's week. DesignCraft, the InDesign one most of us would want, is still pre-alpha. PhotoCraft is furthest along: opening and re-saving a layered Photoshop file renders the same for 307 of the 309 files in a standard test set.
One specific trap before you open a real file. Proprietary fonts are never included, by rule. A Word document set in Calibri or Aptos opens in a substitute face with matching measurements. On a letter nobody notices. On anything where line breaks and page counts matter, you will.
So do not cancel anything. Work on copies, not originals. Treat this as free software you are evaluating, not a migration you are starting.
What I would do this week
Download PhotoCraft or PdfCraft and hand it the jobs you resent paying a subscription for. A quick crop. A PDF that needs two pages pulled out. A sponsor logo that needs its background knocked out. If it does those four times out of five, you have found a real use for it today at zero cost and zero risk.
Then look at the thing almost nobody is covering. Every one of these apps was built so that each button is also a command an AI can call. WordCraft exposes 422 of them, PhotoCraft more than 500, through what is called an MCP server, which is the standard way to let an assistant like Claude operate an outside program. An agent could lay out a templated page, or process a hundred photos to the same spec, by driving the app the way a person would.
That is a long way from helping you Tuesday. But a page layout program an assistant can operate is a different thing than a cheaper InDesign, and it is the reason to keep an eye on this even while it is too young to trust.
And if you take one idea from how it was made, take this one. Next time you ask AI to build you anything, make it write the rules before it writes the work.
Before you write any code for this project, write me a rules file. Plain language, no jargon. It should say what you must never do, what counts as finished, and how we will measure whether you are making progress. Ask me whatever questions you need to write it well. Then show me the rules and wait for me to approve them before you build anything.
Source: https://getartcraft.com/apps
Try this and tell me what happened.
Did it work? Hit reply. Did it come back sounding like a stranger? Hit reply harder. That’s the interesting failure, and it’s almost always fixable.
Get the next one in your inbox
Tuesday brief + Friday deep-dive. Free. Unsubscribe anytime.
Subscribe — free, twice weekly