✓ ShippedByAgents
Practitioner (own blog/paper) Language port

Ladybird ports its JavaScript engine's parser and bytecode compiler from C++ to Rust in two weeks with Claude Code and Codex

Ladybird founder Andreas Kling used Claude Code and Codex to translate LibJS's lexer, parser, AST and bytecode generator from C++ to Rust. He describes it as human-directed, with hundreds of small prompts and several passes of adversarial review by different models. The requirement was byte-for-byte identical output: every AST and all generated bytecode match the C++ pipeline, with zero regressions across test262 and Ladybird's own tests and no performance regressions on tracked JS benchmarks.

The numbers (as reported)

Output sizeAbout 25,000 lines of Rust
TimeAbout two weeks
Estimate without AIMultiple months by hand (author's estimate)
test26252,898 tests, 0 regressions
Ladybird regression tests12,461 tests, 0 regressions

Facts

Company / subject
Ladybird
Tools
Claude Code, OpenAI Codex
Codebase
brownfield
Work type
Language port
Stack
C++, Rust, JavaScript engine
Published
2026-02-23
Last checked
2026-10-20

What the source claims Practitioner (own blog/paper)

Claimed by the builder, writing about their own work. Not checked independently.

  • About 25,000 lines of Rust in about two weeks, where Kling says it would have taken him multiple months by hand ~2 weeks vs multiple months
    “The same work would have taken me multiple months to do by hand.”
  • Zero regressions across 52,898 test262 tests and 12,461 Ladybird regression tests, and no performance regressions 0 regressions
    “No performance regressions on any of the JS benchmarks we track either.”

Caveats

Self-reported by the project founder. Not autonomous: the author decided what to port, in what order and how the Rust should look. The code is intentionally non-idiomatic Rust that mirrors the C++. No cost or token figures given.

More stories by tool: Claude CodeOpenAI Codex

Related topics: Language portsBrownfield codebases

Source

Ladybird blog (Andreas Kling)

One email a week: what actually shipped

New sourced stories, the numbers behind them, and what didn't work. No hype.

We'll only use this to send the newsletter. See the privacy page.