AGI

AGI in Chrome · Coming soon

AGI in Chrome

The architecture

The browser asks. Managed Cloud answers.

AGI in Chrome never runs a model locally and never stores provider keys. It captures what you point at, sends it to Managed Cloud under your account, and brings the answer back into the panel. Pairing AGI Desktop adds a local road for selections and captures, not a second place an answer can come from. Computer use keeps the same gateway and adds the screenshots it takes of your tab.

  1. Browser captures intent

    The side panel and content scripts read the active tab and your prompt only when you ask. No model runs in the browser process and no provider key is ever stored there.

  2. Managed Cloud answers

    Your message, the conversation so far, and any page text you attached go to AGI Managed Cloud under your signed-in account. The extension ships no local chat runtime, so this is the only road an answer can take.

  3. Computer use sends the pictures too

    Driving a tab keeps the same gateway and changes the payload: every step posts the whole conversation, including every screenshot the run has taken of your tab, to the Managed Cloud gateway under your account token.

Capabilities

A working surface, not a wrapper.

Everything below is built into the extension, scoped to the pages and tasks you approve.

Panel

Side panel on any page

A persistent Manifest V3 side panel opens beside the tab you are reading. No window juggling, no copy-paste.

Context

Page context on request

Content scripts capture page content when you ask. Capture is an explicit action you take, never something running in the background.

Chat

Answers from Managed Cloud

Press send and the conversation goes to AGI Managed Cloud under your account. The panel holds no provider key and offers no second chat route.

Bridge

Paired Desktop handoff

Native messaging carries a selection, a page capture or a queued message to AGI Desktop on localhost port 8787, with explicit pairing and HMAC-signed messages. It moves context into Desktop rather than answering in the panel.

Computer use

Cloud-executed browser control

Driving a tab requires Managed Cloud sign-in. Each step sends the conversation and the screenshots taken of your tab to the Managed Cloud gateway, so a secret rendered on the page travels with the picture of it.

Permissions

Approved-site permissions

Permission profiles specify the approved sites, allowed actions and any expiry. You can revoke a profile to end the sessions using it.

Automation

Workflow recording

Record a browser flow as element selectors. Field values stay out of the recording by default. Replay it when the task comes back.

Automation

Scheduled tasks

Put recurring browser work on a schedule. Tasks persist in the extension and fire through Chrome's built-in alarms.

Trust boundary

What stays where.

Local, BYOK, and AGI Cloud are separate trust boundaries, and the panel sits in the cloud one: chat leaves for Managed Cloud under your account whatever route you run on Desktop. Computer use goes further still, transmitting the conversation and its screenshots to that gateway on every step, which is why starting a session is always an explicit act. The session gates, the site allowlist, and the residual screenshot risk are written out at /agent-permissions. Those chats mirror to your account until you turn mirroring off in the extension options.

ManifestChrome MV3 with side panel
BridgeOptional native messaging to AGI Desktop · localhost port 8787 · selections, captures and queued messages
PairingExplicit pairing · HMAC-signed messages
Inference in ChromeNone. Chat answers come from AGI Managed Cloud, and computer use calls the Managed Cloud gateway directly from the extension with the screenshots it takes.
Keys in ChromeNone. Chat and computer use run on AGI’s server-side provider keys, not on yours. The current Desktop app also accepts no provider keys.
Computer-use egressThe whole conversation and every screenshot POST to the Managed Cloud gateway under your account token. Screenshots are not redacted and cannot be.
Chat-memory syncManaged Cloud chats mirror to your account by default. Turn mirroring off under Data handling in the extension options and they stay in local extension storage.
Security storyThreat model maintained in the repo (apps/extension/docs/threat-model.md)
StatusChat and computer use scoped to Managed Cloud · the Desktop bridge is an optional local handoff

Coming soon

Put AGI beside the page.

The panel answers from AGI Managed Cloud, and computer use posts the conversation, its screenshots, and any console messages and request records it read to that same gateway. Pair AGI Desktop when you want a local road for selections and captures. AGI managed cloud is in public alpha and open by default on the web: sign in and start, no waitlist. The extension itself is coming soon. Get notified takes you to the form on the download page, where you leave an email to hear when it is ready to install.