Browser Use CLI 3.0 Cuts Agent Token Usage 6x With Direct Chrome Access

Coding agents like Claude Code and Codex are remarkably capable inside a terminal. They read files, write code, run tests, manage Git. But the moment a task requires a browser, they hit a wall. Browser Use just shipped CLI 3.0 to tear that wall down, and the approach is meaningfully different from what came before.

The token tax that was killing browser agents

The dominant approach to giving agents browser access has been MCP servers layered on top of Playwright. It works, but it's expensive. Playwright MCP gives you powerful browser control, but every screenshot, every DOM snapshot, every accessibility tree adds tokens to your context window. One GitHub issue documented a 6x token increase between versions. Users reported single screenshots consuming over 15,000 tokens, with some exhausting their entire five-hour token allocation in just a few automation steps.

That's the problem Browser Use CLI 3.0 is built to solve. The headline claim is 6x smaller output with fewer tokens consumed per action, which directly translates to longer, more capable agent runs before hitting context limits.

One websocket, nothing in between

Browser Use CLI 3.0 is powered by Browser Harness, and it applies what the team learned about agent harnesses: the latest models do best when you give them freedom, rather than abstracting away complexity. The CLI provides agents with a direct, dependable surface for acting in the browser.

The key architectural choice is going straight to CDP (Chrome DevTools Protocol), the low-level protocol Chrome exposes for remote control, rather than routing through a higher-level abstraction. Browser Harness connects an LLM directly to your real browser with a thin, editable CDP harness, for browser tasks where you need complete freedom. One websocket to Chrome, nothing between.