Browser Beta

A Chromium-based browser where AI agents work in the tabs you pick, and nothing on a website changes until you allow it.

I built Browser because I didn't want to hand an agent my whole browser to get help with one tab. Agents here can research with cited sources, fill in forms, build comparison tables, watch a page for changes, learn a workflow you show them, or look into a broken page. The film shows one of them, “Watch for changes,” keeping an eye on a sample shop.

Figure 1. A silent recording of the development build, on fictional sample sites. MP4

Chapters

  1. 0:00Tabs across the top, slim sidebar.A script recorded this from the real app and checked every page for private data along the way.
  2. 0:06One address row: go, search, ask, hand off.The same box goes to a site, searches, asks about the page or hands an agent a task.
  3. 0:16“Watch for changes,” one tab.The agent gets only the tab you pick, and the screen says so: “Agents use only the tabs you select.”
  4. 0:24Ask answers from the page.Ask reads the open page and answers on your Claude subscription, in 5.8 s here at low effort.
  5. 0:36Watcher spots the drop, no AI model.The watcher checks the page on the computer every 15 s with 0 model calls and 0 tokens. It reported the drop 16.8 s after it started.
  6. 0:43Review before Send to Workspace.You see exactly what would leave before anything goes to Workspace.
  7. 0:49All tabs at once.Each open page becomes a card. There are five here.
  8. 0:53Board sorts agent work.Runs are sorted by what they need from you.

Numbers

860
tests passing

860 passed, 1 skipped across 92 files on the current build.

0
model calls in the watcher

Its run card in the film reads “0 steps · 0 tokens”.

5.8 s
Ask answer

Timed in the film from pressing Return until the answer stopped changing, at low effort, so the answer itself took a little less.

56
privacy checks, 0 failures

At the end of every scene, the text of every open page was checked for personal names, email addresses, machine paths, internal app names and real web addresses.

System diagram

Browser: selected tabs, action approval and local data pathsYou use Browser's tabs and one address row. An agent is limited to the tabs you pick. Each action is classed before it runs; you choose which kinds ask first. Each approval covers one action. Money, deletion and credentials always ask, whatever the settings. Ask reads the open page and answers on your Claude subscription, with a first-party claude.ai plan checked before every run, or an Anthropic API key you add. The watcher runs on the computer every 15 seconds with zero model calls. Send shows a review sheet; the address, title, excerpt and note go through a temporary local file over a paired link on the same computer, not a server. The arrow to Workspace is dashed: after you send, not shown in the film. Browser Sync locks data on the computer with keys only your devices hold, through a folder you choose whose owner sees only scrambled files, to your other devices. Passwords sync only if switched on; cookies, API keys and the never-touch list never sync. No Browser server is in the path.YouBrowserTabs and oneaddress rowAgentOnly the tabs youpickApproval gateEach action classed before it runs. Choose which kindsask first. Each approval covers one action. Money,deletion and credentials always ask, whatever thesettings.WebsiteAsk reads the open pageYour Claude subscription: afirst-party claude.ai plan checkedbefore every run; or an Anthropic APIkey you add.Local watcherEvery 15 seconds on thecomputer. 0 model calls.Review sheet → temporary local fileAddress, title, excerpt and note. Pairedlink on the same computer, notthrough a server.Workspaceafter you send(not shown in thefilm)Browser SyncLocked locally with keys only your devices hold → folder you choose (owner sees scrambled files) → your other devices. Passwords only if switched on.Cookies, API keys and the never-touch list never sync. No Browser server in the path.Browser: selected tabs, action approval and local data pathsYou use Browser's tabs and one address row. An agent is limited to the tabs you pick. Each action is classed before it runs; you choose which kinds ask first. Each approval covers one action. Money, deletion and credentials always ask, whatever the settings. Ask reads the open page and answers on your Claude subscription, with a first-party claude.ai plan checked before every run, or an Anthropic API key you add. The watcher runs on the computer every 15 seconds with zero model calls. Send shows a review sheet; the address, title, excerpt and note go through a temporary local file over a paired link on the same computer, not a server. The arrow to Workspace is dashed: after you send, not shown in the film. Browser Sync locks data on the computer with keys only your devices hold, through a folder you choose whose owner sees only scrambled files, to your other devices. Passwords sync only if switched on; cookies, API keys and the never-touch list never sync. No Browser server is in the path.YouBrowserTabs and one address rowAgentOnly the tabs you pickApproval gateEach action classed before it runs.Choose which kinds ask first.Each approval covers one action.Money, deletion and credentialsalways ask, whatever the settings.WebsiteAsk reads the open pageYour Claude subscription: afirst-party claude.ai plan checkedbefore every run; or an AnthropicAPI key you add.Local watcherEvery 15 seconds on the computer.0 model calls.Review sheet → temporary local fileAddress, title, excerpt and note.Paired link on the same computer,not through a server.Workspaceafter you send(not shown in the film)Browser SyncLocked locally with keys onlyyour devices hold → folder youchoose (owner sees scrambledfiles) → your other devices.Passwords only if switched on.Cookies, API keys and the never-touch list never sync. No Browserserver in the path.
Figure 2. How an agent's actions and your data move through Browser. The dashed arrow is the step after you send, which the film doesn't show.

