An AI video company shipped a free Premiere clone built with Claude. Its own roadmap says it's half ready

Late on Thursday 1 October, Brandon Thomas, the CEO of the AI image and video studio ArtCraft, left a comment on Hacker News that has since traveled a long way: "Software is over. But for real. I just one-shotted Photoshop. The whole thing." Within a week his company had put seven free, open-source desktop apps on GitHub that copy the look, panels and shortcuts of Adobe's suite, and one of them, FilmCraft, is a video editor built to feel like Premiere Pro.

Thomas says he built them in Rust with Anthropic's Claude Opus 5.5, which came out on 22 September, and the code backs him up. Of the last 100 commits to FilmCraft, 48 carry a Claude trailer, and the README says its own screenshots and grades were made "by an agent driving the running app." The apps are dual-licensed MIT or Apache 2.0, so anyone can use, change and redistribute the code, although the ArtCraft name and logos are excluded.

The coverage has run under headlines about Adobe getting "nuked." The story that matters to filmmakers is narrower and more useful: FilmCraft is a real, installable editor that shipped four releases in five days, its own makers rate it about half ready for real work, and the genuinely new part is not the Premiere skin but the fact that every button in it is a command an AI agent can press.

What shipped, and how fast

The storytold organization on GitHub created the PhotoCraft, FilmCraft, LightCraft, VectorCraft and PdfCraft repositories on Wednesday 30 September, EffectCraft and DesignCraft the next day, and five more (for documents, audio, slides, CAD and spreadsheets) on Wednesday 7 October. FilmCraft v0.1.0 landed on Friday 2 October and v0.2.1 on Tuesday 6 October, with installers for macOS, Windows and Linux, a command-line tool and a self-hosted web build. By Thursday morning FilmCraft had about 3,660 stars and 1,180 forks on GitHub, and PhotoCraft about 19,100 stars, according to the GitHub API. About 520 of FilmCraft's roughly 646 commits come from Thomas's own account.

The feature list reads like a Premiere manual. It has three-point editing, ripple, roll, slip and slide trims, J/K/L shuttle, a Lumetri-style color panel with scopes, keyframes with value and velocity graphs, EBU R128 loudness meters and caption formats from SRT to CEA-708. FilmCraft ships its own codecs written in Rust, among them H.264, HEVC, ProRes, DNxHR and AV1, and the README states there is "no FFmpeg inside." For moving projects in and out it reads and writes FCP7 XML, FCPXML, OpenTimelineIO, EDL, AAF and OMF.

The roadmap is more honest than the hype

The most useful document in the repo is ROADMAP.md, updated on Monday 5 October. It puts the feature checklist at about 87 percent and then adds a separate line: "Ready for real work: ~50-60%." Plugins score 0 to 10 percent, with the note that "for many professional editors this alone rules FilmCraft out." H.264 is the only delivery codec, AAF and OMF export have "never been validated in Avid Media Composer or Pro Tools," and Windows and Linux are "barely exercised at runtime" because development happens on macOS.

The roadmap also admits that several of its parity percentages were "written by the agents doing the work," and that UI fidelity "hasn't been checked independently." That caveat belongs beside every capability in this piece, because the feature list is the README's and not ours; we have not cut a project in FilmCraft. Early users are finding the edges already. One person on X reported that a 4K project used nearly 39 GB of memory on a 24 GB Mac, a single report we could not reproduce but one that fits the roadmap's own 35 to 40 percent score for performance.

Thomas has already moved his own deadline. On Reddit around 2 October he said the apps "should reach full parity within a month." On Hacker News three days later he put it differently: "99% parity will take a while, but I'm sure it'll be measured in months and not years."

• What an editor needs: Cut with Premiere muscle memory. FilmCraft today (its own docs): Panels, shortcuts and trim modes mirrored; Premiere, FCP and Avid key presets; Status: Works
• What an editor needs: Grade. FilmCraft today (its own docs): Lumetri-style panel, scopes, 32-bit float; Status: Works, CPU only
• What an editor needs: Deliver. FilmCraft today (its own docs): H.264 MP4 only; ProRes and DNxHR for mastering; no HEVC or AV1 export; Status: Partial
• What an editor needs: Hand off to sound or Avid. FilmCraft today (its own docs): AAF and OMF export, never validated in Media Composer or Pro Tools; Status: Untested
• What an editor needs: Move a project to Resolve or Premiere. FilmCraft today (its own docs): FCP7 XML, FCPXML and OTIO round trips; Status: Claimed, not tested by us
• What an editor needs: Plugins. FilmCraft today (its own docs): No VST3, Audio Units or OpenFX; Status: Missing
• What an editor needs: Heavy footage. FilmCraft today (its own docs): No camera RAW; color and export run on the CPU; Status: Weak
• What an editor needs: Platforms. FilmCraft today (its own docs): macOS first; Windows and Linux built but barely exercised; Status: Mac first
• What an editor needs: Agent control. FilmCraft today (its own docs): 650+ commands via CLI, JSON channel and MCP; Status: Works, the real novelty
• What an editor needs: Generative AI. FilmCraft today (its own docs): Speech-to-text off by default; no generation; Status: Missing

"Clean room" is his word

Thomas calls the apps clean-room replacements and "1:1 functional equivalents," and almost every outlet covering the story has repeated the label. In a classic clean room, the people who study the original never write the new code. FilmCraft's own instructions to its agents undercut that strict meaning: AGENTS.md keeps "Premiere reference screenshots and notes" in a local folder, the roadmap says agents "compare with Premiere reference screenshots" for UI fidelity, and the menu parity figure "comes from diffing a dump of Premiere 26.5's menus."

