Chromium

Agent Browser Protocol: Chromium Fork That Makes Browsing a Step Machine for LLM Agents

ABP solves the fundamental impedance mismatch between async browser state and synchronous LLM reasoning by forking Chromium itself — freezing JS execution and virtual time between agent steps so the page literally waits for the model. At 90.5% on Mind2Web, this is the strongest signal yet that browser agents need engine-level integration, not another CDP wrapper. The MCP-native interface (REST + MCP baked into the browser process) is the right abstraction layer, but the Chromium fork dependency is a distribution bottleneck that will matter at scale.