by adom

Your AI's hands in your real, signed-in browser. The Adom Browser Extension (abe) works with both Chrome and Edge: build, drive, and test web apps, and log past vendor walls, in the browser you already use - cookies, SSO, saved logins and captcha trust intact. The nbrowser_* bridge (pup's counterpart) runs in your actual logged-in profile.

Overview Files Skills Discover Packages Releases Dependencies Issues1 Breadcrumbs Pull Requests Activity

Download

Submission Checklist — Chrome Web Store + Edge Add-ons

Everything below is prepped in this repo. Items marked (needs John) require your login/payment.

Artifacts (ready)

Package: store/adom-for-chrome-edge-v0.0.14.zip (manifest at root; same zip for both stores)
Privacy policy: PRIVACY.md + hosted privacy.html → URL below
Permission justifications: store/PERMISSION-JUSTIFICATIONS.md (paste per-permission)
Listing copy: store/STORE-LISTING.md (name, summary, description, single purpose)
Icons: 16/48/128 present in extension/icons/

⚠️ The one technical decision: extension ID / the manifest `key`

The manifest currently ships a fixed key so the extension ID is identical in dev (unpacked), self-hosted, and — if we keep it — the store. That ID stability is what keeps the native-messaging host's allowed_origins working (the host pins our exact ID).

Two ways to publish, pick one:

Keep the key → store ID == current ID. allowed_origins needs no change. Simplest; upload the zip as-is. (Recommended.)
Remove the key before upload → the store assigns a new ID. Then we must add that new ID to the native host's allowed_origins (and ship that host update). More moving parts.

→ Recommendation: option 1 — keep the key, one ID everywhere, host registration unchanged.

Chrome Web Store (needs John: $5 one-time account + submit)

Create/sign in to the Chrome Developer Dashboard ($5 one-time registration fee).
Upload store/adom-for-chrome-edge-v0.0.14.zip.
Listing: name/summary/description/category from STORE-LISTING.md; add 1–5 screenshots.
Privacy tab: set the Privacy Policy URL (below); paste each justification from PERMISSION-JUSTIFICATIONS.md; certify data-use (no sale, no ads).
Submit for review. (Expect a review round-trip given debugger + <all_urls> + cookies.)
After approval, force-install org-wide by CWS extension ID via ExtensionInstallForcelist for Adom-managed machines.

Edge Add-ons (needs John: free Partner Center account + submit)

Sign in to Microsoft Partner Center (free), create an Edge Add-ons registration.
Upload the same zip.
Reuse the listing copy, screenshots, justifications, and Privacy Policy URL.
Submit for certification. Publishing here removes the Edge "developer mode" warning for users.

Privacy Policy URL

https://wiki.adom.inc/adom/adom-browser-extension/files/privacy.html

What this fixes

Removes the Chrome and Edge "developer-mode extensions" warnings (signed store install).
One-click install + automatic updates for end users.
Enables silent force-install by store ID on managed fleets.

# Submission Checklist — Chrome Web Store + Edge Add-ons

Everything below is prepped in this repo. Items marked **(needs John)** require your login/payment.

## Artifacts (ready)
- **Package:** `store/adom-for-chrome-edge-v0.0.14.zip` (manifest at root; same zip for both stores)
- **Privacy policy:** `PRIVACY.md` + hosted `privacy.html` → URL below
- **Permission justifications:** `store/PERMISSION-JUSTIFICATIONS.md` (paste per-permission)
- **Listing copy:** `store/STORE-LISTING.md` (name, summary, description, single purpose)
- **Icons:** 16/48/128 present in `extension/icons/`

## ⚠️ The one technical decision: extension ID / the manifest `key`
The manifest currently ships a fixed **`key`** so the extension ID is **identical** in dev
(unpacked), self-hosted, and — if we keep it — the store. That ID stability is what keeps the
**native-messaging host's `allowed_origins` working** (the host pins our exact ID).

Two ways to publish, pick one:
1. **Keep the `key`** → store ID == current ID. `allowed_origins` needs **no change**. Simplest;
   upload the zip as-is. (Recommended.)
2. **Remove the `key`** before upload → the store assigns a **new** ID. Then we must add that new
   ID to the native host's `allowed_origins` (and ship that host update). More moving parts.

→ **Recommendation: option 1** — keep the key, one ID everywhere, host registration unchanged.

## Chrome Web Store (needs John: $5 one-time account + submit)
1. Create/sign in to the Chrome Developer Dashboard ($5 one-time registration fee).
2. Upload `store/adom-for-chrome-edge-v0.0.14.zip`.
3. Listing: name/summary/description/category from `STORE-LISTING.md`; add 1–5 screenshots.
4. Privacy tab: set the Privacy Policy URL (below); paste each justification from
   `PERMISSION-JUSTIFICATIONS.md`; certify data-use (no sale, no ads).
5. Submit for review. (Expect a review round-trip given `debugger` + `<all_urls>` + `cookies`.)
6. After approval, force-install org-wide by **CWS extension ID** via
   `ExtensionInstallForcelist` for Adom-managed machines.

## Edge Add-ons (needs John: free Partner Center account + submit)
1. Sign in to Microsoft Partner Center (free), create an Edge Add-ons registration.
2. Upload the **same** zip.
3. Reuse the listing copy, screenshots, justifications, and Privacy Policy URL.
4. Submit for certification. Publishing here removes the Edge "developer mode" warning for users.

## Privacy Policy URL
`https://wiki.adom.inc/adom/adom-browser-extension/files/privacy.html`

## What this fixes
- Removes the Chrome **and** Edge "developer-mode extensions" warnings (signed store install).
- One-click install + automatic updates for end users.
- Enables silent force-install by store ID on managed fleets.

Adom Browser Extension