cd /news/developer-tools/rust-anything-port-apps-to-rust-and-… · home › topics › developer-tools › article
[ARTICLE · art-172490] src=github.com ↗ pub= topic=developer-tools verified=true sentiment=↑ positive

Rust Anything – Port apps to Rust and check them against the original

Erkam Yaman released rust-anything 2.0, an MIT-licensed tool that records the behavior of Node.js, Python, C, Go, Ruby or Java apps and checks a Rust rewrite against that recording before each piece is lifted. The project reports a Prettier 3.6.2 port running 19x faster (6.9 s versus 128.6 s on 2,360 JS/TS files) with 17,224 recorded runs and 0 mismatches, and a json-server port using 3.5 MB at idle versus 74 MB, with 15,837 of 17,224 recorded runs formatting fully in Rust.

key takeaway

rust-anything 2.0 records the original app's outputs on edge cases and replays them against the Rust port, and its Prettier port matched all 17,224 recorded runs while running 19x faster (6.9 s vs 128.6 s on 2,360 JS/TS files).

read9 min views4 publishedNov 19, 2026
Rust Anything – Port apps to Rust and check them against the original
Image: Michielbdejong (auto-discovered)

Rewrite your app in Rust, and prove it still behaves the same.

New in 2.0: Prettier, ported to Rust. 19x faster · 17,224 recorded runs · 0 mismatches

Quick start · Languages · Real-world ports · How it works · Whole apps · FAQ

Made in Türkiye 🇹🇷 by erKam Yaman · MIT · ❤️ Sponsor me

Sponsored by CodeRabbit

<sub>English · Türkçe · Українська · 简体中文 · 繁體中文 · Deutsch · Français · Русский · 日本語 · 한국어 · Azərbaycanca · Oʻzbekcha · Қазақша · Кыргызча · Türkmençe · Татарча · ئۇيغۇرچە · Português · Tiếng Việt</sub>

| Recordrecord runs the original on generated edge cases, semantic traps and your own inputs, and saves what it returns or throws. | Portbridge generates the Rust crate and a wrapper, so callers keep the original API. You or your agent write the Rust. | Checkdiff replays every recorded case against the Rust, and nothing ships until they all match andgate passes. | Lift When replay passes with no fallback and every unit passes gate, app lift makes it a pure Rust app. The original is never touched. |

Rewrite your whole app in Rust, one piece at a time. rust-anything records what your Node.js (TypeScript/JavaScript), Python, C, Go, Ruby or Java app does today, then checks every piece of the Rust rewrite against that recording before it moves on, until the app is pure Rust. CLIs, HTTP servers and libraries; your coding agent (or you) writes the Rust. It can only catch what the recording covers: see What it can't catch. Whole tools and servers, or only the slow part, one hot path at a time:

Real project, same output as the original Original With rust-anything
Prettier 3.6.2, 2,360 JS/TS files from the command line 128.6 s 6.9 s: 19x faster
Prettier, 6,305 Markdown files from the command line 352 s 22.5 s: 15.6x faster
json-server , a whole Node server: memory at idle 74 MB 3.5 MB , one 5.3 MB binary
json-server, from start to first response 79 to 85 ms 8 to 10 ms
Fuse.js search over 50,000 strings, per query 91.2 ms 2.8 ms: 32x faster

Prettier: 15,837 of 17,224 recorded runs format fully in Rust across 10 languages (JavaScript, TypeScript, JSX, JSON, GraphQL, YAML, Markdown, CSS, SCSS, Less), and all 17,224 match Prettier byte for byte, since anything not ported yet falls back to Prettier. json-server: 514/514 recorded HTTP cases match on a pure Rust binary. Measured on an Apple M4, two runs each, every output compared before timing (details). Calling Rust once per small function is usually slower than a JIT; rust-anything finds the loop worth moving, and moves it.

<sub>Prettier against its Rust port on 59 real files from ms, Fuse.js and json-server (Apple M4). Same output, byte for byte. How it was measured.</sub>

<sub>json-server, a whole Node server, lifted to a pure Rust binary (Apple M4). How it was measured.</sub>

rust-anything is an independent project, not affiliated with or endorsed by the Rust Project or the Rust Foundation. "Rust" is a trademark of the Rust Foundation.

Warning

record and app record run your original code, calling each function (or the whole app) on many generated inputs, and app record runs every case twice. diff, gate and app replay run the same cases again, on the port or the original. Code that writes files, talks to a database or calls the network does that once per case. Run them on a copy of the project, with a test database and no production credentials in the environment.

Paste this into Claude Code, Codex, Cursor, Gemini CLI or OpenCode and let your agent install it:

Install rust-anything: run `cargo install rust-anything`, then `rust-anything setup`.
Tell me when to restart you.

Or yourself:

cargo install rust-anything   # from crates.io
rust-anything setup           # registers it with Claude Code, Codex, Cursor, Gemini CLI and OpenCode

No Rust toolchain yet? Prebuilt binaries for macOS, Linux and Windows are attached to each GitHub release, and for JavaScript projects npm install -g rust-anything installs the same binary.

In Claude Code you can also install it as a plugin (the MCP server and the skill; the CLI above must be on your PATH):

/plugin install rust-anything --marketplace erkamyaman/rust-anything