How it's built

An agent working on a real website should never change a page on a guess, and the person using it should be able to see and stop every step. By default, every click, edit or page change asks first and shows exactly what it will do, and each approval covers one action. If you type or click in the page, the agent pauses, and Stop takes over at any time.

Browser is built on Electron 44, the open-source shell around Chromium, so every tab renders in Chromium. Before an agent action runs, it is put in one of five classes: read, local change, draft, outside change or sensitive. You choose which classes ask first. Sensitive actions, meaning anything involving money, deletion or credentials, ask every time, and no setting can auto-approve them. That rule is one of 25 passing policy tests.

Ask runs on your Claude subscription, or on an Anthropic API key you add in Settings. On the subscription route it checks before every run that the sign-in is a first-party claude.ai plan, and stops rather than bill an API key. That check is one of 16 passing login tests.

The watcher rechecks loaded pages every 15 seconds on the computer, without calling a model.

Browser and Workspace talk over a paired link on the same computer, not through a server. Browser Sync, in Settings, locks everything on the computer before it leaves, using keys only your devices hold. It carries bookmarks, favorites, skills, memory, look and open tabs through a folder you choose, and the folder's owner sees only scrambled files. Nothing travels through a Browser server. Passwords sync only if you switch them on, and cookies, API keys and the never-touch list never sync. Adding a computer needs the recovery code.

Walkthrough

  1. Tabs run across the top, and the slim sidebar holds Search, All tabs, Board, Saved, History, Downloads, Agents, the pinned sample sites and More.
  2. The film types http://shop.example/oak-lift-pro into the address row. Its tooltip reads “Go, search, ask, or give an agent a task,” and typing offers Search, Ask and “Give to an agent.” The film takes the handoff.
  3. With only the shop tab selected, the film picks “Watch for changes.”
    Browser development build with sample sites: The watcher is already running.
    The watcher is already running.
  4. The film asks “what does it cost now, and when does it ship?” Ask replies that the Oak Lift Pro frame costs $429, is in stock, and ships tomorrow.
  5. While the watcher runs, the sample shop changes its own page. The report reads “Changed: Oak Lift Pro frame · Shop,” above “No website actions recorded. 0 steps · 0 tokens.”
    Browser development build with sample sites: The watcher reports the sample price drop.
    The watcher reports the sample price drop.
  6. The Send to Workspace sheet lists the page title and address with a typed note. Only the address and title, the chosen excerpt and the note would go through a temporary local file. The film points at Send but never presses it.
    Browser development build with sample sites: Review before Send. Sending is not shown.
    The review sheet before Send.
  7. All tabs shows every open page as a card, five in all. One card reads “Open it once for a picture,” which is the app's text for a tab it hasn't drawn yet.
  8. The Board sorts agent work into Needs you, Working, Ready for review and Watching.
    Browser development build with sample sites: The watcher is in Watching with one result ready.
    The watcher is in Watching with one result ready.

Limits

This is the development build, not a release package. The sites in the film are fictional and were served from the recording computer, but every click and keystroke is real input, and the watcher report, All tabs and the Board are the app's own output. Ask's answer is one real Claude turn.

Search is offered but never run, and the film stops at the review sheet without sending anything to Workspace. The test count is from October 2026 and will change as the build does. The timings come from one run on the recording computer, so they say nothing about speed on other machines.