Where do I start with Craft Anything?

Download on the home page or the release page, follow the install page for your system, then open Setup.

Is there one installer for every CPU?

No. Match x64, ARM, or 32-bit. macOS is the exception: one universal disk image covers Apple silicon and Intel.

Can I keep two versions of Craft Anything?

Yes. Older tags stay on the GitHub releases list. Portable Windows zips and separate folders make that easier than overwriting an MSI install.

Does install include a coding agent?

No. The installer is only the app and, in current desktop builds, the CLI. You sign the agent in separately on this computer after the window opens. Rust is still not required for that path.

Craft Anything · study · build · check

Install Craft Anything

Install Craft Anything from the prebuilt GitHub release for your system. Compiling the Rust workspace is a developer path, not the install most people need.

Windows Linux macOS Steam Deck

Not affiliated with the ArtCraft team or the Craft Anything maintainers. We do not host installers. Downloads go to GitHub Releases. Use the software only on targets you are allowed to examine.

Which page to follow

Windows covers the x64 MSI and when to choose ARM64, 32-bit, or the portable zip. Linux covers the x86_64 AppImage plus deb, rpm, Flatpak, and the aarch64 builds. macOS covers the universal disk image and the separate command-line zip. Steam Deck does not have its own package: it uses the Linux x86_64 AppImage in desktop mode. FreeBSD tarballs and the browser zip are listed on the release page and are not given their own install guide here.

Windows, Linux, and macOS each have an install page
Steam Deck uses the Linux x86_64 AppImage
Source checkout is documented only as an alternative

Install versus setup

Install ends when the app or the craft-anything-cli command opens. Setup is the next list: run doctor, sign in a coding agent, leave Clean room on unless you have a reason to change it, and start a project. If a file will not launch, stay on the install page for that system or open Troubleshoot. If the app launches and then cannot build, go to Setup.

Building from source

The repository asks for Rust 1.97 or newer because a dependency requires it. Update with rustup, clone storytold/craft-anything, and run the desktop package with cargo. Debian and Ubuntu desktops also need the usual Wayland, X11, and GTK development libraries named in the project README before that cargo build can link. The command-line crate installs as craft-anything-cli. After either path, craft-anything-cli doctor reports the coding agents and engines it can see. None of that replaces the installer if you only want to run a release.

This site is not official. We do not host installers. Downloads go to GitHub Releases for storytold/craft-anything. Examine only software you own or are allowed to examine.

What “installed” means here

A successful Craft Anything install is a window you can open, or a craft-anything-cli command that prints a version. It is not a signed-in coding agent, not a finished rebuild, and not a pack of sample targets. People mix those steps because the product does several jobs. Keep this page for the file and the first launch. Keep Setup for doctor and the agent. Keep Clean room vs Deep for inspection policy. If you skip the matching CPU file, the rest of the product never starts, so architecture comes first even when you already know how you want to use the engine.

Choosing an installer format

Windows users who want a normal Add-or-Remove-Programs entry take the MSI. Windows users who want two versions side by side take the portable zip. Linux users who do not want a package manager take the AppImage. Linux users who already live in apt, dnf, or Flatpak take those files from the same tag. macOS users take the universal disk image unless they only want the command-line binary. Steam Deck users follow the Linux x86_64 AppImage in Desktop Mode. Craft Anything does not ship a store listing that this guide controls, so every format is still a GitHub asset. When you are unsure, use the default named on the home page and change format only after that copy runs.

After the first launch

Open Setup next. Run doctor if you have the CLI. Sign in Claude Code or another agent the status document lists as working if you plan to build. Leave Clean room on. Create a project in the default Documents folder unless you have a reason to pick another path. If the binary never opens, do not skip ahead to agent configuration; return to the system page or Troubleshoot. Updating later is the same GitHub release flow: a newer tag, the same filename pattern, checksums in SHA256SUMS.txt. Keep one tag’s desktop app and CLI together so doctor does not mix old and new binaries.

FAQ

Where do I start with Craft Anything?: Download on the home page or the release page, follow the install page for your system, then open Setup.
Is there one installer for every CPU?: No. Match x64, ARM, or 32-bit. macOS is the exception: one universal disk image covers Apple silicon and Intel.
Can I keep two versions of Craft Anything?: Yes. Older tags stay on the GitHub releases list. Portable Windows zips and separate folders make that easier than overwriting an MSI install.
Does install include a coding agent?: No. The installer is only the app and, in current desktop builds, the CLI. You sign the agent in separately on this computer after the window opens. Rust is still not required for that path.