All but React Native are in beta.
All but React Native are in beta.

Buoy Web lets an AI use the web for you. It clicks and types like a person. It only works in the tabs you give it. Your other tabs are left alone.
Tested on 256 web chores
3.4x faster than Claude in Chrome. 2.4x faster than ChatGPT's.
You wait less, and your AI bill is smaller.
3.4x
faster than Claude in Chrome
2.4x
faster than ChatGPT's tool
34%
of the AI cost per task done, or less
All three ran in Claude Code on Claude Haiku 5.5, with the same chores. A server checked every answer. See the whole test
| Ask Buoy in Chrome | Your AI coding tool | |
|---|---|---|
| What it is | A chat in Chrome's side panel | Claude Code, Cursor, Codex or VS Code use Chrome for you |
| What you need | The Buoy Web extension and a Buoy sign-in | The Buoy MCP. The extension is best, but not a must. |
| Cost | Uses AI credits. They come with paid plans. | Free. No account. |
| Works on | Every system | Mac for now |
Copy this prompt into Claude Code, Cursor or Codex. Your AI runs the setup and tells you the steps it can't do for you.
Get Buoy Web from the Chrome Web Store. Click Add to Chrome.
Now ask it to do something, like "Find the weather in Provo this weekend." It works in that tab and tells you what it found. Its tabs sit in a green "Buoy" tab group. The page glows green while it works.
The first time it clicks or types on a site in a chat, it asks you. Pick Always allow for sites you trust. It also asks before it clicks a button with a word like Buy, Pay, Send, Post or Delete. It finds those buttons by their words, so it can miss some. Watch what it does on sites where it can spend money.
Open the panel's menu and pick Settings.
The prompt above does this for you. To do it by hand:
Run this once in a terminal:
npx -y @buoy-gg/mcp@latest init --web
npx -y @buoy-gg/mcp@latest init --web
It adds Buoy Web to Claude Code, Cursor, Codex and VS Code, if you have them. It works in every project.
Add the Buoy Web extension to Chrome.
Restart your editor.
Then ask your AI to do something on the web. When it's connected, the Ask Buoy panel's footer says "Editor bridge on".
No extension? Buoy Web still works with your AI tool. It opens its own Chrome window. Sign in to sites there once. It keeps those sign-ins in ~/.buoy/web-profile.
Each step is a real mouse click or key press. The reply says what changed on the page. So the AI rarely needs to read the page again. That's what makes it fast.
The tools are open, read, click, type, key, wait, scroll, drag, hover, select, tabs and dialog. Your AI coding tool also gets upload and screenshot.
upload only sends files inside your project folder. It never sends secret files like .env or keys.Chrome shows a "started debugging this browser" bar while Buoy works. That's Chrome's rule for this kind of extension. If you click Cancel, Buoy stops. The AI asks before it tries again.
See the privacy policy.
init --web command again. Then wait a few seconds.Once a day, the Buoy MCP sends a random id, its version, your system type and a tag that says it's Buoy Web. It never sends web addresses, page text or what your AI did. Turn it off with BUOY_TELEMETRY=0 or DO_NOT_TRACK=1. See Telemetry.
Google Chrome. Other browsers built on Chrome, like Brave and Edge, may work. We haven't tested them yet.
We measured our speed numbers in Claude Code. Claude Code loads Buoy Web's tools up front. Other editors may load them more slowly.