Browser extension with per-origin agents

The shape

You want one Chrome extension that adds a Linda agent to every SaaS tool your team uses. A different persona per origin. Same-origin DOM access. No server.

Why an extension instead of a script tag

• Don’t own the page. Script tag requires putting Linda on the site — fine for your own product, impossible for Salesforce.
• User installs. Extension lives in the user’s browser. You distribute the extension; your users add Linda capability to apps they already use.
• Per-origin config. One extension, different configs per host.

Scaffold

packages/extension/
├── manifest.json          # MV3, minimal permissions
├── src/
│   ├── content.ts         # injects Linda into matching origins
│   ├── background.ts      # service worker — handles config + key storage
│   ├── popup.html         # the extension popup
│   └── configs/
│       ├── zendesk.json   # "you are a Zendesk macro assistant"
│       ├── salesforce.json
│       └── hubspot.json
└── public/icons/

The content script is ~50 lines: load Linda, look up the config for location.host, attach.

Patterns

Vertical copilot. Build one extension targeting one vertical (e.g. sales) with configs for the 5 tools that vertical uses. Sell it.

Internal-only. Distribute via your org’s Chrome Enterprise policy. Ship internal admin co-pilots without modifying the SaaS tools you use.

Open source. Ship the scaffold under MIT and let your community write configs.

What you don’t get

• You can’t bypass site auth. The user must be logged in for the agent to see anything. (This is a feature.)
• You can’t read across origins. Extensions can request cross-origin permissions, but Linda doesn’t need them — the content script runs inside the page.

FAQ