Can I drive multiple Chrome profiles at once?

Yes. Most browser-automation bridges funnel every call through a single global "current tab", so they drive exactly one tab per profile at a time. agent-webbridge runs a daemon per profile behind one local router, so every Chrome profile stays connected simultaneously. You drive each by adding a "profile" field to the same call.

Can I drive multiple Google accounts or logins at the same time?

Yes. Each Chrome profile carries its own Google login, so agent-webbridge lets Gmail, Drive, Ads, and Search Console accounts all be driven side by side from a single command interface — no logging in and out.

Why do most browser bridges only allow one login at a time?

Most bridges enforce a single connection slot and a single global current tab, so exactly one profile and one tab can be driven at a time. agent-webbridge sidesteps that with isolated daemons per profile behind a central router, plus per-tab DevTools Protocol attachment for true concurrency.

How do I switch profiles without toggling an extension off?

You don't. agent-webbridge points each profile's extension at its own daemon on disk with zero clicks and no popup, and keeps all profiles live at once — so there is nothing to toggle when you switch.

AWB-CONTROL v0.0.2 SYSTEM ONLINE

UTC: --:--:--

Configuration Overview

Clean-Room Browser Automation for AI Agents

agent-webbridge is open-source (MIT), clean-room browser automation for AI agents. It drives your real Chrome — with your real login sessions — across multiple Chrome profiles at once, and runs multiple tabs per profile concurrently. No closed-source dependency, no account, no telemetry, no curl|bash installer.

GitHub Repository → NPM Package View Setup

∞ Concurrent Accounts

N×N Profiles × Tabs in Parallel

macOS Optimized Target

MIT Open Source

Live Fleet Daemon Monitor

Active Google Chrome profile instances and live daemon statuses.

Profile ID	Browser Target	Connection Status	Avg Latency
"Work"	Google Workspace Account	Connected	42ms
"Personal"	Personal Google Account	Connected	36ms
"Developer"	Admin Console Profile	Connected	51ms

Simulated Router Requests Log

[19:27:52] INIT: Router successfully bound and listening

[19:27:53] FLEET: Found 3 Chrome profile extension mappings.

Execution Demonstration & Capabilities

Simultaneous Multi-Session Orchestration

Engine Capabilities

Multi-Session Scraping & Data Collection

Perform concurrent web scraping, DOM queries, and file collection across separate logged-in profiles. Perfect for compiling combined reports from multiple Search Consoles, reading multiple Gmail accounts, or downloading files from different drives simultaneously.

Concurrent Sessions

Drive multiple authentic Chrome cookies and local storage states at once. No session hijacking or logging out.

Real Browser Moat

Unlike headless scraping tools that face captcha blocks, fleet operates your real, logged-in Google Chrome instance headful, preserving authentic cookies and configurations.

Claude Code Skill Support

Equip your agent with the ability to scrape, navigate, and query several profiles sequentially or concurrently via one simple skill.

Live demo of an AI agent driving Work and Personal Chrome profiles simultaneously through agent-webbridge

● SCREENPLAY PREVIEW: One AI agent driving several profiles (Work and Personal) in parallel, opening distinct URLs and loading data simultaneously.

CLI Installation & Walkthrough

Interactive Setup Console

Download and install the CLI layer globally, or add it to Claude Code as an autonomous developer agent plugin.

npm i -g agent-webbridge

added 1 package, and audited 2 packages in 1s found 0 vulnerabilities $ awb --version 0.0.2

Command Builder & Network Playground

Test routing contract interactively

Request Configuration

Assemble a command body for the router to forward.

Target Profile

Action Method

Target URL

CSS Selector

Session Name

curl -s -X POST http://127.0.0.1:10086/command \ -H 'Content-Type: application/json' \ -d '{"action":"navigate","args":{"url":"https://search.google.com/search-console"},"session":"audit","profile":"Work"}'

FLEET TRANSMISSION RESPONSE Idle

Press "Transmit Command to Fleet" to simulate the network routing...

Architecture Comparison

Old Single Slot vs. Fleet Routing

The Single-Slot Limitation

Most browser-automation bridges enforce a single connection slot and one global "current tab", so they drive exactly one tab per profile at a time. Attempting to connect a second Chrome profile results in connection rejection, requiring manual toggle adjustments.

Simultaneous Session Isolation

We spawn one isolated background daemon process per Chrome profile (using deterministic port mappings). This allows each Google account profile to run fully isolated with separate cookies and local storage.

Transparent Router Gateway

The proxy router serves as the central API gateway on the native port 10086. It accepts standard HTTP commands, extracts the "profile" parameter, and forwards the payload transparently to the corresponding browser daemon.

Frequently Asked Questions

Internal Diagnostic Manual

Yes. Most browser-automation bridges enforce a single connection slot, meaning only one Chrome profile is driven at a time. agent-webbridge runs a daemon per profile and places a router on 10086. Every profile stays connected simultaneously, allowing you to select the target by passing a "profile" field in the request payload.

Yes. Each Chrome profile carries its own independent Google session and credentials. Because agent-webbridge runs a separate daemon for each profile, actions directed at Gmail, Search Console, Ads, or Google Drive for different logins can execute side-by-side.

Yes — this is the killer feature. agent-webbridge attaches the Chrome DevTools Protocol per tab (a Map keyed by tab), so N tabs in one profile run in parallel. Measured: 2, 5, and 10 tabs in a single profile each finish in about 2 seconds flat, versus 4s, 10s, and 20s if they ran serially. Two axes of concurrency: N profiles × N tabs per profile.

Most bridges enforce two singletons: a process refuses to start if port 10086 is occupied, and a single daemon will only connect to one browser extension at a time. agent-webbridge sidesteps these constraints by assigning isolated local directories and distinct ports to each daemon process, keeping the central port free for its router.

You don't have to. The awb connect command points each profile's extension at its own daemon by directly writing the destination URL to the Chrome extension's on-disk Local Storage LevelDB files (while Chrome is quit), with zero manual clicks — and keeps every profile live at once.