What the repo does support is narrower and still significant. It claims no Adobe code, icons, presets or LUTs, and its codecs are written from public specifications. Nothing we found shows that anyone decompiled Adobe software, despite a viral Bluesky post claiming someone had "decompiled the Adobe suite" and Eric S. Raymond's guess on X that the team had done the same.

The law here is better mapped than the hype suggests. In Lotus v Borland (1995) a US appeals court held that a menu command hierarchy is an uncopyrightable "method of operation," and in Google v Oracle (2021) the Supreme Court found that copying an interface so users could carry their skills over was fair use. Ars Technica flagged trade dress, the protected look of a product, as the live risk, and PetaPixel raised design patents. There is a contract question as well, since Adobe's General Terms bar users from reverse engineering its software. Adobe had not commented when PetaPixel asked, and we found no statement as of Thursday morning.

The business behind the free editor

ArtCraft makes its money elsewhere. Its pricing page sells credits for other companies' generators, including Seedance, Kling, Veo, Sora, Midjourney and Flux, starting at $10 a month for 1,000 credits, which buys about 63 seconds of Seedance 2.0 video. Thomas has said on Reddit that ArtCraft is "at $5M in revenue," a figure he has not backed with any filing.

Ars reported that development is funded by selling ArtCraft model access inside the apps. FilmCraft does not do that today. It has no generation features, its speech-to-text is off by default, and Thomas told Hacker News on 5 October that the apps "are not monetized in any way." Our read, and it is analysis rather than reporting, is that an editor an agent can drive is a natural storefront for generation later, so the follow-up worth watching is whether a credit menu ever appears inside FilmCraft.

What this means for AI creators

In practice, for anyone making work this week, FilmCraft is a free thing to test rather than a place to move client jobs. Cut a rough assembly, export H.264, then round-trip an FCPXML or OpenTimelineIO file into Resolve or Premiere and see what survives; if the interchange holds, trying it has cost you nothing.

The bigger opening is the agent layer. FilmCraft exposes more than 650 commands over a command line, a JSON channel and an MCP server, an open protocol that lets AI assistants operate software, so a model can cut, grade and export without anyone touching the mouse. For creators who already script their pipelines, that means rough cuts, caption passes and versioned exports for six platforms can be handed to an agent and checked by an editor, which is where the craft judgment should stay.

The limit is on the other side of the same coin. A free editor with agent control drops the price of the editing seat to zero, but it does nothing for taste, and any footage you trust to it today should live in a project format another editor can open.

What is still open

Three questions remain open as of Thursday 8 October. Adobe has not responded publicly, and nobody outside the project has published a full hands-on test of FilmCraft on real footage, us included. Thomas's month-to-parity promise from 2 October also comes due in early November, which is when we will read the roadmap again.

Timeline

• Date: Tue 22 Sep 2026. What happened: Anthropic releases Claude Opus 5.5; Source: Anthropic
• Date: Wed 30 Sep 2026. What happened: PhotoCraft, FilmCraft, LightCraft, VectorCraft and PdfCraft repos created; Source: GitHub API
• Date: Thu 1 Oct 2026. What happened: EffectCraft and DesignCraft created; Thomas on HN: "Software is over"; Source: GitHub API; Hacker News
• Date: Fri 2 Oct 2026. What happened: FilmCraft v0.1.0; Reddit post promises "full parity within a month"; Source: GitHub releases; r/vibecoding
• Date: Mon 5 Oct 2026. What happened: Roadmap says ~50-60% ready; Thomas: parity in "months and not years", apps "not monetized"; Source: ROADMAP.md; Hacker News
• Date: Tue 6 Oct 2026. What happened: FilmCraft v0.2.1; Eric S. Raymond: "Adobe just got nuked"; Source: GitHub releases; X
• Date: Wed 7 Oct 2026. What happened: Five more Craft repos; "decompiled" post spreads; Ars and PetaPixel stories; Source: GitHub API; Bluesky; Ars; PetaPixel
• Date: Thu 8 Oct 2026. What happened: No Adobe statement found; Source: Our check

Sources and what is unconfirmed: the FilmCraft README, ROADMAP.md and AGENTS.md, read in full; the GitHub API for repo dates, releases, commits and stars (pulled 8 October); getartcraft.com app and pricing pages; Thomas's Hacker News comments and the r/vibecoding thread; Ars Technica (Kyle Orland) and PetaPixel (Jeremy Gray), both 7 October; Adobe's General Terms; Lotus v Borland and Google v Oracle. We have not run FilmCraft ourselves, so every capability above is the project's own claim. The $5M revenue figure is self-reported, the parity percentages are agent-written, and "clean room" is Thomas's description. We did not contact ArtCraft or Adobe for this draft.

Links for QA (plain URLs, as the CMS strips hyperlinks):

• github.com/storytold/filmcraft
• getartcraft.com/apps/filmcraft
• getartcraft.com/pricing
• arstechnica.com/ai/2026/10/software-is-over-bold-ai-developer-takes-aim-at-adobe-with-open-source-clones/
• petapixel.com/2026/10/07/someone-rebuilt-free-open-source-versions-of-photoshop-premiere-and-lightroom-using-ai/

Your Voice

Quoted from public posts on X and credited by handle. If one of these is yours and you want it removed, message @the__generated on X and it comes down.

Got something to say? Tag @the__generated on X