Craft Apps GuideHow Was ArtCraft Built?
The short answer
Brandon Thomas identifies himself publicly as an ArtCraft founder. The public project contains two related kinds of software: ArtCraft AI Studio, which provides AI image and video creation, and a family of Crafting Apps for tasks such as image editing, presentations and CAD drawing. Their public repositories document code, contributors, releases and rules for AI coding agents. Those records show how the projects are organized; they do not establish that every line of code was written by AI or that one person built every app alone. Brandon Thomas's profile ↗ · ArtCraft repository ↗ · ArtCraft's agent instructions ↗
Which ArtCraft are we talking about?
The name covers related products with different jobs. ArtCraft AI Studio ↗ is the image and video creation app. Its repository describes a Tauri desktop application with Rust and TypeScript. The Crafting Apps directory ↗ introduces separate tools such as PhotoCraft, DeckCraft, FigCraft and CADCraft; each has its own product scope and repository. A claim about the Studio's frontend should not automatically be applied to every Crafting App. Likewise, a feature listed for one Crafting App does not prove it exists in all the others.
The repositories are public, and the apps can have releases at different stages. To decide whether a specific app fits your work, open that app's release notes and test the file or task you need. “Open source” tells you that code is available to inspect; it does not by itself guarantee every workflow or imported file will work.
A short timeline from public records
These entries are examples of dated public evidence, not a complete history of ArtCraft's founding.
| Date | Public record | What it establishes |
|---|---|---|
| 2026-10-07 | The CADCraft roadmap ↗ records the project's account of its first development session. | CADCraft's maintainers reported an early build milestone. The account does not independently measure work across the whole ArtCraft family. |
| 2026-10-08 | The same roadmap lists early CADCraft releases. | CADCraft began publishing builds; this does not mark the launch date of every Crafting App. |
| 2026-10-17 | CADCraft v0.8.0 ↗ was published with downloadable assets and change notes. | A specific version and its public release can be checked. |
Brandon Thomas's public GitHub profile ↗ states his founder role but does not date the beginning of every project. We have not turned that undated statement into an invented founding date.
How do the public repositories describe development?
The ArtCraft repository ↗ exposes source code, issues, pull requests and releases. Its AGENTS.md ↗ gives coding agents instructions about the monorepo and identifies the desktop app's Rust and TypeScript structure. A Crafting App example, DeckCraft's AGENTS.md ↗, describes a separate pure-Rust application and shared project standards. The existence of these files means the maintainers have written rules for agents and contributors. It does not show which instructions were followed in a particular commit.
For a concrete change, the useful trail is a linked issue or pull request, the reviewed code, any automated checks and the release that includes it. A merged change still needs a user-level check for its actual outcome. CADCraft, for example, has a public release history ↗ and a roadmap at v0.8.0 ↗ that discusses features and known gaps. Read the release matching the version you installed, because the main branch can move ahead of a published build.
People, agents and contributions
Brandon Thomas ↗ calls himself an ArtCraft founder. Public repositories also show other people contributing through commits and pull requests. An agent instruction file describes a way of working; it is not a reliable count of AI-authored code, agent sessions, costs or hours. Git attribution can show the account associated with a change but may not reveal every tool used to produce it. No public source reviewed here supports a percentage for “how much of ArtCraft AI built.”
For Brandon's public background and his relationship to the project, read Who Is Brandon Thomas?. This page focuses on the development evidence rather than repeating his biography.
What the evidence can and cannot tell you
| Public evidence | Supported conclusion | Limit |
|---|---|---|
| A repository AGENTS.md | The project publishes instructions for coding agents. | It does not prove that an agent wrote every change. |
| A release and its notes | A named build and stated changes were published. | It does not prove your own file or workflow works in that build. |
| A pull request and checks | A specific change and its recorded checks can be inspected. | Passing checks do not establish full compatibility with every external file. |
| An author profile | The person has made a public statement about their role. | It is a self-description, not a complete independent biography. |
What this means if you want to use an app
Choose the app for the task, then check its current release, the relevant feature notes and one representative file of your own. For CAD drawing, start with CADCraft's manual first drawing or the CADCraft guide. For installation, use Get ArtCraft Apps and the Launcher guide. If you need to assess download safety, read Is ArtCraft Safe?.
This approach gives you something more useful than a claim that a product was “built by AI”: you can identify who publishes it, inspect the code and release, and verify the exact result you need.