Browser extension — Firefox (self-host)
Build the OpenQuok extension for Firefox, load it as a temporary add-on, and set the Firefox extension ID on the web app.
Connect your agent today
Draft from chat, review in your calendar, and publish only what you approve.
Overview
Firefox uses a separate build (extension/dist-firefox/). The UI opens in the sidebar (not Chromium’s side panel). The dashboard talks to the extension through a page postMessage bridge on OpenQuok hosts — Firefox does not use externally_connectable.
Gecko add-on id defaults to [email protected] in extension/manifest.firefox.json. After AMO publish, add firefox:<add-on-id> to VITE_OPENQUOK_BROWSER_EXTENSION_IDS when the listing id differs.
Install from Firefox Add-ons (AMO)
After review, users install from addons.mozilla.org. Set production env and redeploy web:
VITE_OPENQUOK_BROWSER_EXTENSION_IDS=chromium:chrome-id,edge:edge-id,firefox:[email protected] Use the ID AMO shows if it differs from [email protected].
Temporary add-on (self-host dev)
Firefox does not keep a permanent “load unpacked” install like Chrome. For local testing, load a temporary add-on each session (or after every browser restart).
Build the Firefox package
pnpm common:build
pnpm --filter @openquok/browser-extension build:firefox Output is in extension/dist-firefox/.
Load in Firefox
- In the address bar, open about:debugging and press Enter.
- In the left sidebar, click This Firefox (not Setup). Setup only shows USB/network debug options — it does not load extensions.
- On the This Firefox page, click Load Temporary Add-on… (near the top of the main panel).
- In the file picker, choose extension/dist-firefox/manifest.json from your monorepo clone.
Note
Shortcut: open about:debugging#/runtime/this-firefox to land on This Firefox directly.
After you rebuild, click Reload on the add-on row in about:debugging. Quitting Firefox removes the temporary add-on — load it again on the next session.
Wire the web app
The dashboard resolves extension messaging through the dashboard content script bridge on your OpenQuok origin. For production multi-browser maps, include Firefox:
# VITE_OPENQUOK_BROWSER_EXTENSION_IDS=chromium:…,edge:…,firefox:[email protected] Restart the web dev server when env changes. Sign in on your dashboard in the same Firefox profile as the add-on, then open the OpenQuok sidebar.
Use the sidebar
Click the OpenQuok toolbar icon (or open from the context menu on Schedule with OpenQuok). Social and Directory match the Chromium feature set with sidebar UI.
Optional AMO zip
pnpm --filter @openquok/browser-extension zip:firefox Writes extension/openquok-browser-extension-firefox.zip for Mozilla submission.
Self-host dashboard origin
Ensure your dashboard HTTPS origin is covered by host_permissions and the dashboard content_scripts matches in extension/manifest.json (merged with manifest.firefox.json on Firefox builds). Rebuild dist-firefox/ after manifest edits.
Directory launch handoff from the web app must reach the extension via the page runtime bridge — verify on Firefox after any bridge or manifest change.