Vibecoded in Rust, Aimed at Adobe: What ArtCraft Actually Is

Depending on which headline you read, ArtCraft is either an existential threat to Adobe or “the IDE for interactive AI image and video creation.” Both framings come from the same project, and the gap between them is the most interesting thing about it.

The repo at storytold/artcraft pitches itself in the second register: a desktop studio where artists compose shots deliberately — posing characters, blocking scenes in 3D, compositing cutouts and meshes — and then hand the result to a generative model to render. The tagline is “we turn prompting into crafting.” The press, meanwhile, ran with the first register. Futurism covered it as a reverse-engineered, open-source Adobe Creative Cloud; PetaPixel reported that the suite spans seven Adobe counterparts — PhotoCraft for Photoshop, FilmCraft for Premiere, LightCraft for Lightroom, plus Illustrator, Acrobat, After Effects, and InDesign analogues. The README itself eggs this on: “This is Adobe Photoshop for everyone, and we’re giving away the source code!”

The two stories aren’t contradictory so much as differently weighted. The Adobe framing is the hook that got Hacker News to 142 points and 209 comments; the crafting IDE is the actual thesis of the software. Which one you find more credible depends on whether you think the future of visual media looks like Photoshop with the subscription stripped out, or like something that never had a Photoshop-shaped ancestor at all.

The problem ArtCraft is actually solving

Strip away the Adobe-bait and the core argument is straightforward: text-to-image and image-to-video are terrible instruments for deliberate work. A prompt is a lottery ticket with adjectives. Artists — particularly artists trying to make anything longer than a single image — need to know what a shot will look like before generating it, and they need consistency and repeatability across shots.

This is not a niche complaint. A 2025 arXiv survey of generative AI in film creation, authored by a multi-institutional team spanning Harvard, MIT, NYU, USC, and Netflix, analyzed hundreds of films from three years of the MIT AI Film Hack and found exactly this disconnect: artists don’t understand why character consistency is technically hard, and researchers don’t understand what artists actually need from controllability. The survey’s list of artist pain points — consistency, fine-grained control, editing, motion refinement — reads like a requirements document for ArtCraft’s feature table.

The repo’s answer is to move control upstream of the model. Instead of describing a scene in prose and praying, you build the scene: place a virtual actor into a photographed location so multiple shots in the same room don’t hemorrhage continuity; convert reference images into 3D meshes so complicated objects can be positioned “exactingly and intentionally”; kit-bash a scene with 3D asset kits to lock camera angles and depth layering before calling action. The through-line is spatial determinism. The model renders; the artist decides.

The cleverest trick in the list is character identity transfer, which the README describes bluntly: “use mannequins as simple 3D ControlNets for posing any character.” That’s a compact statement of the whole philosophy. ControlNet — the technique of nudging diffusion models with structural inputs like sketches or poses, which The Collective Pitch’s survey identifies as the standard tool for posing characters and setting compositions — gets reified into a physical object in the scene. You pose a mannequin the way a director blocks an actor. The metaphor is film production, not prompt engineering.

There’s a certain dry honesty in the README’s own economics, too: every demo video on the page was generated for free with Grok Video, and the authors note the cost of building the README was negligible. A project about cheap, controllable media production that documents itself with cheap, controllable media production is at least internally consistent.

Built by a model, judged like software

Then there’s the origin story, which is where the controversy lives. PetaPixel reports that founder Brandon Thomas — a 15-year industry veteran, former CEO of Storyteller.ai, ex-Square engineer with roughly a decade of Rust experience — used Anthropic’s Opus 5.5 to recreate the apps in Rust, describing the result as a “clean-room reimplementation” that recreates functionality without touching copyrighted assets or protected code. His stated motivation includes Adobe charging him cancellation fees on multiple occasions, which is perhaps the most relatable origin story in modern software.

The “vibecoded” provenance drew exactly the skepticism you’d expect. The Hacker News thread — flagged, which tells its own story — contains a full spectrum of verdicts. One user who tested an early build called it “very broken” and questioned whether the framing was deceptive. Another who tried a later release found it “basically fine” except for popped-out panels, which suggests the iteration loop is fast. A third built and ran the Photoshop clone on a Mac and found it “mostly fine,” arguing the project demonstrates that large, working software can be built with AI.

