Chrome Controlla ships six-tool Chrome MCP that treats unknown side effects as a real outcome
Swimming_Ask3859 · reddit · 2026-11-02
The Chrome Controlla maintainer detailed the project's six-tool architecture on r/mcp: browser, snapshot, act, workflow, extract, and verify — an Apache 2.0 open-source Chrome MCP built for Claude Code browser automation.
Key design points:
- Multi-step browser tasks run as one bounded workflow
- Tracks the exact tab and document being controlled; recovers stale element references and layout changes automatically
- Uncertain write results are never silently retried — the tool reports exactly what it knows
Stack: Rust, a Manifest V3 Chrome extension, and Chrome Native Messaging. Measured performance: ranked snapshot 32ms with five CDP commands; full snapshot of a 4,103-node page 103ms; a 3,973-character Google Docs write verified independently afterward. Chrome-only for now; the author is soliciting failure cases from users of Playwright and other browser MCPs.
Related event: Chrome Controlla: open-source verification layer for browser agents(2 posts)→
More from coding & agent
- A scorecard for agent pilots: tasks, interruptions, missed decisions — krishnan · 2026-11-02
- Managing agents is babysitting: every ping arrives equally loud — krishnan · 2026-11-02
- A task you can't verify yet isn't done — agents need a 'deferred' task state — Key-Register-1969 · 2026-11-02
- A Redditor's ranked list of small models for running coding agents without a big GPU — transanethole · 2026-11-02
- Building revenue-team agents taught us context matters far more than model choice — hossam_elkhateeb11 · 2026-11-02
- "1% faster isn't enough, this should be 10x faster" becomes an AI-coding meme — DanielLockyer · 2026-11-02