Skip to content

Browser extension — Edge (self-host)

Build the OpenQuok extension for Microsoft Edge, load it from your clone, and set the Edge extension ID on the web app.

2 min read

Connect your agent today

Draft from chat, review in your calendar, and publish only what you approve.

Start your free trial

Overview

Microsoft Edge ships the same Chromium MV3 package as Chrome (extension/dist/ and openquok-browser-extension.zip). Edge assigns a different extension ID (CRX ID) than Chrome after you publish to Edge Add-ons. Add edge:<crx-id> to VITE_OPENQUOK_BROWSER_EXTENSION_IDS on the web app so the dashboard can ping the Edge install.

Install from Edge Add-ons

After your listing is public, users install from the Microsoft Edge Add-ons store. Copy the CRX ID from edge://extensions → extension Details and set production env:

VITE_OPENQUOK_BROWSER_EXTENSION_IDS=chromium:YOUR_CHROME_WEB_STORE_ID,edge:YOUR_EDGE_CRX_ID

Redeploy the web app after you change extension IDs.

Load unpacked (self-host)

Build the package

pnpm common:build
pnpm --filter @openquok/browser-extension build

Output is in extension/dist/.

Load in Edge

Open edge://extensions, turn on Developer mode, click Load unpacked, and select extension/dist/. The folder must contain manifest.json at its root.

Wire the web app

Use the unpacked ID for local testing, or the store CRX ID for production:

VITE_OPENQUOK_BROWSER_EXTENSION_ID=edge-unpacked-id-for-local-dev

# Production (example shape — use your real IDs)
# VITE_OPENQUOK_BROWSER_EXTENSION_IDS=chromium:chrome-store-id,edge:edge-crx-id

Keep a signed-in dashboard tab in the same Edge profile as the extension. On https://localhost:5173, use self-host sign-in in the side panel and tap Refresh.

Open the side panel

Pin OpenQuok on the toolbar. Social and Directory tabs behave the same as on Chrome. Context menu items Schedule with OpenQuok and Humanize selection with OpenQuok work on any page.

Optional store zip

pnpm --filter @openquok/browser-extension zip

Upload extension/openquok-browser-extension.zip to Partner Center (same file as Chrome Web Store).

Self-host dashboard origin

Same as Chromium: update externally_connectable.matches in extension/manifest.json for custom dashboard HTTPS origins, then rebuild and redistribute.

Search documentation
Find a docs page
Discord Support