Chrome extension

Install Loom.js Companion

Loom.js Companion has passed Chrome Web Store review. Install the approved release directly from the Store—no repository build or Developer mode setup is required.

Install from the Chrome Web Store

Add Loom.js Companion to Chrome

After installation, open the extension options, review the disclosure, and explicitly enable the bridge before connecting the workbench.

Current development ID

foofdcgdelahbdgdfgocoeajdodhjbjo

This unpacked ID can vary with packaging or checkout location. It is separate from the Store ID gdcebopdllcifgleoefgbobdopiaholg. Production uses the Store ID automatically, while the workbench field remains editable for local development.

1. Build the extension

pnpm install --frozen-lockfile
pnpm --filter @mgravey/loom-extension-codex-experimental build

The unpacked package is generated at:

packages/extension-codex-experimental/dist

2. Load it in Chrome

  1. Open chrome://extensions.
  2. Enable Developer mode.
  3. Select Load unpacked.
  4. Choose packages/extension-codex-experimental/dist.
  5. Copy the ID displayed on the extension card.
  6. Open Details → Extension options.
Authentication is disabled by default

Read the disclosure in the options page, explicitly enable the bridge, and then choose browser sign-in or the device-code fallback. Disabling it removes stored authorization.

3. Connect the workbench

pnpm build
python3 -m http.server 4173 --directory packages
  1. Open the browser workbench.
  2. Paste the ID from chrome://extensions if the prefilled value differs.
  3. The workbench checks automatically; select Reconnect if needed.

You may also supply the ID once with ?extensionId=<32-character-id>. The page remembers this non-secret ID in local storage. It never stores a provider credential.

4. Deployment configuration

  1. Production defaults to Store ID gdcebopdllcifgleoefgbobdopiaholg and checks it when the workbench loads.
  2. The approved listing URL is configured as chromeWebStoreUrl so public installation links open the Store.
  3. Confirm the production HTTPS origin and verified legal/support details.
  4. Build the Store ZIP with the production-origin packaging command documented in the extension README.
  5. Retest the installed Store build against the production website before public release.

See the repository’s docs/chrome-web-store-submission.md dossier for the review and packaging record.