Browser Use ships Pi, a TypeScript web agent that writes JavaScript into a persistent V8 REPL and drives Chrome through raw CDP

Browser Use published browser-use-pi on 2026-09-05, a TypeScript SDK for a web agent that writes JavaScript, evaluates it in a persistent V8 REPL, and drives Chrome through the raw Chrome DevTools Protocol. The repository is at 126 stars as of 2026-09-09, four days after it appeared, under the MIT licence.

The control loop

Pi hands the agent a live JavaScript environment as its action surface. The agent receives an accessibility tree and screenshots, writes JavaScript, and evaluates it in a V8 REPL that persists across steps. It can build the helpers it needs as it goes, and it can inspect any element or property that JavaScript can reach. The README describes it as "the programmability of Browser Harness, with sessions, saved logins, streaming and typed results".

The runtime requires Node 22.19 or newer, or Bun 1.3.14 or newer, and Bun also needs Node so it can host the V8 worker. Pi supports either a hosted browser through Browser Use Cloud or a local Chrome, and the README shows the cloud path as the default so a first script does not need a local Chromium install.

Sessions, follow-ups, and typed results

Pi carries the primitives Browser Use has already shipped through its Python and macOS lines: follow-up turns on the same agent, saved logins, persistent workspaces, streaming, hooks, typed results and compaction, and caps on steps or time or cost that preserve partial work. Upstream models come through Pi's provider catalogue, which today includes OpenRouter and custom providers, and the model call sits behind the same OpenAI-compatible surface.

Ship-ready caveats the README states out loud

The JavaScript worker has filesystem and network access, so the README says out loud that "JavaScript runs in a killable worker with filesystem and network access. Use an isolated machine for untrusted tasks." Anonymous run counters are on by default, and the README documents both telemetry: false and the DO_NOT_TRACK=1 environment variable as ways to turn them off. There are no published benchmark numbers in the announcement itself, only a link to a historical benchmarks page in the docs, so a team choosing Pi should read that page and re-run any measurement that matters on their own task.

For a team already writing agents on top of Playwright or Puppeteer, the trade Pi asks for is a runtime cost, a Node or Bun toolchain, and an isolation boundary in exchange for a code-first control surface and a set of session primitives that would otherwise have to be built. 126 stars in four days is real traction inside the browser-use community, so the useful signal for a team outside it is what the star count and the issue tracker look like after another month.

Source

The browser-use/browser-use-pi repository on GitHub.