A 70-Megabyte Browser Engine Wants to Displace Chrome for AI Agents

The 10,000-Star Spec Sheet

Obscura arrived with a comparison table that reads like a spec-sheet ambush. Thirty megabytes of RAM. Seventy megabytes on disk. Eighty-five milliseconds to load a page. Instant startup. The target is headless Chrome, which the project casts as a desktop browser shoehorned into data centers and agent loops. The repository recently crossed ten thousand stars, a threshold that signals the idea has found its audience among developers who measure infrastructure in cents per core-hour.

The proposition is simple. Chrome carries rendering pipelines, GPU sandboxes, accessibility trees, and user-interface baggage that an automated agent never touches. Obscura, written in Rust, keeps the V8 JavaScript engine and the network stack, jettisons the rest, and wraps the result in a binary small enough to fit on a decade-old USB drive. A Docker image built on distroless weighs roughly fifty-seven megabytes compressed. There is no Node.js runtime to install, no Chromium snapshot to download, and no package manager required on the host.

This minimalism would be merely academic without compatibility. Obscura implements the Chrome DevTools Protocol, the same wire format that Puppeteer and Playwright use to drive headless Chrome. For teams with existing automation scripts, this means the migration path is a WebSocket endpoint swap rather than a rewrite. In a landscape where CDP has become the de facto lingua franca of browser automation, speaking it fluently is the difference between a research demo and a production candidate.

Stealth as Standard Equipment

Where Obscura diverges from mere minimalism is its treatment of detection. Anti-bot systems have moved far beyond simple navigator.webdriver checks. Modern defenses evaluate canvas fingerprints, WebGL signatures, audio contexts, screen resolution, timezone, font lists, and hardware concurrency, looking for inconsistencies that betray automation. The 2025 Akamai State of the Internet report estimates bot traffic now accounts for over forty percent of commercial site requests, and the defense industry has responded accordingly.

Obscura bundles anti-fingerprinting and tracker blocking as built-in features rather than aftermarket patches. Per-session randomization covers GPU, screen, canvas, audio, and battery APIs. It masks internal properties so that Object.keys(window) remains safe, overrides Function.prototype.toString to return native code strings, and unsets navigator.webdriver. A blocklist of 3,520 domains strips analytics, telemetry, and fingerprinting scripts before they execute, preventing trackers from loading entirely rather than merely spoofing their results.

In the commercial anti-detect market, comparable fingerprint depth typically costs between twenty-four and two hundred dollars per month per seat for tools like GoLogin, AdsPower, or Multilogin. Obscura offers this at the binary level, free under an Apache 2.0 license. That said, the anti-detect space is an arms race with a short half-life. Fingerprinting defenses evolve quarterly, and what passes today may not pass tomorrow. The project makes confident claims, but no third-party source independently verifies them. As one analysis of the category notes, marketing claims for anti-detect tools often diverge from practical performance under heavy load.

The Agent Protocol Layer

The most telling architectural choice is not what Obscura removes from Chrome, but what it adds: a native Model Context Protocol server. While CDP compatibility serves the old guard of scrapers, the MCP layer speaks directly to the current wave of AI agents. Instead of exposing a raw WebSocket and letting a large language model fumble with JavaScript snippets, Obscura exposes structured tools—browser navigation, snapshots, clicks, form fills, and evaluation—that map cleanly to the tool-calling patterns used by Claude Desktop, Cursor, and similar agent hosts.

This places Obscura in the middle of a rapidly commodifying stack. Browserbase, a managed cloud platform, claims over one hundred thousand developers and nearly thirty-seven million unique browser sessions, pitching itself as the infrastructure layer for agents that need to handle CAPTCHAs, login walls, and dynamic UIs. It claims to unlock the eighty-five percent of the web that APIs cannot reach. Firecrawl, which has accumulated more than one hundred thirty thousand GitHub stars, markets itself as the web data layer for AI applications. Market projections cited by industry observers expect the AI browser segment to grow from $4.5 billion in 2024 to $76.8 billion by 2034, with seventy-nine percent of companies already adopting agent technology.

Obscura’s bet is that a meaningful slice of this market will prefer a self-hosted, open-source engine over a metered API—at least for the core runtime. The command-line interface supports parallel scraping across worker processes, proxy routing, and multiple output formats including raw response bodies, link extraction, asset enumeration as NDJSON, and DOM-to-markdown conversion. For agents that need to move fast without ringing up a cloud bill, the local binary is a compelling primitive.

A Crowded Engine Room

Obscura is not the only project trying to rewrite the headless stack in a systems language. Lightpanda, a Zig-based browser also embedding V8, has accumulated roughly thirty-four thousand stars and over eight thousand commits. It too targets AI agents and automation, and it too rejects the bloat of Chromium. Recent work there has focused on web API conformance, separating terminal and REPL histories, and build-system plumbing to support prebuilt V8 shared libraries. It has also established a Contributor License Agreement and a security monitoring workflow, suggesting governance maturity that a younger project may need to match. The divergence in language—Rust versus Zig—is less important than the shared thesis: the incumbent browser engine is over-provisioned for machine-driven tasks.

Where Obscura attempts to differentiate is in out-of-the-box stealth and AI-native protocols. Lightpanda’s roadmap reads like a standards-compliance exercise. Obscura, by contrast, ships a command-line interface with parallel scraping workers, proxy routing, and the MCP server. It is a more opinionated product, less a research browser and more a drop-in appliance.

Yet the commercial field is crowded with well-funded alternatives. Bright Data, Oxylabs, and ScraperAPI offer enterprise tiers with SOC 2 Type II certification, static IP allowlisting, and service-level agreements. Zyte maintains Scrapy, the oldest listed provider, and requires more overhead for AI integration. For organizations scraping at scale, compliance, proxy rotation, and data-retention policies often matter more than binary size. Obscura’s roadmap acknowledges this gap: the maintainer is already building a hosted version with managed infrastructure and residential proxies. The open-source engine will remain fully featured, the author promises, with no feature gating. Whether that balance holds will depend on revenue pressure once the cloud service launches.

Claims, Caveats, and the Cloud Question

The benchmarks posted in the README are dramatic—static HTML in fifty-one milliseconds against Chrome’s roughly five hundred, dynamic scripts in seventy-eight milliseconds against seven hundred. These are self-reported figures, and none of the provided external sources validate them. In a category where vendors routinely promise perfect stealth and sub-second latency, skepticism is warranted until independent tests confirm the numbers.

The project also carries the structural risk of solo maintenance. The voice of the README is singular, and ten thousand stars, while respectable, is a fraction of the gravity held by Browser Use or Firecrawl. Sustaining an anti-detect browser against the combined engineering budgets of Cloudflare, Akamai, and DataDome is a marathon that usually requires more than one runner. The first build from source compiles V8 from scratch, a five-minute reminder that this is still a heavy engine under the hood, however small the final binary. The engine exposes raw V8 flags, allowing operators to raise heap limits when JavaScript-heavy pages exhaust the default memory cap. It is a small detail, but one that signals the embed is real V8, not a toy interpreter.

Still, the underlying critique is sound. Headless Chrome was built for humans who needed a browser without a window; it was not built for fleets of agents that need only JavaScript execution, cookie jars, and plausible fingerprints. Obscura’s argument—that automation infrastructure has outgrown the browser it automates—resonates with the economics of the moment. If the self-reported performance holds, and if the stealth layer survives the next round of defensive upgrades, Obscura could become the default engine for developers who want to own their scraping stack. If not, it will at least have forced the question of why the agent economy is still paying a three-hundred-megabyte tax for the privilege of parsing a login form.