This piece covers one path: install it, finish a first rebuild, understand what it hands back. Prompt craft is the next one.

Step one: pick an install route

Two routes. Prebuilt packages, or build from source.

Prebuilt is easier and needs no Rust. Windows has an MSI and a portable zip across x64, arm64 and x86, code-signed. macOS gets a universal DMG covering Apple Silicon and Intel, signed and notarised. Linux has AppImage, Flatpak, deb, rpm and tar.gz for x86_64 and aarch64, with a riscv64 tarball as well. FreeBSD has a tarball. Download from GitHub Releases; the standalone package list on the site sometimes lags behind.

Building from source has one hard requirement: Rust 1.97 or newer, because the workspace uses edition 2024 and recent dependencies. On Debian and Ubuntu the desktop app additionally needs system libraries: libxkbcommon-dev, libwayland-dev, libx11-dev, libxrandr-dev, libxi-dev, libgl1-mesa-dev, libgtk-3-dev.

After cloning, two commands cover both surfaces:

cargo run --release -p craft-anything

cargo install --path apps/craft-anything-cli

If you only want the CLI, skip the first; the GUI is not required.

Step two: run the doctor

Do not create a project yet. Run:

craft-anything-cli doctor

It checks three things: whether the install is complete, whether a usable coding agent is present, and whether engine dependencies are satisfied. Output names whatever is missing.

Worth a look while you are here: craft-anything-cli commands lists every probe. Each one is a CLI subcommand, an MCP tool and a component of the desktop app, all backed by the same engine. To feed those tools to any MCP client, run craft-anything-cli mcp.

Step three: connect a builder

A working install is not a working builder. craft-anything ships no model; the Build step calls an agent you have already signed into.

Claude Code is first-class and the most tested path. One command wires it up:

craft-anything-cli setup --client claude_code --yes

Then ai list shows the builders recognised on this machine, ai test checks connectivity, ai add registers a new one. With Claude Code it runs your own unmodified claude binary under your own sign-in.

Other options include OpenCode, Copilot CLI and Grok Build, plus anything speaking ACP. A CLI that is not on the built-in list falls through to a Plain adapter with one rule: pass the arguments plus the prompt as the final parameter and read the output as text. Use absolute paths in the command, because an app launched from the desktop inherits the minimal PATH from launchd.

Step four: create the first project

In the GUI, the Make screen asks for a target type, an address, clean room or deep, and one sentence such as rebuild this website. Press start.

The CLI equivalent:

craft-anything-cli rebuild https://example.com "Recreate this website"

Projects land in Documents/Craft Anything, one folder each, with a fixed layout. craft.json holds the request, target, status and history. capture holds evidence recorded from the original. app holds the generated project. checks holds every comparison round. inbox holds questions waiting for you. investigation.cany is the evidence store. You can also start in a folder you pick; if it already has files, you are asked whether it is an app to edit in place or material to start from.

Step five: read the result

After the four steps the project page gives you two things: a similarity score per page, and an itemised list of what still differs. The input box at the bottom takes the next instruction in plain language.

One trap on non-English interfaces

A build from source can render Chinese, Japanese or Korean text as empty boxes. The reason is mundane: CJK fonts are not pulled from the system at runtime but injected at build time from a separate font repository, which official release builds include. Either follow the docs and rebuild with the font directory, or switch the interface to English:

craft-anything-cli settings-set language en

One last thing

Do not practise on a commercial product. Pick a small site you own or are explicitly allowed to examine, run all four steps once, and you will judge the tool better than after reading ten reviews.