# Chrome extensions and Manifest V3

Connect's Chrome extension, the Connect Marketplace Assistant, is built on Chrome's Manifest V3. It fills a marketplace listing form, or shows a prepared ad campaign's fields, from the business's approved products. The owner then reviews and submits it. It pairs with a one-time code, holds only a revocable device token, asks for one platform's sites at a time, and never presses Submit, Publish or Pay.

- **Status:** Reference
- **Audience:** both, developer
- **Last verified:** 2026-11-02
- **Canonical:** https://connectbyjbrh.com/docs/technology/chrome-extension-mv3/

## What it is

Manifest V3 is the current Chrome extension platform. It replaced persistent background pages with service workers that start on demand, forbids remotely hosted code, and narrows how extensions observe network requests.

The assistant uses `storage`, `activeTab` and `scripting`. It has one fixed host permission, Connect's own site, and 80 optional host patterns: supported marketplaces, the Google and Meta ad managers, and, since 1.1.0, the Google and Microsoft admin consoles and the carrier consoles used in assisted business setup. Chrome asks the owner for one platform's sites at a time, when the owner presses for it.

**Category** — Browser extension platform
**Extension** — Connect Marketplace Assistant 1.1.0
**Manifest** — `manifest_version: 3`; service worker `background.js`; popup `popup.html`
**Official site** — [developer.chrome.com/docs/extensions](https://developer.chrome.com/docs/extensions/develop/migrate/what-is-mv3)

## Where Connect uses it

| Place in Connect | What it does there |
|---|---|
| `extensions/chrome-marketplace-assistant/` | The extension: manifest, service worker, popup and the fill adapter `content.js` |
| Marketplace Autopilot and Google & Meta Ads | Prepare the browser tasks the extension lists |
| `/api/assistant-extension/*` | The extension's own door, called with its device token and no cookies |
| `tools/chrome_assistant_build.py` | Generates the optional hosts from the platform registry and checks the manifest |

## How it connects

1. The owner gets a pairing code in Connect (eight characters, ten minutes, single use)
2. The extension exchanges it for a device token, which Connect stores only as a hash
3. The owner opens a task's platform site and presses Fill This Page
4. Empty fields are filled and outlined for review; password, file and hidden fields are never touched
5. The owner submits on the platform, and the extension reports what they chose

## Benefits and limits

What it gives Connect:

- The owner stays in control: it prepares, a person submits.
- Narrow access: one site of Connect's plus the platforms the owner grants, one at a time.
- Revocable: removing the person or pressing Revoke stops the browser at its next request.

Where it stops, and what Connect does about it:

- It cannot solve a CAPTCHA, sign in for the owner, or act on a site the owner did not open.
- Platform forms change, so the fill adapter needs upkeep. It is tested on local fixture forms.
- Deploying Connect does not publish the extension. Store publishing is the owner's step, and until then it loads unpacked.

## Security and privacy

- No Connect or platform password, cookie or session is ever read, stored or sent. Requests use `credentials: 'omit'` and a Bearer device token.
- Every request re-checks that the person still belongs to the workspace and may operate the business.
- No `<all_urls>`, no history, tabs, cookies or web-request permissions, and no remote code.

## Licence, cost and versions

| Question | Answer |
|---|---|
| Licence | Connect's own code. Chrome's extension platform is free to use |
| Cost | Publishing needs a Chrome Web Store developer account, which has a one-time registration fee |
| Version | 1.1.0 in the manifest |
| Compatibility | Chrome and Chromium browsers with Manifest V3 |

## Troubleshooting

**Pairing fails** — The code expired (ten minutes) or was used once already. Get a new one.
**Fill This Page does nothing** — Chrome has not granted that platform's site yet. Press the button again and allow it.
**The extension stopped working for one person** — Their access was revoked, or they left the workspace. That is intended.

## Official references

- [What is Manifest V3](https://developer.chrome.com/docs/extensions/develop/migrate/what-is-mv3)
- [Optional permissions](https://developer.chrome.com/docs/extensions/reference/api/permissions)
- [Extension service workers](https://developer.chrome.com/docs/extensions/develop/concepts/service-workers)

## Questions

### Can the extension read all my browsing?

No. It has no all-sites permission. It reaches Connect's site and only the marketplace sites you grant, one platform at a time, and acts only when you press Fill This Page.

### Will it submit or pay on my behalf?

No. It fills empty fields for you to review. Submit, Publish and Pay are always your own press on the platform.

## Related

- [OAuth 2.0](https://connectbyjbrh.com/docs/technology/oauth/)
- [Agent security](https://connectbyjbrh.com/docs/technology/agent-security/)
- [The no-build browser frontend](https://connectbyjbrh.com/docs/technology/browser-modules/)
- [Human in the loop](https://connectbyjbrh.com/docs/technology/human-in-the-loop/)

## What this page is based on

- `extensions/chrome-marketplace-assistant/manifest.json`
- `extensions/chrome-marketplace-assistant/README.md`
- `extensions/chrome-marketplace-assistant/background.js`
