Craft Anything · study · build · check
Troubleshoot Craft Anything
Most Craft Anything failures are a mismatched file, a first-launch permission prompt, or doctor reporting that the coding agent is not signed in. Update to the current release before debugging an old bug.
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.
The direct download does nothing useful
This site does not store installers. Buttons depend on GitHub. If the API is down or the asset name changed, open the latest release and choose Assets. Confirm the filename contains windows-x64, linux-x86_64, or macos-universal before you run it. SHA256SUMS.txt on that release is the checksum list.
The program will not start
On Windows, an arm64 or x86 MSI on an x64 PC will not run; download the x64 file. A black window on older Windows builds was fixed upstream — install the current release instead of hunting display drivers first. On Linux, an AppImage that says permission denied needs chmod +x. On macOS, open the disk image’s app; if you downloaded the CLI zip in a browser and macOS says it cannot verify the program, use the curl steps on the macOS page or allow that binary under Privacy & Security. Do not download a second copy from an unrelated site to “get around” the warning.
Doctor or the build stops immediately
Building requires a coding agent that is actually signed in. Claude Code is the supported path. An agent installed with npm on Windows can fail the PATH check on old Craft Anything builds; update the app. A local server on the model port is offered as an AI only when it answers with a model list — another program on that port is not an agent. If you compiled from source, Rust older than 1.97 will not build the workspace, and a Debian or Ubuntu desktop build will fail until the README’s GUI libraries are installed.
A project looks stuck
The app is supposed to show what a build is doing and how long it has been quiet. Use the in-app retry, which continues from where the build stopped, rather than deleting the project. Cost figures from an agent are estimates. If the failure is a crash, the current releases name the program by its error; paste that text into a GitHub issue without attaching private project files you do not want public.
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.
Platform-specific first checks
Windows: confirm the MSI architecture, then update if the window is black. Linux: chmod +x the AppImage, confirm x86_64 versus aarch64, and avoid noexec mounts. macOS: open the notarized .app from the universal disk image; treat a blocked CLI zip as a quarantine issue, not a missing install. Steam Deck: Desktop Mode only, same Linux AppImage. Craft Anything will not start from the wrong OS file no matter how you rename it. If GitHub is unreachable, wait or use another network; this site has no backup binary.
What to send when you file a bug
Include the release tag, the filename you downloaded, doctor output, and the exact error string. Do not attach accounts, API keys, or a copy of a target you are not allowed to share. App bugs go to storytold/craft-anything issues or Discord. Wrong links on this guide go to support@craftanything.online. If Clean room refused a tool, that is expected; read the Clean room versus Deep page instead of treating the refusal as a crash. If two tags behave differently, say both version numbers. Alpha software changes quickly, so an old forum post may describe a bug that the current desktop build already fixed. Check SHA256SUMS.txt before you assume a “corrupt” file needs a different mirror; this site has no mirror. If doctor is clean and Build still exits at once, the agent is usually not signed in, not a broken MSI. Retry from the project folder instead of creating a second project with the same target.
FAQ
- Which architecture file did I download?
- Read the filename. x64 and x86_64 are the default PC builds. arm64 and aarch64 are ARM. macos-universal is both Mac CPUs. x86 without 64 is 32-bit Windows.
- Can you send a patched build by email?
- No. Installers come only from GitHub Releases. Email to this site is for the guide.
- Clean room refuses a tool I expected in Craft Anything.
- That is the default. The refusal tells you how to turn on Deep mode. Do that only when you are allowed to inspect the target that way.
- The home page button downloaded nothing.
- Open the GitHub latest release and pick Assets yourself. This site does not store the installer.