Give Your AI Agent Your Logged-In Browser

Chrome Sync copies your already-authenticated sessions — cookies and per-site local storage — from your local Chrome into your AgentPod cloud browser, one domain at a time, without ever sharing a password.

Install the Chrome Extension

Chrome Web Store — Coming soon (pending review)

The listing (AgentPod Chrome Sync) has been submitted and is currently pending Google's review — no longer a draft. It isn't installable from the store until Google approves it. Until then, install the verified v0.1.0 GitHub release (unzip, then chrome://extensions → Developer mode → Load unpacked), or use the CLI below — it needs no installation at all.

What Gets Synced

Transferred

  • • Cookies for each domain you explicitly approve
  • • Per-origin localStorage for approved domains
  • • Nothing until you click "Approve" on a specific domain

Never transferred

  • • Your password (there is nothing to type in)
  • • Browsing history, bookmarks, or autofill data
  • • Cookies for any domain you haven't approved
  • • Your identity-provider or AgentPod console session — those domains can't be approved at all

Consent and Domain Selection

1

Deny-by-default

Nothing is read from your cookie jar until you add a domain. No jar-wide scan happens in the background.

2

Approve a domain

Type a domain (e.g. github.com) in the popup and approve it. This is a real user click that also grants the matching browser "host permission" — consent and permission move together, never one without the other.

3

Some domains can't be approved

Identity providers and AgentPod's own console are on a blocked list. Syncing those would let your cloud browser act as you against the systems that control your account.

4

Revoke anytime

Remove a domain from the popup's list to stop syncing it. Removing the extension entirely (chrome://extensions) clears everything it stored locally.

Signing In, Pushing, and Verifying

1

Sign in

Click "Sign in" in the popup (or run the CLI's login command). It opens the real AgentPod console sign-in page; once you're signed in, the extension/CLI stores a token for your account — never your password.

2

Pick the target agent

Your account can have more than one deployment. Choose which one (by subdomain) should receive the synced session — the same tenant you'd chat with in the console or Telegram.

3

Push

Click "Sync now" in the popup, or run the CLI's push command. Cookies and localStorage for your approved domains are sent over an encrypted connection straight into that tenant's cloud browser.

4

Verify it worked

The popup/CLI reports an injected count (e.g. "Injected 3394 cookies") with zero errors. To double-check, open the console's browser view for that tenant and confirm the site shows you logged in.

Security, Privacy, and Limitations

Security

  • • Every push is HTTPS-only, enforced before the request is even built, not just by convention
  • • Tokens are stored locally on your machine (or in the extension's local storage) — never synced to Google's servers
  • • Cookie values, tokens, and auth headers are redacted from every log line

Logout / revocation

  • • CLI: rm -rf ~/.config/chrome-sync clears the stored token
  • • Extension: remove a domain in the popup, or remove the extension entirely to clear everything
  • • A synced session is only revoked in the cloud browser itself by logging out there, or by re-deploying the tenant

Limitations

  • • Sites that bind sessions to a device fingerprint or IP may still ask you to re-authenticate
  • • The CLI needs your local Chrome running with an active session on the domain you want to sync
  • • The extension only syncs domains you've individually approved — nothing is jar-wide

Troubleshooting

  • • "Could not connect to Chrome via CDP": make sure a local Chrome is actually running
  • • "Found 0 cookies": you aren't signed into that domain in the active Chrome profile
  • • Session rejected after push: some highly secure sites require re-auth even with valid cookies
  • • Blocked domain: identity providers and the console can't be approved — this is intentional, not a bug

CLI Fallback (Available Now)

No extension install required. Works today, published to npm as @vibetechnologies/chrome-sync. The commands below always run the latest published release — no version pinning to go stale.

npx -y @vibetechnologies/chrome-sync@latest login

one-time browser sign-in

npx -y @vibetechnologies/chrome-sync@latest push

syncs your active Chrome session

Ready to Sync?

Open your console and give your agent the context you already have.

Open the Console