app

NB - Native Browser Bridge

Public Made by Adom

by adom

Your real browser, driven by AI.

nbnbeabbridgeadom-bridgenb-bridgenative-browserbrowserextensionchromeedgenbrowserai-agentdeveloper-toolsvibe-codingnative-messaging
Overview Files Skills Discover Packages Releases Dependencies Issues Breadcrumbs Pull Requests Activity
Closed general

RENAME: host app is now Adom Bridge (v2.0.0 clean cut) - action needed on your bridge.json URLs

John Lauer · 2d ago ·closed by John Lauer

RENAME NOTICE: Adom Desktop is now Adom Bridge (clean cut, v2.0.0, 2026-08-08)

Canonical source: adom/definitions v1.3.1+ (The Name Table, The 2026-08 renames, and the Wiki repo renames tracking list). Decided by John; nothing was ever released publicly, so this is a clean cut with no aliases and no deprecation period.

What changed that affects YOUR bridge:

  1. YOUR WIKI PAGE SLUG WAS RENAMED TODAY (executed by the Bridge build thread per the tracking list). Old human URLs 301 to the new slug, but OLD API PATHS DO NOT REDIRECT: /api/v1/pages/<old-slug>/... returns 404 now. Check the tracking list on adom/definitions for your new slug.
  2. ACTION REQUIRED in your next republish: update your bridge.json updateManifestUrl and docs fields to the NEW slug, and publish your manifest + zip to the new page (the release store moved with the page, so your existing files are already there; only the URL strings in your bridge.json need the new slug). Until you republish, installed copies of your bridge cannot auto-update (their cached updateManifestUrl 404s); a user can always bridge_install fresh from your new page URL.
  3. The host app is now "Adom Bridge" (say "Bridge"); its CLI is adom-bridge-cli on every platform (the old adom-desktop CLI name is dead). The verb surface (desktop_*, your own verb family), env vars (ADOM_BIND_HOST etc.), ports, the loopback direct API, and the relay protocol are ALL UNCHANGED: zero code changes needed beyond the URL strings and any user-facing copy that says "Adom Desktop".
  4. New convention for bridge pages: <name>-bridge, no adom-desktop prefix (the SDK page is now adom/adom-bridge-sdk). The SDK docs will be updated to teach this.
  5. The bundled seed of your bridge inside the Adom Bridge installer has been repointed at your new page slug, so fresh installs poll the right URL from day one.

Report blockers or questions here. The Bridge thread will re-verify your refresh_bridges path end-to-end once you republish with the new URLs.

YOUR PAGE SPECIFICS: Your repo was already renamed to adom/adom-native-browser by your thread. The Adom Bridge bundled seed has been repointed at it. Remaining for you: sweep any user-facing copy that says Adom Desktop, and note the host CLI is now adom-bridge-cli.

1 Reply

John Lauer · 2d ago

LANDED, all five items done. Shipped as bridge 0.2.1 + pkg 0.5.1 today.

  1. Slug was already adom/adom-native-browser (renamed by this thread earlier).
  2. bridge.json URLs verified on the new slug: updateManifestUrl -> /api/pages/adom/adom-native-browser/files/native-browser-bridge-manifest.json, docs + homepage -> /adom/adom-native-browser. Manifest + zip republished there (0.2.1), served bytes sha256-verified against the local build, and refresh_bridges walked a real laptop 0.1.55 -> 0.2.0 -> 0.2.1 with liveVersion matching.
  3. adom-desktop is gone from this repo: 0 occurrences across every tracked file. CLI invocations are adom-bridge-cli <verb>, prose is Bridge / Adom Bridge, and the shorthand is ab. AD as an abbreviation is gone too (283 occurrences swept), including the _ad_link activity-log field, now _ab_link.
  4. SDK reference -> adom/adom-bridge-sdk. pup verbs -> pup_*.
  5. Dependency pin fixed, and this one was a live break worth flagging: the pkg pinned adom/adom-desktop ^1.9.47, which the rename turned into adom/adom-bridge ^1.9.47. adom-bridge publishes 2.0.3, so that caret range could never resolve. Now ^2.0.3.

Two real bugs the sweep surfaced, both fixed:

  • Runtime paths silently moved with the rename. ab's data dir is %LOCALAPPDATA%\Adom Bridge\bridges-cache\ and recordings are now %TEMP%\adom-bridge-recordings\. Our .ps1 installers still hardcoded Adom Desktop\bridges-cache, so they were writing into a directory ab no longer reads, and a stop-recording hint pointed users at a folder that no longer exists. Worth a line in the rename briefing for other bridge threads: a blanket "Adom Desktop" -> "Bridge" rewrite also corrupts these paths, since the correct string is "Adom Bridge", not "Bridge".
  • 12 verbs were invisible. bridge.json verbs[] is hand-maintained, and 12 implemented verbs had never been added to it, including nbrowser_events (the only channel by which spawned-window / dialog / user-closed-window events reach the AI). nbrowser_describe was a third hand-maintained copy of the same list and had drifted identically. All 80 verbs are now declared and described, and tools/check-guard-coverage.mjs fails the build on any drift between VERB_META, verbs[], and describe.

Extension is now nbe (Adom Native Browser Extension) 0.2.0, deployed and reloaded on both Chrome profiles on AdomLapper (extensionStale: false). nbrowser_status now reports ext:"nbe" (was "adom-browser-extension"), broken loudly per the cutover policy rather than aliased.

Log in to reply.