R082 · AI-built software and its verification › Test oracles for agent-written code

Craft Anything: rebuild software, graded against the original

Read the original

test-oraclesreverse-engineeringai-built-softwareagent-protocolsagent-governancesandboxing

Source: Mayank A.'s LinkedIn post (2026-11-13) on storytold/craft-anything, from the team behind the PhotoCraft photo editor. Rust, MIT or Apache-2.0, early alpha (v0.6.1, 2026-11-12).

TL;DR

Craft Anything is a desktop app, CLI and MCP server that wraps a pure-Rust reverse-engineering engine (320 tools) around a coding agent. You give it a target (a website, app, game or file) and a request such as "recreate this site in Svelte". It runs a four-stage loop: Study the original, have the agent Build a new project, Check the build against the original and list mismatches, and refine until Ready. The interesting idea for agent engineering is not the cloning. It is that the original software is the test oracle, and that every inspection result is an evidence record with a confidence, a coverage figure and stated limits. Like R080 (AWS Emulator), the spec is a running system, and the acceptance test is how closely the build matches it.

The repo was about two weeks old at 33K stars as of 2026-11-15. The post's numbers check out: PhotoCraft has about 79K stars and Craft Anything crossed 31K.

How it works

One engine, three surfaces. All 320 tools are exposed as CLI commands and as MCP tools (craft-anything-cli mcp). Humans drive the same engine through an egui desktop app with a Simple view (four steps, approval cards, a similarity score) and an Advanced workbench (functions, strings, pseudo-C, disassembly, hex, call graphs, an evidence ledger and an "unknowns" panel). About 300 tools live in the engine and the rest in the AI and setup layers. The engine covers native binaries, .NET, Java, Android, Apple, Electron/JS, websites, firmware, packet captures, databases and game files, with its own decoders, disassembler and decompiler. Ghidra is optional. Inspection needs no LLM.

The loop.

  1. Study. Capture the target: pages at every width, code, files, runtime behavior.

  2. Build. A coding agent writes a new project in the requested stack, or a default.

  3. Check. Compare against the original. Websites are checked at three screen widths, games with the game's own self-test, and apps by running them. Output is a list of what doesn't match yet and a similarity score.

  4. Ready. Open or preview the result, or ask for changes and loop again.

The CLI form is rebuild <url|-> <request>, with --rounds to cap iterations and --existing to edit a prior build.

Two capability modes.

The README is explicit that clean room is a policy about which tools are offered, not an OS sandbox. The coding agent still runs as the user with its own permissions, and a doc lists which Claude Code tools it can refuse.

Agents. Claude Code is the first-class builder: it runs the user's own claude binary under the user's own sign-in, and Craft Anything never touches the account. Codex has an adapter that hasn't been verified live. Copilot CLI, Grok Build and other agents (Gemini CLI, Qwen Code, opencode, goose and more) plug in through ACP, and only some have been run live. Analysis can use Anthropic, OpenAI, OpenRouter, xAI or local OpenAI-compatible models.

Durable project state. Each project is a folder: craft.json (request, target, status, history), capture/ (what was recorded), app/ (the build), checks/ (each comparison), investigation.cany/ (evidence) and inbox/ (open questions for the user). Large results come back as a summary first and are paged on demand.

What's transferable

Tradeoffs and failure modes

Review checklist (if you adopt the pattern)

Sources

Connections

See R082 on the knowledge map

Part of the Research notes on nowucca.com. Figures and claims are the source's own unless the summary says otherwise.