ArtCraft founder Brandon Thomas says AI coding agents built a working Photoshop approximation in about 24 hours, and argues open source can now rebuild Adobe, Microsoft Office and Figma. In his talk at CODE Summit 2026, posted by the AI Engineer channel, Thomas explains why the web turned from open protocols into rent-seeking platforms, how ArtCraft’s Rust apps went viral, why every app ships with MCP and CLI control, and what Autocraft, his forthcoming open source software factory, is meant to do.
TLDW
Thomas, a former Square infrastructure engineer, says the early web of IRC, open APIs and customizable pages was replaced by platforms that gatekeep distribution and extract fees, with Adobe’s cancellation charges as his example. ArtCraft began as an open source desktop tool for filmmakers, and when the team saw artists vibe coding their own workflows on top of it, they decided to rebuild the apps those artists depend on. Large structured prompts produced a usable Photoshop approximation in a day; the team says it is now past 60% feature parity, and has since done Premiere, InDesign, Office apps, a Figma clone with a collaboration server, CAD and audio tools. Thomas claims more than 300,000 GitHub stars, 4,000 contributors, 1.7 million downloads a day and a quarter of users on Linux. He credits Rust for native performance and portability, says CI is the real bottleneck, and argues agents can run unsupervised on apps and games while humans keep control of schemas and APIs.
Thoughts
The clone is the headline, but the real product is hiding in a story Thomas tells almost in passing. Before any of the Adobe work, ArtCraft noticed artists vibe coding their own workflows on top of its open source tools. He describes micro drama studios doing $30,000 to $50,000 of fulfillment a month with big teams, whose needs no vendor will ever build for, but who have people in house who can point Claude Code at an API and generate the exact interface they need. That is the argument for open source in the agent era, and it is stronger than “Adobe is expensive.” A closed app gives every user the same surface area. An open one with MCP and CLI control can be cut down to one artist’s job, five or ten times over for five or ten people on the same team. The Photoshop look-alike exists to meet artists’ muscle memory and to prove the method works. If ArtCraft is right, the interesting software of the next few years won’t be clones at all. It will be thousands of small, narrow tools that nobody would have funded, built by the people who use them.
The most practical rule in the talk comes in the last three minutes, delivered while Thomas is apologizing for running over. If the work involves schema migrations, API design or anything else other code depends on, keep humans in the review loop. If it is a desktop app, a game or something “basically immutable”, give agents full confidence and let them run. That is a reversibility test, and it is a better guide than “review everything” or “review nothing.” A bad button in a paint app costs one bug report. A bad schema migration costs every user’s data and every downstream integration. It also explains why his team says CI is falling over and they are renting their own servers: when agents write code that fast, the build and test pipeline is the only reviewer that scales. That lines up closely with what Satya Nadella said recently about cheap code making verification the hard part. Autocraft, the software factory Thomas promises to open source, is his attempt to automate the rest of that loop, from issue triage to evals.
Where the talk is weakest is parity. Thomas says the team went from 50% to just past 60% of Photoshop, and that “in the fullness of time like Pareto principle” they could reach 99.99%. Pareto points the other way. The first 60% of a mature app is the part that tutorials describe and that a model has absorbed from its training data: layers, masks, brushes, file import. The last 40% is the decades of edge cases, color management, performance on huge files and features like Content-Aware Fill, which press coverage notes PhotoCraft doesn’t have yet. That is exactly the work professionals pay for. None of this makes the project less impressive. A usable image editor in a day would have been absurd two years ago. But “approximation” is the honest word, and it is the one Thomas himself uses. There are also open questions he doesn’t address, from Adobe’s patents to how a volunteer community maintains 300 apps once the excitement fades.
The reason this went viral, with New York Times interest within days and anti-AI artists sending feature requests, is that the grievance is real. Thomas’s example is Adobe’s annual plan paid monthly, where cancelling early triggers a fee. Adobe’s own terms confirm it: after the first 14 days, cancelling costs 50% of the remaining contract. For a filmmaker who needs Premiere for one festival short a year, that is a punishing structure, and it has made people who distrust AI cheer for an AI-built alternative. Combine that with Linux users, who Thomas says make up a quarter of his audience and have never had professional creative tools, and languages like Arabic that InDesign didn’t support, and you get a community with plenty of reasons to contribute. The big platforms spent fifteen years treating their users as a captive market. AI coding agents have made it cheap to leave, and ArtCraft is the first loud proof.
Key Takeaways
- ArtCraft’s first Photoshop approximation took about 24 hours, built from large structured prompts covering the UI, every tool, data structures and file importers.
- The team says it is past 60% feature parity with Photoshop and is deliberately copying Adobe’s look and feel so artists keep their muscle memory.
- The project has expanded to Premiere, InDesign, Animate, Acrobat, core Microsoft Office apps, Figma with a multi-user server, CAD and digital audio workstations.
- Every app is MCP and CLI first, so agents can drive them and assemble creative projects on screen.
- ArtCraft started as an open source desktop tool for filmmakers, and its users began vibe coding their own workflows on top of it.
- Thomas claims more than 300,000 GitHub stars, about 4,000 contributors, 1.7 million downloads a day and 300 community apps in development.
- A quarter of users are on Linux, which has historically lacked professional creative and office apps.
- The community has localized apps into unsupported languages, such as Arabic for InDesign, and is maintaining Adobe Animate past its support lifecycle.
- Rust was essential: native performance, a low defect rate, every operating system including NetBSD, and the web through WebAssembly. Engineers don’t need to know Rust, because agents write it well.
- Compile times and CI are the biggest bottlenecks, and the team is running its own servers to keep up.
- Keep humans on schema migrations and API design, and let agents run unsupervised on desktop apps and games.
- Autocraft, a forthcoming open source software factory, will triage issues, do agentic development and use its own decisions as data for evals and post training.
Chapters
0:00 Open Sourcing the World
Thomas opens by apologizing for a talk thrown together the night before, after a sleepless month of VC calls and press since the project went viral. His goal is to open source the entire world. Open source powers much of modern technology but has never been at the front, Linux has been a second class citizen, and AI gives developers a chance to take the web back. He introduces himself: about 15 years as an engineer, eight at Square running payments and authentication infrastructure, seven doing startups, and a background in Atlanta’s film scene building laser projectors that played video games on skyscrapers.
2:30 The Open Web Before Closed Platforms
He takes the audience back to the 1990s and early 2000s: IRC servers you could own and automate, messaging apps that tolerated third-party clients, sites with data exports and APIs that let developers build mashups of Reddit, Flickr and Twitter, MP3s you actually owned, Flash animations, phpBB communities, Wikipedia and MySpace pages you could restyle with your own HTML and CSS. Web 2.0, broadband and smartphones brought everyone online, which he says was good, but it rounded off the technical edges. Protocols were replaced by platforms, APIs were withdrawn, and the experimental early web faded.
4:29 Subscriptions, Gatekeepers and Lost Ownership
Distribution became gatekept, especially on phones, which never allowed the free distribution the desktop did. Once companies won market share, they found pricing power, and streaming turned back into cable. Thomas’s personal example is Adobe’s annual plan paid monthly: cancel early and you pay a fee, which hurts someone who only needs Premiere for a weekend to finish one short film a year. He calls the result an extractive, rent-seeking web and borrows the word “enshittification” for it.
6:47 ArtCraft and Artists Coding Their Workflows
ArtCraft started as a professionally minded, fully open source desktop alternative to consumer AI video sites, built for filmmakers, with generated files living next to their editor. His advisors said artists don’t care about open source. Instead, the team watched artists vibe code their own workflows on top of it. Micro drama studios doing $30,000 to $50,000 of monthly fulfillment had needs no product would ever serve, but had staff who could use Claude Code against ArtCraft’s APIs. That raised the bigger question: what if every app those artists use, starting with Adobe’s, were open and could be trimmed to each person’s part of the workflow?
9:17 A Photoshop Approximation in 24 Hours
The team prompted a model that has already absorbed every Photoshop tutorial with a large plan: separate the UI from the engine, make everything MCP and CLI compatible, plan each tool, the data structures and the file importers. Within 24 hours they had a functional, familiar approximation that starts far faster than Photoshop. They have gone from 50% to just over 60% parity. For now they are matching Adobe’s interface on purpose, both for artists’ muscle memory and to prove something real was built agentically; new, more agentic interfaces will come later. They went on to do InDesign, Premiere and the rest of the suite.
11:10 Viral Growth and Artists Embracing AI
Thomas held off posting to Hacker News, but the project leaked on Reddit, and two days later The New York Times wanted an interview. Their Discord grew from 3,000 members to more than the Discords of several large AI media startups. Artists who had pushed back against AI turned around, started using the apps, filed bug reports and feature requests, and he hopes to teach them what MCP is and how to work agentically.
12:13 Beyond Adobe: Office, CAD, Collaboration and Linux
The team and community have built CAD, a Flash replacement, digital audio workstations, core Microsoft Office apps and a Google Docs alternative. He calls the PDF app the most polished and tells the room they’ll never need Acrobat again. The Figma clone includes an open source collaboration server. A community-led CAD project, Solid Craft, has its own open engineering kernel and an MCP that makes 3D printing projects quick. He claims more than 300,000 GitHub stars, 4,000 contributors and 1.7 million downloads a day, with a launcher for every operating system and a quarter of users on Linux. Apps are localized into languages Adobe and Microsoft never supported, Adobe Animate is being kept alive for animation studios, and 300 apps are in development, with shared 2D and 3D UI libraries so non-technical people can contribute.
16:11 Why Rust, Native GUIs and CI
Rust, he says, was probably essential. Earlier attempts used Electron, but serious creative apps need native code. He cites Google’s research on Rust’s low defect rate, its fast startup, support for every platform from tablets to NetBSD, and WebAssembly for the browser. You don’t need to know Rust, because agents drive it fine, though compile times hurt. Rich GUIs are possible in Rust now. The main gotchas are permissions, GitHub scaling and CI, which he says is falling over, so the team is running its own co-located servers.
17:35 Human Review and the Autocraft Software Factory
Humans should own backend work, schema migrations and API design. For desktop apps, games and anything effectively immutable, let agents run with full confidence; one community member has 40 machines rebuilding Unreal Engine in Rust. Autocraft, which ArtCraft plans to open source soon, is an autonomous software factory that ingests and triages issues, does agentic development, keeps engineers on task and records every decision as training data for evals and post training. He closes with a call to rebuild all software and platforms as open protocols, to own “our apps, our infra, our protocols, our models”, and says the company is hiring for fully open source work.
Notable Quotes
“We’re going to open source the entire world. Like why not?”
Brandon Thomas, on the goal of the project
“Suddenly your Netflix actually became cable once you started subscribing to all the streaming services.”
Brandon Thomas, on platform pricing power
“We actually observed artists vibe coding their own workflows on top of the software that we gave them.”
Brandon Thomas, on why ArtCraft went fully open
“Within 24 hours we were looking at a pretty good approximation of what Photoshop was.”
Brandon Thomas, on PhotoCraft
“A quarter of our users are on Linux, which is really fascinating.”
Brandon Thomas, on who is downloading the apps
“For like desktop apps and games and anything that’s basically immutable, throw your agents at it and give them like full confidence.”
Brandon Thomas, on agentic development versus human review
“Let’s own our apps, our infra, our protocols, our models, all of it.”
Brandon Thomas, closing the talk
Related Reading
- PhotoCraft on GitHub the source for ArtCraft’s Rust Photoshop alternative.
- Satya Nadella: When Code Gets Cheap, Verification Becomes the Hard Part the same verification problem Thomas hits with CI, seen from inside Microsoft.
- Software Factory Tutorial: Build an AI Agent Pipeline background on the kind of pipeline Autocraft promises.
- Eliminating Memory Safety Vulnerabilities at the Source Google’s research on Rust and defect rates that Thomas cites.
- The Cathedral and the Bazaar by Eric S. Raymond, the classic case for open, community-built software.