Rewriting existing codebases into Rust with AI.
RoboCrab tracks projects pushing the limits of AI-assisted rewrites into Rust.
Join the community: RoboCrab Discord.
- AI-Assisted Rust Rewrites
- C2Rust And Automated Translation Case Studies
- Adjacent AI Rewrite Case Studies
- Adjacent Rust Reimplementations
- Tools
- Research
- Programs And Benchmarks
- Articles And Talks
- Adjacent Lists
- Bun Zig-to-Rust rewrite - Bun merged "Rewrite Bun in Rust" on May 14, 2026 from the
claude/phase-a-portbranch, adding a Rust workspace across thousands of files; Bun canary builds are released from everymaincommit viabun upgrade --canary. - Grit - GitButler's AI-authored Git reimplementation in Rust, targeting close behavior compatibility with upstream Git by porting and running the Git test suite against
grit-git. - Ladybird's Rust adoption - Browser project adopting Rust with AI assistance, starting with LibJS because it is relatively isolated and has extensive test coverage.
- pacquet - Official pnpm rewrite in Rust, porting the pnpm CLI from TypeScript to Rust while matching pnpm behavior, flags, defaults, error codes, file formats, and directory layout.
- pgrust - PostgreSQL rewrite in Rust using AI-assisted engineering, with PostgreSQL behavior and compatibility tests as the bar.
- tsz - AI-assisted Rust implementation of a TypeScript checker targeting drop-in
tsccompatibility, with conformance progress reported against the official TypeScript test suite.
These are mostly not AI-assisted, but they are useful prior art for automated translation, cleanup, safety work, and compatibility.
- libbzip2-rs - Drop-in compatible Rust implementation of bzip2 created with C2Rust and later used by the
bzip2crate. - libyaml-safer - Fully safe Rust fork of
unsafe-libyaml, originally translated from libyaml with C2Rust. - rav1d - Fully safe Rust port of the
dav1dAV1 decoder, created with C2Rust and then refactored toward safer, more idiomatic Rust. - rexpat - Rust port of Expat used as a C2Rust case study.
- sapp-kms - C2Rust-derived port of sokol's KMS backend, cleaned up but still unsafe.
- spiro.rlib - Fully safe C2Rust-derived port of the
spirospline interpolation library. - tsuki - Fully safe C2Rust-derived port of the Lua interpreter.
- unsafe-libyaml - Mostly direct C2Rust-derived port of libyaml, kept fully unsafe with minor cleanup.
- zlib-rs - Rust implementation of zlib exposed as both a C dynamic library and a Rust crate.
These are not all Rust migrations, but they are useful examples of AI-assisted rewrites, long-running agents, compatibility targets, and guardrails.
- Cloudflare vinext - AI-written reimplementation of the Next.js API surface on Vite and Cloudflare Workers, with Cloudflare describing the build process, token cost, test suite, and quality gates.
- Cursor FastRender browser experiment - Cursor research run where hundreds of agents worked for close to a week on a Rust browser engine experiment, producing over one million lines across 1,000 files.
- Cursor self-driving codebases - Follow-up post on the agent harness, coordination patterns, and review problems Cursor saw after the browser experiment.
- Webernetes - ngrok's LLM-assisted partial port of Kubernetes from Go to TypeScript for browser-based clusters, with manual review and tests comparing behavior against k3s.
These are not necessarily AI-assisted, but they show large ecosystems replacing existing developer tooling with Rust implementations.
- Astro 7 - Astro rewrote its
.astrocompiler in Rust, made its Rust-powered Markdown and MDX pipeline the default, and reports 15-61% faster builds across benchmark sites. - Biome - Rust web toolchain for formatting, linting, and code analysis, positioned as a faster alternative to common JavaScript tooling.
- Deno 2.0 - Rust-based JavaScript and TypeScript runtime with Node.js and npm compatibility, plus built-in formatter, linter, test runner, and task runner.
- Lightning CSS - Rust CSS parser, transformer, bundler, and minifier used by Parcel and other tools.
- Next.js Compiler - Rust/SWC-based compiler that replaces Babel for individual files and Terser for minification in Next.js.
- Oxc - Rust JavaScript tooling stack covering parser, linter, formatter, transformer, resolver, and minifier.
- Rolldown - Rust Rollup-compatible bundler used by Vite to replace its previous esbuild/Rollup split.
- Rspack - Rust Webpack-compatible bundler designed for progressive migration from Webpack.
- Ruff - Rust Python linter and formatter that replaces or consolidates tools such as Flake8, isort, and Black.
- Rustwright - Alpha Rust reimplementation of Playwright's browser-control engine under Playwright-shaped Python and Node APIs; reports 515 shared parity cases and 1,046 Docker-gate tests, plus local diagnostic speed and client-memory gains, while explicitly saying full behavioral parity is not yet proven.
- Tailwind CSS v4 - New high-performance Tailwind engine using Rust-powered pieces and Lightning CSS, with substantially faster full and incremental builds.
- Turbopack - Vercel's Rust-based successor to Webpack, introduced through Next.js.
- Turso - Rust rewrite of SQLite evolving into a pluggable database core; its new Postgres frontend compiles Postgres syntax and types to Turso bytecode, targets common-application compatibility rather than 100% PostgreSQL parity, and documents simulation, oracle, fuzz, and formal-method testing.
- uv - Rust Python package and project manager designed as a fast replacement for tools such as
pip,pip-tools,pipx,poetry, andvirtualenv.
- C2Rust - C-to-Rust translator and refactoring toolkit for migrating C code to Rust.
- Corrode - Older C-to-Rust translator, useful historical context for deterministic translation.
- ShiftCodex - AI code migration platform built around translate, test, fix, and re-run loops.
- VLTR - AI-powered C/C++ to Rust migration tool.
- C2RustXW - C-to-Rust translation that combines program analysis, LLM translation, dependency-aware ordering, and execution-based validation.
- EvoC2Rust - Skeleton-guided framework for project-level C-to-Rust translation.
- Rustine - Repository-level C-to-Rust translation system targeting compilable, idiomatic, safer Rust with test-verified functional equivalence.
- &inator - Correct and precise C-to-Rust interface translation.
- SafeTrans - LLM-assisted C-to-Rust transpilation with iterative repair.
- SACTOR - LLM-driven multi-step C-to-Rust translation using static analysis.
- RustMap - Project-scale C-to-Rust migration using program analysis, LLMs, dependency guidance, and test feedback.
- LLM4C2Rust - Retrieval-augmented C/C++ to Rust transpilation framework focused on memory safety.
- DARPA TRACTOR - Program aiming to automate translation of legacy C code to Rust using software analysis and machine learning.
- TRACTOR Benchmarks - MIT Lincoln Laboratory benchmarks and evaluation work for DARPA's C-to-Rust translation program.
- Porting C to Rust for a Fast and Safe AV1 Media Decoder - Prossimo write-up on the goals and approach behind
rav1d. - Making the rav1d Video Decoder 1% Faster - Performance case study on a C2Rust-derived port.
- Translating bzip2 with C2Rust - Trifecta Tech Foundation write-up on translating bzip2 with C2Rust.
- Rust Is Eating JavaScript - Lee Robinson's evolving survey of Rust replacing JavaScript tooling, updated in 2026 with Turbopack, Rolldown, Oxc, Biome, Rspack, Tailwind CSS v4, Deno, uv, and Ruff.
- Using GPT-4 to Assist in C to Rust Translation - Galois experiment using GPT-4 for behavior-preserving refactoring in C2Rust output.
- Function Argument Nullability Using an LLM - Galois article on augmenting C2Rust migration analysis with an LLM.
- Awesome Rust - Rust code and resources.
- Awesome Alternatives in Rust - Reimplementations and alternatives written in Rust.
- Awesome Transpilers - Transpilers and source-to-source compilers.
This list is intentionally narrow. It is not a general Rust list, a general AI coding list, or a list of greenfield Rust projects. Scale and ambition matter: entries should replace a meaningful surface of an established system or demonstrate unusual migration scope. Small wrappers, plugins, and accelerators are out of scope even when they are useful and well built.
Good entries should show at least one serious validation signal: test results, compatibility target, benchmark data, migration log, source and target code links, or discussion of unsafe code and semantic gaps.
Contributions are welcome. See CONTRIBUTING.md.