A 3–8ms latency budget over Chrome DevTools Protocol — Weavetab Research

How Weavetab MCP achieves single-digit millisecond dispatch by pinning a native CDP client to the same event loop as the tool router, and why we rejected WebDriver, Playwright, and Puppeteer as transport layers.

A 3–8ms latency budget over Chrome DevTools Protocol

Published: 2026-06-19

How Weavetab MCP achieves single-digit millisecond dispatch by pinning a native CDP client to the same event loop as the tool router, and why we rejected WebDriver, Playwright, and Puppeteer as transport layers.

## The budget

An agent-driven browser session is bounded by the model's turn latency, not the browser's. That leaves a small but real budget for the tool layer itself. We targeted **3–8 ms** end-to-end for a call like \