← In the News

Curl's maintainer counts what the agent-written Rust rewrites already lack

Actual curl rewrites in rust · Daniel Stenberg, curl maintainer · daniel.haxx.se, November 17, 2026

Machine-readable Download Markdown

Stenberg points to two public Rust reimplementations of curl: urlx, which claimed to be a memory-safe, from-scratch reimplementation, and a November rewrite that keeps the name curl and, he notes, claims to have spent 8,600 USD. He counted the result: agents converted 185,000 lines of C into 340,000 lines of Rust in a little more than three weeks. Over the same weeks the curl project merged over 300 commits, a little over 200 of them bug fixes, plus fixes for a few vulnerabilities. None of those bug fixes are in the rewrites. He credits the speed to the material agents had to work from: curl is extremely well documented, hundreds of open source applications use its API, and thousands of test cases can check an implementation. "Writing code once was never the big deal with software and it still isn't," he writes. He also puts a number on the memory-safety argument: of the 81 vulnerabilities curl has confirmed so far in 2026, 14 (17.3%) would most likely have been avoided in a language such as Rust, so a Rust curl would still have had 67.

Why it matters: A mature project with full documentation and a large test suite is close to an ideal specification, which is why agents can reproduce it in weeks. Stenberg's figures price the part they do not reproduce: curl averages about 11 commits a day, and a fork has to absorb that stream or fall behind. Anyone costing an agent-driven rewrite should budget for that maintenance as well as the conversion.