Chrome side panel
The conversation and activity stay beside the page you are working on.
Technology
How direct integrations and browser actions work together
Use a direct integration when the task supports it. Work in the browser when you need the interface.
Task and tool selection
Released operations are matched using explicit tool descriptions and task rules.
Connector or browser action
Use structured service operations when supported, or work through the visible interface.
Permission checks
Scopes and per-operation settings define what can run and what must ask.
Account-linked history
Conversation text can sync to the verified internal account.
Choose the right approach for the task.
| Consideration | Chat-only | Visual browser automation | Combined approach |
|---|---|---|---|
| Supported actions | Produces guidance and content | Interacts through visible pages | Uses released direct operations or the page |
| UI layout dependency | None for generation | Higher | Lower for direct operations; higher for browser tasks |
| Structured service data | Only when supplied | Limited to visible page state | Available for released connector operations |
| Setup | AI provider access | Browser and site access | AI key plus chosen connector permissions |
| Failure modes | Missing context | Changed layouts or page state | Scopes, rate limits, API coverage, or page state |
Technical explanationManifest V3, sessions, credentials and sync
The extension uses a Manifest V3 side panel and background service worker. Tools have explicit machine-readable schemas.
Supported Drive, Calendar and ClickUp credentials are encrypted on the backend and used only for server-side service calls. Gmail currently follows its separate connector design.
Server-side sessions bind connector records and conversation sync to the verified internal account. Encryption at rest is not end-to-end encryption.
Ready to see how it works?
Watch demoThe Chrome Store listing and checkout are not public yet. Watch the product preview first.