Nicheloom

Market intelligence for builders — see what's gaining traction before it's crowded.

Urlx

an agent-made Rust replacement for curl/libcurl

Details

External ID
47490735
Source
HN
Company
—
Product
Urlx
Website domain
github.com
Launched
March 23, 2026
Cohort
—
Upvotes
5
Upvotes percentile
0.1070110701107011
Tags
—
Fetched at
Sept. 7, 2026, 9:26 p.m.
Updated at
Sept. 7, 2026, 9:26 p.m.

Description

Recently several AI labs have published experiments where they tried to get AI coding agents to complete large software projects.- Cursor attempted to make a browser from scratch: https://cursor.com/blog/scaling-agents- Anthropic attempted to make a C Compiler: https://www.anthropic.com/engineering/building-c-compilerA few weeks ago I posted xmloxide, an agent-made Rust replacement for libxml2 made by pointing Claude code at the libxml2 test suite: https://news.ycombinator.com/item?id=47201816curl is arguably the most widely deployed software in the world. It's 180,000 lines of C with a history of memory safety CVEs. The curl project itself tried to address this by adding a rust-based HTTP backend using hyper, but after four years of work, they abandoned the effort in December 2024. Daniel Stenberg wrote that, "there simply were no users asking for it and there were almost no developers interested or knowledgeable enough to work on it".- Daniel Stenberg's blog post on dropping hyper: https://daniel.haxx.se/blog/2024/12/21/dropping-hyper/- Hacker News discussion: https://news.ycombinator.com/item?id=42478911The key insight from my xmloxide work was that an agent can iterate very quickly when given a comprehensive test suite as a specification. The majority of the development for urlx was done in two ~16 hour long iteration loops where claude code would implement some features, run the tests, and then plan what to do next. Towards then end I took a more manual approach telling it to analyze the remaining failures, make issues, and submit them to teams of subagents to fix.urlx now passes 1,300 of 1,300 applicable curl tests (100% pass rate). It supports HTTP/1.0-1.1, HTTP/2, HTTP/3 (QUIC), FTP/FTPS, SFTP/SCP, WebSocket, SMTP, IMAP, POP3, MQTT, DICT, TFTP, Gopher — with 261 CLI flags, authentication (Basic, Digest, NTLMv2, SCRAM-SHA-256, AWS SigV4), cookies, HSTS, proxy support (HTTP/SOCKS4/5/HTTPS tunnel), and a libcurl-compatible C ABI. There are some features still left to do that I might come back to.- GitHub: https://github.com/jonwiggins/urlx- crates.io: https://crates.io/crates/urlx-cli- Install: cargo install urlx-cli or brew install jonwiggins/tap/urlxThe same lesson from xmloxide applies here: when a project has a good test suite, an agent can use it as a specification and converge on a working implementation surprisingly fast. curl's test suite turned out to be an excellent spec, the hard part was already done by the curl contributors over 25 years.I don't expect anyone to replace curl with this, but I think there's something worth paying attention to in the pattern: take a well-tested project, point an agent at the test suite, and get a fast reimplementation. I think this also points to a need to adopt test-driven-development when using AI coding tools, as it allows them to iterate autonomously before needing human input. I also think this changes the economics of software development, what used to be a multi-year, multi-engineer commitment is becoming a task you can meaningfully attempt in days by setting up an agent to rapidly iterate on it alone.

Enrichment

Theme
browser automation and scraping for AI
Vertical
Horizontal
Function
Agent / copilot
Audience
Developer
AI stance
AI-native
Project type
Commercial product
Normalized one-liner
ai-generated rust replacement for curl
Manually corrected
False

Could you build this?

No Re-implementing curl/libcurl involves vast RFC-compliant protocol implementations (HTTP/1/2/3, TLS, FTP, DNS, SOCKS) and cross-platform socket multiplexing.

What it would actually take: The project requires a networking stack written in Rust supporting multiple application protocols, custom state machines, TLS negotiation (via rustls or OpenSSL bindings), and HTTP/3 over QUIC. The difficult part is edge-case protocol conformity, proxy handling, connection pooling, and matching libcurl's extensive option interface and platform robustness across dozens of OS environments. It requires specialized protocol engineering and low-level networking knowledge.

Discussion

1 comment analyzed.

Concerns raised: Performance issues - excessive cloning in Rust implementation causes slowness

Feature requests: Optimize performance to reduce cloning overhead

Competitors

Other products that read as similar to this one — 285 launches clear the similarity bar, closest 8 shown.

Attention rank: #264 of 286 (itself plus its competitors, highest first — normalized so YC and Product Hunt are compared fairly).

Launched 140 days after the earliest competitor.

Other launches for this product

Same idea, different domain

Nobody's really built a agent / copilot tool for Agriculture yet.