2026-11-18 · ← News
Agents Rewrote curl in Rust, Then Upstream Moved 200 Fixes Ahead
Two agent assisted projects turned curl's 185,000 lines of C into roughly 340,000 lines of Rust. curl maintainer Daniel Stenberg says the original project meanwhile merged more than 300 commits and over 200 fixes, making maintenance rather than the first rewrite the real test.
The image could not be loaded.
Daniel Stenberg has responded to two projects using AI agents to build Rust implementations of curl and libcurl. By his count, they turned 185,000 lines of C into roughly 340,000 lines of Rust. One project reports spending 8,600 dollars.
The rewrite took weeks while the living project kept moving
In a little over three weeks, the original curl merged more than 300 commits, over 200 bug fixes and fixes for several vulnerabilities. Stenberg says the Rust clones do not contain those changes. Upstream continues at an average pace of about 11 commits a day.
The agents also had unusually favorable material. curl is thoroughly documented, used by hundreds of open source applications and covered by thousands of tests. Translating a well specified snapshot is easier than continuously processing user reports and changing an implementation without breaking compatibility.
Open source value extends beyond the source tree
The projects show that agents can quickly produce a large compatible implementation. They do not show that agents can replace a community that triages bugs, makes design decisions and preserves API and ABI stability over decades. A code snapshot captures the result of that work, not the mechanism that keeps producing it.
For companies, this is a warning against valuing agent projects by generated line count or by passing today's tests. Costs also arrive with every upstream change, new platform and ambiguous bug report.
Rust addresses only part of curl's security record
Stenberg says that of 81 vulnerabilities confirmed in curl during 2026, a memory safe language would probably have prevented 14, or 17.3 %. The remaining 67 were not primarily memory safety failures by his assessment. These are the maintainer's figures, not an independent audit of either rewrite.
Rust can remove an important class of defects, but it does not import logic fixes, edge case knowledge or operational experience. The language lowers a specific risk. It does not maintain compatibility with a project that changes every day.
Synchronization after the first release will decide the outcome
The next several months will reveal the value of these rewrites. The key signals are whether their authors continuously absorb upstream fixes, handle their own reports and demonstrate compatibility and security beyond the original test suite.
If agents can cheaply follow an average of 11 commits a day, they could enable a new model for maintaining compatible implementations. Otherwise, the impressive conversion will remain a photograph of a project that kept walking.
Lilith's verdict
Agents built a second curl faster than an ordinary team could. While they posed at the finish line, the original project had already moved more than 200 fixes down the road.