Skip to content

Agent orchestration

Several tabs, several agents, one browser, all at once

A conversation belongs to the tab it started in, not to whatever you happen to be looking at. Start one where an upload is running, another where support is waiting on an answer, a third watching a release, then go and read something else. The extension holds each session in its own tab and dials out to a single local daemon, which wakes one agent per session and streams the work back to the panel as it happens.

A board, mid-morning

Four tabs, four conversations, one browser

Three sessions work at once by default, which is why the fourth is holding for a slot rather than crowding the browser.

app.acme.com working

Invoices

Six invoices gone past due

  • sees six invoices past due
  • takes in the terms agreed on each
  • wording the reminders now

agent: claude

help.vendor.io approval

Ticket 8841

The renewal, argued back down

  • read fourteen messages of history
  • weighed the offer against last year
  • waiting on you before it reaches them

agent: codex

dash.deploys.dev working

Release 2291

Watching the release land

  • senses the progress the page gives off
  • pinned to this tab, in the background
  • 62 percent, about a minute to go

agent: claude

jobs.acme.com queued

Application

Applying with the resume you attached

  • holding for a slot
  • three sessions already at work

agent: agy

Underneath

One link out, one agent per session

One local daemon

127.0.0.1 · loopback only

Nothing listens inside the browser. The extension opens the link itself, and one daemon owns it however many sessions are in flight.

One agent per session

3 of 3 slots in use

Woken as you, on the CLI you already signed in to, and told about this session and no other.

The rules that keep it sane

What a session can and cannot reach

A session belongs to its tab, not to your attention

The conversation is bound to the tab it started in. It carries on there while you look at something else, its work stays in that tab instead of following you, and reaching into a tab it was never pointed at is a gated action.

Two sessions never share a tab

A tab another conversation has claimed answers TAB_IN_USE. Tabs a session opens for itself join that same session as subtabs, so everything it did stays in one transcript.

Three at a time, eight open

Three sessions work at once by default and eight can be open, so the fourth holds for a slot instead of crowding the browser. Raise maxConcurrentRuns as far as eight.

Stopping one leaves the rest alone

End the session you are looking at and the others carry on. Close a tab and only that one ends, with its transcript moved to History. A pulsing dot on the toolbar icon and on the tab’s own favicon marks whatever is still at work.

shared link

The same link carries anything else you point at it. Claude Code in one terminal, Codex in another, Cursor or Zed alongside them: they all reach the browser you are already signed into, and every step they take surfaces on the timeline marked external.

Stop describing the page. Hand it over.

Free and MIT licensed. Nothing to sign up for, no key to paste, and a fresh install connects to nothing until you redeem a pairing code yourself.

claude mcp add browsentic -- browsentic-mcp