AI News
All stories
Reported

Curl maintainer Daniel Stenberg says AI-built Rust rewrites trail curl's own bugfixes

Stenberg says agents converted about 185,000 lines of C into 340,000 lines of Rust while curl merged over 300 commits and about 200 bugfixes in roughly three weeks.

AI in Practice · · 3 min read

Curl maintainer Daniel Stenberg says that while AI agents converted about 185,000 lines of C code into 340,000 lines of Rust, the real curl project merged over 300 commits in a little more than three weeks. Those commits included a little over 200 bugfixes and a few vulnerability fixes. He argues that none of the Rust rewrites contain those fixes. He made the case in a blog post dated November 17, 2026. He wrote that he counted the line counts himself, but the post doesn't say how he did it.

Stenberg wrote about two rewrites he knows of. The first, urlx, appeared a few months earlier and was described as a memory-safe, from-scratch reimplementation of curl and libcurl. The second, posted in November, is a rewrite of curl and libcurl in Rust that doesn't use a different name. It claims to have spent 8,600 USD. Stenberg says he has not been in contact with anyone behind these projects. He knows of them only because people sent him links to their repositories. He suspects there are more he hasn't seen yet, and he says he doesn't know whether the projects are more than proofs of concept.

The cost figure drew pushback in the comments on the post. Commenter Joonas Kuorilehto said the 8,600 USD is an estimated API-cost equivalent. Because the work ran on a subscription, he said, the actual cost was much lower. Another commenter, Dàmian Lusq, noted that the rewrite's own write-up mentions a weekly limit only from October 28, a week after the rewrite began. Lusq argued that the work was probably partly subsidized. These are the commenters' views, not facts established in the post.

Stenberg's main argument is that writing code was never the hard part. He says an agent could make the conversion for three reasons. Curl is extremely well documented. Hundreds of existing open source applications use its API. Thousands of test cases can verify an implementation. In his view, the C code is the specification, and the agent only needs to convert it and polish until the tests pass. What makes curl hard to copy, he says, is the accumulated time, decisions, users, feedback and iterations behind it. Decades of ABI and API stability are part of that, and he says only curl can demonstrate them.

The post also makes a case against rewriting for safety. Stenberg says 81 vulnerabilities have been confirmed in curl so far in 2026. Of those, 14, or 17.3%, resulted from mistakes that most likely would have been avoided in a memory-safe language such as Rust. By his arithmetic, a Rust implementation would still have had 67 of those vulnerabilities. A commenter named Félix questioned how anyone could know that number, listing other Rust features such as sum types, traits and RAII. Stenberg replied that nobody can know the exact number of problems another language would have produced. He said the count of past curl vulnerabilities caused by C mistakes is verifiable because the data is public.

On maintenance pace, Stenberg says curl averages about 11 commits per day. The rewrite authors could follow those commits and convert them to Rust as they land. They could also ignore the bug reports or take their projects in other directions. The post doesn't say which they will do. He says that in another month the curl project did another 200 bugfixes and possibly a few more vulnerability fixes. He asks whether the clones will keep up with that pace.

Why it matters

Companies using AI agents to port or rewrite software should expect that a fast rewrite can fall behind the original's ongoing security and bug-fix work.

What you can do

When evaluating AI-generated rewrites of existing software, ask who will maintain them and how they will receive security and bug fixes.

Original source

Where we saw it

1 source

Simon Willison

AI wrote this summary from the sources listed, and nobody reviewed it individually before publication. Check the original source before you rely on it. How it works