The most substantive critique in the thread isn’t about stability at all. User dofm argued that Photoshop differs fundamentally from spec-shaped applications like Excel: it is a “surface” and a “medium,” with subjective feel, responsiveness, and brush dynamics — and noted that some users refuse to switch to Affinity Photo even though it’s free and highly capable, purely because it doesn’t feel right. High-end fashion retouching, the argument goes, demands responsiveness that a clone can’t inherit by imitation. Another commenter made the adjacent point: Office apps follow written specifications, which makes them clonable; Photoshop is a different animal.

Thomas, for his part, rejects the “casual vibe coder” label, citing six-nines payment rails processing billions of dollars daily. Whether a decade of Rust discipline plus an LLM constitutes craftsmanship or its simulation is a question the thread never resolves — but it’s the question the whole project forces.

No middleman, no subscription — bring your own models

The business model is the quiet radical part. ArtCraft’s site emphasizes no subscriptions, no aggregator middleman between users and models, and work that stays with the user. The provider table in the README makes the shape of this concrete: ArtCraft itself offers access to a long roster of models — Nano Banana and Nano Banana Pro, GPT-Image-1 and 1.5, the Seedance and Seedream families, Flux, Veo, Kling, Sora 2 and Pro, Hunyuan 3D — but the studio also connects directly to Grok, Midjourney, Sora, and WorldLabs’ Marble for Gaussian-splat world generation, with Kling, Google, Runway, and Luma direct connections on the roadmap.

In other words, ArtCraft wants to be the workbench, not the meter. That positions it against a whole ecosystem of middlemen. The Curious Refuge tool directory — an entire category economy of AI tool aggregators, video tools, consistency tools, and enhancement tools, backed by paid courses and a parent company in Promise.ai — exists largely to help creators navigate exactly the fragmentation ArtCraft is trying to absorb into a single canvas. And the Artlist blog notes that most creators currently stitch together combinations of AI tools, a workflow held together with export folders and hope. A studio that treats a dozen providers as interchangeable backends, with no markup, is a direct attack on that layer.

There’s a tension worth naming, though: Futurism quotes LightCraft’s promise of “no account, no cloud, no telemetry, no subscription” — a genuinely local-first editing claim — while the AI features by definition require cloud model calls through someone’s account. The local-app framing and the model-aggregator framing coexist awkwardly, and the sources don’t fully resolve how the project reconciles them.

The rough edges, honestly assessed

The project is in alpha, and it says so. Several advertised features — scene blocking, canvas editing, scene relighting, inpainting, “image ingredients” — are marked “preview coming soon” in the README, which is refreshingly candid and also a reminder that the feature table is partly a roadmap. Linux requires building from source, per the README, while macOS and Windows get stable releases from the website. PetaPixel notes Thomas hopes to reach “100% feature parity” with Adobe within a month, while carefully observing that feature parity doesn’t mean functionality or performance parity — a distinction professionals will feel immediately.

The legal question is the one nobody can wave away. PetaPixel points out that Adobe holds thousands of patents covering appearance and functionality, and that how legal precedent applies to a clean-room reimplementation remains an open question. A post about ArtCraft on r/Adobe was removed by moderators, which is a small data point about how nervously this is being received in incumbent-adjacent spaces. And Futurism’s bottom line is blunt: ArtCraft is four people in Atlanta (per their reporting) going after an $18 billion digital media business, and the hardest part of the climb is still ahead.

Why the timing matters

The backdrop is a field in genuine churn. The arXiv survey documents a research community and an artistic community that barely understand each other, with emerging trends — 3D generation, integration of real footage with generated elements — that happen to be precisely ArtCraft’s center of gravity. Working practitioners keep confirming the pain: Chris Salters’ year-long case study building a broadcast-style Fender commercial found image generation requiring tedious iteration to achieve framing, and image-to-video lacking crispness — the tiresome middle of the workflow ArtCraft is designed to compress. And the Raindance producer’s essay captures the industry mood: equal parts hope that AI funds unconventional films and dread of fully synthetic IP-mining, with ethics still unsettled.

ArtCraft’s bet is that the winning tool in this environment isn’t a better prompt box — it’s a place where the prompt is the last step. Whether a vibecoded Rust suite from a four-person team can deliver the responsiveness that retouchers and editors demand, survive Adobe’s patent portfolio, and finish its “coming soon” list is genuinely unknown. But the framing — control before generation, artists before models, source code on the table — is the correct argument, and it’s now being made in public, for free.