#chrome-use

A five-minute walkthrough of why agents should use the Chrome you're already signed into, how chrome-use connects to it, how it leaves your tabs alone, and what happens at a captcha.

During development and debugging, want to mock an unfinished API, change a request parameter, or modify a real response? chrome-use network route intercepts directly in the Chrome instance you are driving, with four uses: mocking responses, changing requests, modifying real responses, and blocking. This article explains why it is the lightest path—built on CDP Fetch, with zero JS injection, no added extension permissions, and no Chrome Web Store re-review—and includes real-device tests.

chrome-use test turns manual browser checks into repeatable YAML suites that can run in CI, effectively writing unit tests for the frontend. This article explains what it is, why its implementation can be so thin, and how to use it with cookie-use to switch back and forth between multiple accounts.