Today's AI open source · 2026-11-21
erkamyaman/rust-anything
rust-anything is an open-source tool that continuously verifies that an app behaves the same as the original while a coding agent ports it to Rust.
| Repository | github.com/erkamyaman/rust-anything ↗ |
|---|---|
| Main language | Rust |
| License | MIT |
| GitHub stars · forks | ★ 6,594 · 518 forks (as of 2026-11-21) |
| Created · last update | 2026-11-16 · 2026-11-20 |
| GitHub topics | agent-skills, claude-code, cli, code-migration, codex, ffi, golang, java |
Overview
rust-anything is a tool that helps rewrite CLIs, HTTP servers and libraries written in TypeScript, Python, C, Go, Ruby and Java into Rust, little by little. The README explains that the tool does not translate code; instead, it proves that the rewritten code behaves exactly like the original.
The work is split into four stages. record runs the original with generated edge cases and user inputs and records return values and exceptions. bridge creates a Rust crate and wrappers so that callers can keep using the existing API as is. When a developer or coding agent writes the Rust code, diff reruns all recorded cases and compares them, and the work moves to the next step only if everything matches and passes the gate.
It is also available as a Claude Code plugin and an MCP server, which makes it a good fit for teams that want to hand migrations to a coding agent. It also suits developers who want to move existing services or libraries to Rust for performance but worry that behavior might change.
Why it is worth a look
When a coding agent ports code to another language, the hardest part is confirming that the result behaves exactly like the original. rust-anything builds verification into the workflow by first recording the original's actual behavior and then replaying and comparing it for each unit. It is worth looking at as an example of harness design that makes agent-written code trustworthy.
Key features
- The record command runs the original with generated edge cases, inputs likely to be semantic pitfalls, and user inputs, and records return values and exceptions.
- The bridge command creates a Rust crate and wrappers so that callers keep the original API unchanged.
- The diff command reruns all recorded cases against the Rust implementation and compares the results; the work moves on only if everything matches and passes the gate.
- It is provided as a Claude Code plugin and an MCP server, so coding agents can carry out the migration steps directly.
- PHP and C# currently support recording and replay only, and the README announces unit porting as the next step.
What it is used for
- Use it to move a CLI tool built with Node.js or Python to Rust while keeping its behavior unchanged.
- Use it to replace an existing library with Rust unit by unit without modifying existing calling code.
- Use it to hand language migration work to a coding agent while verifying the results automatically.
- Use it to move an HTTP server to Rust step by step while checking for regressions at each stage.
Getting started
- Following the Quick start in the repository README, install the rust-anything package published on crates.io or npm, or add it as a Claude Code plugin.
- Run record on the app to be ported to capture the original behavior.
- Use bridge to create the Rust crate and wrappers, then write the Rust code yourself or with a coding agent.
- Use diff and gate to confirm that all recorded cases match, then move on to the next unit.
What to weigh
- It is under the MIT license, so commercial use has few restrictions, but the copyright notice must be kept.
- It is a new project created in November 2026, so commands and settings may change often.
- The figure of 19x faster in the Prettier port is the repository's own claim according to the README, and actual results may vary depending on the target code.
- PHP and C# currently support only the recording and replay stage, so if you need unit porting, first check that your language is supported.
Related terms and companies
Sources
Written with AI assistance from the repository README and GitHub data. Star counts and other numbers are GitHub values as of the date shown; features and licensing can change, so check the repository.