setup adds the MCP server to each agent it finds and installs the workflow skill where the agent reads skills. It keeps your other settings, is safe to run again, and --remove undoes it. Then ask your agent, for example:

  • "Rewrite this CLI in Rust with rust-anything, end to end, and prove it behaves the same."
  • "This search feels slow. Profile it with rust-anything and move the hot loop to Rust."
  • "Plan a migration of src/parser/ to Rust with rust-anything; port the first unit and prove it."
  • "Bench the Rust port in rust/text-rs against the original and tell me whether to ship it."
Agent rust-anything setup adds
Claude Code MCP server in ~/.claude.json , skill in~/.claude/skills/
Codex MCP server in ~/.codex/config.toml , skill in~/.codex/skills/
Cursor MCP server in ~/.cursor/mcp.json
Gemini CLI MCP server in ~/.gemini/settings.json
OpenCode MCP server in ~/.config/opencode/opencode.json (mcp.servers ), skill in~/.config/opencode/skills/
Any other MCP client add rust-anything mcp as a stdio server by hand (seeInstall )

Before changing a file that exists, setup saves a copy beside it (<file>.rust-anything.bak).

To wire OpenCode up by hand, put the server in ~/.config/opencode/opencode.json (command is the whole argv) and copy skills/rust-anything/ to ~/.config/opencode/skills/rust-anything/:

{
  "mcp": {
    "servers": {
      "rust-anything": { "type": "local", "command": ["rust-anything", "mcp"] }
    }
  }
}

Or run the steps yourself:

rust-anything profile . -- node bench.mjs              # what is hot, and who calls it
rust-anything bridge . src/fuzzy.ts --batch fuzzyScore:text
rust-anything record rust/fuzzy-rs && rust-anything build rust/fuzzy-rs
rust-anything diff rust/fuzzy-rs                       # every recorded case must match
rust-anything bench rust/fuzzy-rs                      # faster? the verdict says
rust-anything gate rust/fuzzy-rs                       # done means this passes

rust-anything does not translate code: your coding agent (Claude Code, Codex, Cursor, OpenCode, ...) or you write the Rust. rust-anything supplies what an agent cannot guess reliably: where the time goes, what to port first and in which order, a bridge so the rest of the code calls the Rust with its API unchanged, the exact behavior the port must match, a safe way to ship it, and a gate that says when a port is done.

Same output is not enough. Record what the app sends too, and a rewrite that mails twice fails:

<sub>A real run of app record --effects and app replay. See Side effects.</sub>

Language Unit Bridge Recorded and replayed by
TypeScript/JavaScript folder or file napi-rs or wasm-bindgen with a generated binary wire; classes and async included Node, running the .ts sources
Python package or module PyO3 (abi3), direct conversion, typed exceptions Python, importing the original
C .c file extern "C" functions with the original names and a header the original compiled to a shared library, called through ctypes, one fork per case
Go package typed cgo calls and a generated binary wire, in a package with the original API a generated Go driver, built as its own module
Ruby file or folder of module functions a magnus extension under the original modules a generated Ruby driver
Java package of public static methods typed JNI and a generated binary wire, in wrapper classes with the original methods a generated reflection driver
PHP folder of functions and public static methods coming next: PHP FFI over a C ABI whole apps today: app record ,app replay and the front door, for CLIs and servers (php -S )
C# folder of public static methods coming next: P/Invoke over a C ABI whole apps today: app record ,app replay and the front door, for CLIs and ASP.NET servers (dotnet <app>.dll )

Every language except C also gets batch classes (--batch): the items cross once and stay in Rust, and each call runs over all of them on all cores.

The language is detected from the repository (go.mod, pom.xml, a .csproj or .sln, pyproject.toml, Gemfile, composer.json, package.json, else the most common source files); --lang overrides it. Types come from the source: TS types, Python hints, C, Go, Java and C# signatures, Ruby YARD tags, PHP types and phpdoc; untyped parameters used as numbers are inferred as numbers.

For PHP, analyze plans a PHP app (Composer packages and PSR-4 auto, risks such as loose comparison and integer overflow into floats, Composer packages mapped to crates), and a PHP CLI or server can be recorded, replayed and put behind a Rust front door. Porting its units into Rust through PHP's FFI is the next step (issue #2).

C# works the same way: analyze reads .csproj projects and their NuGet packages (mapped to crates), resolves using directives to folders, and flags what C# does differently (decimal, dynamic, LINQ's deferred queries, Task, lock, reflection). A C# CLI or ASP.NET server can be recorded, replayed and put behind a Rust front door; porting units through P/Invoke comes next.

rust-anything is free and open source. If it helps your work, please consider sponsoring it.

Your support keeps development going.

Issues and pull requests are welcome; CONTRIBUTING.md covers the setup, where tests go, and how to add a language. Design choices and their reasons are in DECISIONS.md. Case studies of real ports are especially welcome. Please report security problems privately (SECURITY.md), and see the code of conduct.

MIT © Erkam Yaman. Ports and generated code in your repository are yours.

── more in #developer-tools 4 stories · sorted by recency
── more on @rust-anything 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
→ Live at https://your-agent.zahid.host ✓
Get free account → Pricing
from €0/mo · no card required
LIVE [news/rust-anything-port-a…] indexed:0 read:9min 2026-11-19 · —