Parallel coding agents

Keep every agent in its own browser workspace.

Concept diagram of separate workspaces for Codex, Claude Code, and Cursor
One visible Hronaut process. A durable workspace for every task.

The problem

Parallel agents should not race through one browser.

A persistent profile keeps state, but it does not decide who may use it. See why a persistent profile is not a concurrency strategy →

  • Tabs stop meaning one thing. One agent navigates, closes, or reuses a tab while another still trusts its earlier snapshot of that page.
  • Roles and cookies collide. Two tasks may need different test accounts, organizations, feature flags, or local storage on the same site.
  • One task can end another. If the browser belongs to one client process, restarting that client can wipe state other work depends on.

How Hronaut keeps tasks apart

A visible boundary agents can follow.

Every agent task starts by creating a named workspace with browser_workspaces, then passes the returned UUIDv7 workspace ID to every browser tool call.

  1. 1

    Create

    Create a workspace with a fresh, human-readable task name. Hronaut returns a stable workspace ID and a private resume key. Keep the key private so the same task can reconnect later.

  2. 2

    Choose storage

    Use storage=scratch for a clean profile. To reuse sign-ins on purpose, call list-fork-sources, then create with storage=fork-workspace, a sourceWorkspaceId, and only the origins you need.

  3. 3

    Stay scoped

    Pass the workspace ID to every page tool. Tabs from another workspace are rejected. After reconnecting, call action=resume with the workspace ID and private resume key before inspecting the page.

  4. 4

    Archive or close

    Archive the workspace to keep its state for later, or close it permanently to delete its isolated browser data.

Storage boundary

Separate cookies and storage, not just separate tab labels.

Every Hronaut workspace gets its own persistent Electron partition for cookies, local storage, cache, service workers, and related site state. Workspace membership is fixed: tabs cannot move between workspaces, and a tab ID from another workspace is rejected.

A fork copies cookies and local storage into a new workspace with a blank tab. It does not copy source tabs, passwords, IndexedDB, or caches, and it inherits the source's navigation restrictions. Turning off direct agent access to a source still allows forks, so that switch does not keep its reusable sign-ins secret.

Returning to a task

Keep the state. Recheck before acting.

  • One writer at a time. A single live connection holds the workspace's five-minute, renewable write lease. Other authorized connections can inspect but not write.
  • Conflicts are refused safely. A conflicting write returns BUSY or LEASE_LOST without dispatching the action. Pause, disconnect, release, or expiry removes write authority.
  • Hand off deliberately. Inspect fresh state, check ownership-status, and use claim-ownership only when ready to continue.

The lease coordinates writers inside one Hronaut process. It does not coordinate separate installations. Archive useful state to keep it, or close a workspace permanently to delete its browser data.

Choose the right model

Isolation can belong to the project, your browser, or a dedicated app.

Project-scoped automation

Playwright MCP profiles

Playwright MCP creates persistent profiles from the workspace root and supports isolated sessions. Its documentation notes that one persistent profile can be used by only one browser instance at a time.

Playwright MCP profile modes ↗

Exact browser already open

Existing Chrome

Connect when the task must inspect the exact tab and profile already on screen. The agent gets the authority and shared state of your everyday browser.

Chrome DevTools auto-connect ↗

Durable multi-agent work

Hronaut workspaces

Use one separate, visible browser app when task profiles should outlive client sessions and stay isolated from each other.

Compare browser ownership models →

Limits and sources

Use workspace isolation for interactive local tasks, not as a CI replacement.

Hronaut embeds Chromium and is built for visible, long-lived desktop work. Use Playwright or another test runner when ephemeral headless jobs or Firefox and WebKit coverage matter more than durable sessions a person can watch.

Sources for this guide

Try the workspace boundary

Run two browser tasks without sharing tabs or sign-ins.

Install Hronaut, connect two MCP clients, and have each create a clearly named scratch workspace before opening a page.