跪拜 Guibai
← All articles
Backend · Programmer · AI

Craft Anything: A Pure-Rust Reverse Engineering Suite That Rebuilds Software from Observation

By cxuanAI ·
Read original on juejin.cn ↗ Google Translate ↗ Alt translation

This gives Western engineers a legally safer way to re-implement proprietary UIs and behaviors without touching source code, while still offering deep analysis for code they own. It also moves reverse engineering from a manual, days-long process to an automated one that a coding agent can drive, for better or worse.

Summary

Craft Anything turns software reverse engineering into an automated pipeline. Instead of manually digging through Ghidra or IDA Pro, you feed a target URL or binary to the tool, set your preferred tech stack, and it runs through four steps: Study (observation), Build (construction), Check (validation), and Refine (iteration). The engine has already passed 35K GitHub stars and is written entirely in Rust, which keeps memory use low and makes cross-platform execution smooth.

Two operating modes separate the legal from the risky. Clean-Room mode, on by default, only looks at externally visible information like screenshots, DOM structure, colors, fonts, and visible interaction flows, and blocks all tools that could read the original source code. Deep mode, which must be manually enabled, unlocks file-level analysis, executable parsing for ELF, Mach-O, and PE formats, and can connect to local decompilers such as Ghidra for authorized legacy or private code.

The tool comes as a desktop GUI, a CLI (craft-anything-cli), and an MCP server, so it plugs into Claude Code or other coding agents. It bundles 320+ tools that each act as both a standalone CLI command and a standard MCP tool. Its creator, ArtCraft (storytold), is also building a full Rust-based creative suite—PhotoCraft, FilmCraft, CADCraft, and more—making Craft Anything the meta-tool that lets anyone re-implement any software they can observe.

Takeaways
— The engine is written entirely in Rust, requiring Rust 1.97 or higher, and supports macOS, Windows, Linux, and FreeBSD.
— It reached 35K GitHub stars shortly after being open-sourced; the current release at the time of writing is v0.6.1.
— A four-step pipeline is used: Study (observation), Build (construction), Check (validation), and Ready/Refine (iteration).
— More than 320 built-in analysis tools cover DOM structures, Electron apps, Apple apps, Android, .NET, Java, databases, firmware, and game assets.
— Clean-Room mode, enabled by default, restricts observation to externally visible data (screenshots, DOM, layout, colors, fonts, visible text, interaction flows) and blocks source-code access.
— Deep mode, opt-in, enables ELF/Mach-O/PE parsing, symbol decoding, and integration with local decompilers like Ghidra, with process isolation using bwrap on Linux and Job Objects on Windows.
— The tool runs as a desktop GUI, a CLI (craft-anything-cli), or an MCP server, and can be driven by agents like Claude Code.
— The `craft-anything-cli doctor` command checks the Rust environment, decompiler extensions, and connected coding agent before use.
— Craft Anything is part of the ArtCraft (storytold) suite, which includes open-source replacements for Photoshop, Figma, Premiere, CAD, Word, Excel, and similar software.
Conclusions

Clean-Room mode directly answers the legal liability that REA drew criticism for: it proves the tool can replicate a site or app without ever reading its source, which fits clean-room reverse engineering practices used in IP litigation.

Shipping 320+ tools as both CLI and MCP means the tool is designed from day one to be driven by coding agents, not as a standalone analysis product.

A pure-Rust implementation gives it a performance and distribution advantage over Node-based reverse engineering tools, but the Rust 1.97+ requirement and first cargo build are a real onboarding cost.

The "rebuilt in minutes" claim compresses days of expert analysis into an automated flow, but the quality of the rebuild still depends on the underlying large model's reasoning, so complex apps will still need human verification.

Concepts & terms
Clean-Room Reverse Engineering
A legal strategy where a tool only observes externally visible behavior (screenshots, DOM, layouts) and never accesses the original source code or internal files, so the resulting reimplementation is not derived from protected code.
MCP (Model Context Protocol)
An open protocol that lets tools expose their capabilities to AI coding agents as standardized commands; here, each of the 320+ craft-anything tools can be called by agents like Claude Code over MCP.
Source: juejin.cn ↗ Google Translate ↗ Backup ↗