NB - Native Browser Bridge

@@ -462,11 +462,11 @@ async function wgcRecord(verb, args) {     return {       success: false,       error: 'ab is too old for native window recording',-      _hint: 'desktop_record_window_* shipped in Bridge - upgrade ab (adom-bridge-cli --version must be >= 1.8.148; older builds mis-route to the puppeteer bridge). Meanwhile use method:"getdisplaymedia" or the "Record this tab" toolbar button.',+      _hint: 'desktop_record_window_* shipped in Bridge - upgrade ab (adom-bridge --version must be >= 1.8.148; older builds mis-route to the puppeteer bridge). Meanwhile use method:"getdisplaymedia" or the "Record this tab" toolbar button.',     };   }   if (r.status >= 200 && r.status < 300 && out && out.success !== false && !out.error) {-    const stopHint = 'mp4 is on the laptop at out.path (under %TEMP%\\adom-bridge-recordings) - fetch it with: adom-bridge-cli pull_file {"filePaths":["<path>"]}';+    const stopHint = 'mp4 is on the laptop at out.path (under %TEMP%\\adom-bridge-recordings) - fetch it with: adom-bridge pull_file {"filePaths":["<path>"]}';     const startHint = 'recording started in the BACKGROUND - the user keeps working; do NOT foreground the window (foregrounding is the user\'s choice, never the AI\'s). ⚠️ If frames come out BLANK, the recorded Chrome was NOT launched with the occlusion-disable flags (--disable-backgrounding-occluded-windows --disable-renderer-backgrounding --disable-background-timer-throttling --disable-features=CalculateNativeWinOcclusion) - Chrome stops painting an occluded window without them. pup\'s Chrome already has these (so it background-records fine); a default user Chrome must be relaunched with them. Poll nbrowser_record_status {method:"wgc",recordingId}; stop with nbrowser_record_stop {method:"wgc",recordingId}.';     return { success: true, output: JSON.stringify({       ok: true, method: 'wgc',@@ -1248,7 +1248,7 @@ function _hostManifestPaths() { const OWN_ONLY = 'ONLY operate on a window/tab YOU opened via nbrowser_open_window. NEVER navigate/reload/close a window or tab the user already had open - the bridge drives their REAL browser, so you would destroy their live page, forms, sessions, or other AI threads.'; // The politeness mandate, repeated verbatim on every focus-relevant verb. The bridge ENFORCES it in code // (background-by-default + focus-steal auto-revert + focus_violation events); this hint tells the AI why.-const NO_FG = 'Open in the BACKGROUND — users automating the browser almost always have OTHER things in the foreground, and a raised window STEALS their keyboard focus (it has typed a user\'s own keystrokes into a username field and dismissed Chrome\'s password dropdown mid-task). Background is where automation SUCCEEDS. NEVER fall back to OS-level launches (Start-Process/launch/msedge/chrome --new-window) or bring_to_front/maximize to surface a window. To genuinely foreground (some auth pages / browser features need it) you must do real work: (1) FIRST warn the user with a Bridge notify (adom-bridge-cli notify_user {message:"Adom is about to bring a browser window forward for <reason>"}), then (2) pass userRequestedForeground:true AND foregroundReason:"<why>". A bare userRequestedForeground with no foregroundReason STAYS background; any driven window that lands topmost is auto-reverted + logged (focus_violation / foreground_raised).';+const NO_FG = 'Open in the BACKGROUND — users automating the browser almost always have OTHER things in the foreground, and a raised window STEALS their keyboard focus (it has typed a user\'s own keystrokes into a username field and dismissed Chrome\'s password dropdown mid-task). Background is where automation SUCCEEDS. NEVER fall back to OS-level launches (Start-Process/launch/msedge/chrome --new-window) or bring_to_front/maximize to surface a window. To genuinely foreground (some auth pages / browser features need it) you must do real work: (1) FIRST warn the user with a Bridge notify (adom-bridge notify_user {message:"Adom is about to bring a browser window forward for <reason>"}), then (2) pass userRequestedForeground:true AND foregroundReason:"<why>". A bare userRequestedForeground with no foregroundReason STAYS background; any driven window that lands topmost is auto-reverted + logged (focus_violation / foreground_raised).'; const VERB_META = {   nbrowser_status: { hint: 'Connectivity check: connected profiles + active browser. Call this first if any verb errors "not connected".', related: ['nbrowser_profiles', 'nbrowser_ping', 'nbrowser_open_window'], pitfalls: ['a profile\'s extension SLEEPS when that profile has no open windows - it then shows disconnected; open a window to wake it'] },   nbrowser_readiness: { hint: 'READ-ONLY cold-start probe: is the native-browser extension connected + ready to drive? NEVER spawns work or installs anything. state:"ready" = drive now; state:"needs-extension" = offer to install it (Level-2, see installing-the-extension) or it is asleep (open a window in that profile). Also reports chromeInstalled: if false, the user has no native Chrome and you can offer nbrowser_install_chrome.', related: ['nbrowser_status', 'nbrowser_open_window', 'nbrowser_install_chrome'], pitfalls: ['"needs-extension" can mean not-installed OR installed-but-asleep - nbrowser_status\'s tooltip distinguishes', 'this verb never installs; to install, run the installing-the-extension flow', 'for a machine-wide "what do I have" answer prefer ab\'s bridge_readiness (aggregates all bridges, spawns none)'] },@@ -1311,13 +1311,14 @@ const VERB_META = {   nbrowser_record_start: { hint: RECORD_WGC_HINT, related: ['nbrowser_record_stop', 'nbrowser_record_status'], next: 'nbrowser_record_status', pitfalls: ['⭐ prefer method:"wgc" (delegates to core desktop_record_window_start)', 'getdisplaymedia/tabcapture are REFUSED without fallbackConfirmed:true - a browser extension cannot silently screen-record'] },   nbrowser_record_stop: { hint: 'Stop a recording and finalize the mp4 (pull it with pull_file).', related: ['nbrowser_record_status'], pitfalls: ['needs the recordingId from record_start, not a sessionId'] },   nbrowser_record_status: { hint: 'Poll a recording.', related: ['nbrowser_record_start'], pitfalls: ['pass the SAME method (wgc|getdisplaymedia|tabcapture) + recordingId you started with', 'blank frames on a WGC recording = the recorded Chrome lacks the occlusion-disable launch flags'] },-  nbrowser_record_list: { hint: 'List recent recordings.', related: ['nbrowser_record_status'], pitfalls: ['paths are on the LAPTOP - pull them with adom-bridge-cli pull_file, do not expect them in the container'] },+  nbrowser_record_list: { hint: 'List recent recordings.', related: ['nbrowser_record_status'], pitfalls: ['paths are on the LAPTOP - pull them with adom-bridge pull_file, do not expect them in the container'] },   nbrowser_flash: { hint: 'Flash the driven window\'s taskbar button - the "come look" cue (e.g. at a captcha/2FA/login human-gate).', related: ['nbrowser_flash_stop', 'nbrowser_flash_mode'], pitfalls: ['auto-clears on focus; nbrowser_flash_stop to clear early'] },   nbrowser_flash_stop: { hint: 'Stop the taskbar flash.', related: ['nbrowser_flash'], pitfalls: ['the flash already auto-clears when the user focuses the window - only stop it early if you no longer need their attention'] },   nbrowser_flash_mode: { hint: 'Set auto-flash verbosity: quiet (come-look moments: page load, screenshot, error/refusal, human-gate, spawned window) | chatty (every action) | off (no auto-flash at all). Flash manually with nbrowser_flash at task-done.', related: ['nbrowser_flash'], pitfalls: ['off is the user opt-out - if the user says the orange flashing is annoying, set flash_mode:"off" and it stops entirely', 'quiet is the default; the flash is a "come look" cue, so keep it for human-gates even if you dial the rest down'] },   nbrowser_taskbar: { hint: 'Paint progress/overlay/flash on the window taskbar button (e.g. paused=yellow for a human gate). The "Adom is driving" badge is AUTOMATIC: the bridge composites the profile\'s circle avatar + the Adom favicon at open/drive, and idle-expires it (~3 min) back to the plain native avatar - you rarely need to touch overlay yourself.', related: ['nbrowser_flash'], pitfalls: ['clear progress+flash at task end: {progress:{state:"none"},flash:"stop"} - the badge clears itself (idle-expiry / close)', 'overlay.badge:"none" RESTORES the native avatar look (the bridge never blanks the overlay slot - blanking would erase the user\'s profile avatar)'] },   nbrowser_describe: { hint: 'Returns per-verb schemas + hint/related/pitfalls for ab\'s Verbs tab.', related: ['nbrowser_help'], pitfalls: ['this is the catalog - a few extension-only verbs (e.g. nbrowser_login_form) are real but resolved in the extension, not listed here'] },   nbrowser_handle_dialog: { hint: 'Press OK/Cancel (or answer a prompt) on a native JS dialog (alert/confirm/prompt/beforeunload) BLOCKING the page. accept:true=OK/Yes/Leave · accept:false=Cancel/Stay · text:"…" answers a prompt.', related: ['nbrowser_screenshot', 'nbrowser_click'], next: 'nbrowser_screenshot', pitfalls: ['these dialogs are NOT in a screenshot and have NO hwnd (Chrome renders them) - you learn of them via a modal_open error or a screenshot _modal note', 'the page is FROZEN until you handle it: clicks/typing/eval return modal_open until you do', 'if the AI "keeps failing to fill a form", suspect an open dialog - handle it, then re-screenshot'] },+  nbrowser_uninstall: { hint: 'CASCADE HOOK, not for normal use: ab calls this itself during bridge_uninstall (ab 2.0.35+) with {cascade:true} BEFORE deleting the bridge cache, so nb can remove artifacts that live outside it - above all the HKCU native-messaging host registration, which would otherwise leave every profile dialing a deleted binary forever ("Native host has exited"). Also clears ~/.adom/bridges/native-browser, the activity trail, and the icon cache.', related: ['nbrowser_readiness'], pitfalls: ['you almost never call this directly - run ab\'s bridge_uninstall and let it cascade', 'it deliberately does NOT remove the nbe extension from the user\'s browser (their profile, their choice) - it only stops working; use uninstalling-the-extension to remove it properly', 'best-effort by contract: a failure here still lets ab delete the cache, so check removed[]/failed[] rather than assuming'] },   nbrowser_dev_reload: { hint: 'MAINTAINER-only: reload the extension to pick up on-disk code changes (2-pass, reconnects in ~10s).', related: ['nbrowser_status'], pitfalls: ['throttled to 1/90s (a reload restarts the SW + native host)', 'not for normal driving - only after editing the extension source', 'reloads ONE profile; other profiles pick up the new code on their own next reload'] },   nbrowser_clear_cookies: { hint: 'Background logout: drop a site\'s cookies (incl. httpOnly) for ONE registrable domain, leaving other sites (e.g. Google SSO) intact.', related: ['nbrowser_login_state'], pitfalls: ['scoped to one domain so it never nukes unrelated sessions', '⚠️ do NOT use this to log OUT of a site that ties device-trust to cookies (e.g. Gusto) - it forces a fresh 2FA; use the site\'s own Sign out'] },   nbrowser_caption: { hint: 'Paint an on-page caption (subtitle or red alert banner) for demos/narration.', related: ['nbrowser_cursor'], pitfalls: ['only on a window you opened', 'pass action:"hide" or empty text to dismiss'] },@@ -1556,6 +1557,7 @@ function dispatch(verb, args) {         d('nbrowser_clear_cookies', 'Background logout: drop one registrable domain\'s cookies (incl. httpOnly), leaving other sites (e.g. Google SSO) intact.', { host: 'required str (e.g. "gusto.com"; url/domain also accepted)' }, { ok: 'bool', removed: 'int', hosts: '[str]' }, 30, { example: { host: 'gusto.com' } }),         d('nbrowser_caption', 'Paint an on-page caption (subtitle, or red alert banner) for demos and narration.', { sessionId: S, text: 'required str (or action:"hide")', style: 'optional "subtitle"(default)|"alert"', position: 'optional str', fontSize: 'optional int', pulse: 'optional bool', durationMs: 'optional int (default 5000)', action: 'optional "hide"' }, { ok: 'bool', tabId: 'str', style: 'str' }, 20, { example: { sessionId: 's1', text: 'Signing in to DigiKey' } }),         d('nbrowser_cursor', 'Show or move the gliding Adom cursor with an intent label (demo narration). Visual only, it does not click.', { sessionId: S, action: 'optional "move"(default)|"hide"', x: 'optional int', y: 'optional int', label: 'optional str (or intent)' }, { ok: 'bool', tabId: 'str', action: 'str', label: 'str' }, 20, { example: { sessionId: 's1', x: 400, y: 300, label: 'Clicking Sign in' } }),+        d('nbrowser_uninstall', 'CASCADE HOOK (ab 2.0.35+): ab calls this during bridge_uninstall, before deleting the cache, so nb removes its own out-of-cache artifacts (HKCU native-messaging host for Chrome + Edge, ~/.adom/bridges/native-browser, activity trail, icon cache). Never removes the extension from the user\'s browser.', { cascade: 'bool (set by ab)', name: 'str (set by ab)' }, { ok: 'bool', removed: '[str]', failed: '[str]', extensionStillInstalled: '[str]' }, 30, { example: { cascade: true, name: 'native-browser' } }),         d('nbrowser_dev_reload', 'MAINTAINER-only: reload the extension to pick up on-disk code changes (2-pass, reconnects in ~10s). Throttled to 1 per 90s.', { profile: P }, { ok: 'bool', reloaded: 'bool', throttled: 'bool?' }, 30, { example: { profile: 'chrome:[email protected]' } }),         d('nbrowser_describe', 'This verb: returns per-verb schemas for the ab Verbs tab.', {}, { success: 'bool', verbs: '[{name,summary,input,output,timeoutSeconds,statusVerb,longRunning,example}]' }, 15, { example: {} }),       ];@@ -1817,6 +1819,38 @@ function dispatch(verb, args) {       })();       return;     }+    // nbrowser_uninstall - the CASCADE hook (ab 2.0.35+). ab calls this BEFORE deleting our cache dir,+    // with {cascade:true,name}, so we can remove artifacts that live OUTSIDE that dir while our files+    // still exist. THE ONE THAT MATTERS: the HKCU native-messaging host registrations. Chrome/Edge keep+    // pointing at native-host.bat forever; once the cache is gone that path is dead and every profile+    // with the extension gets "Native host has exited" with no way to diagnose it. We own that key, so+    // we clean it. We deliberately do NOT remove the extension from the user's browser: that lives in+    // THEIR profile and is THEIR choice (uninstalling-the-extension walks them through it if they want).+    if (verb === 'nbrowser_uninstall') {+      (async () => {+        const removed = [], failed = [];+        const HOST = 'inc.adom.native_browser';+        for (const vendor of ['Google\\Chrome', 'Microsoft\\Edge']) {+          const key = `HKCU\\Software\\${vendor}\\NativeMessagingHosts\\${HOST}`;+          try {+            const r = await abCommand(null, 'registry_delete', { path: key, reason: 'nb bridge uninstall cascade: removing our own native-messaging host registration so the browser stops dialing a deleted binary' });+            (r && r.success !== false ? removed : failed).push(key);+          } catch { failed.push(key); }+        }+        for (const p of [path.join(os.homedir(), '.adom', 'bridges', BRIDGE), ACT_FILE, ICON_DIR]) {+          try { fs.rmSync(p, { recursive: true, force: true }); removed.push(p); } catch { failed.push(p); }+        }+        const stillInstalled = knownProfiles().filter((kp) => (adomExtStateForProfile(kp.browser, kp.profileDir) || {}).installed).map((kp) => kp.key);+        resolve({ success: true, output: JSON.stringify({+          ok: true, cascade: !!(a && a.cascade), removed, failed,+          extensionStillInstalled: stillInstalled,+          _hint: `Cleaned nb's OWN artifacts: the HKCU native-messaging host registration (Chrome + Edge), ~/.adom/bridges/${BRIDGE}, the activity trail, and the icon cache. ab removes the bridge cache dir next.` ++            (stillInstalled.length+              ? ` NOT REMOVED (deliberately): the nbe extension is still loaded in ${stillInstalled.join(', ')} - it lives in the USER'S browser profile and is their choice. It will simply stop working (its native host is gone). To remove it properly walk them through the uninstalling-the-extension skill; never rip an extension out from under a user.`+              : ` No profile currently has the nbe extension installed, so nothing is left in the user's browser.`) }) });+      })();+      return;+    }     if (verb === 'nbrowser_os_windows') {       (async () => {         let ws = []; let abOk = true;@@ -2072,7 +2106,7 @@ function dispatch(verb, args) {         }         if (Array.isArray(args.filePaths) && args.filePaths.length && args.chooserStatus !== true) { // both real modes read the files at serve time; a status probe needs no files           const missing = (args.filePaths || []).filter((fp) => { try { return !fs.existsSync(fp); } catch { return true; } });-          if (missing.length) return resolve({ success: false, errorCode: 'file_missing', error: `file_missing: ${missing.join(', ')} not found on the laptop`, _hint: 'Paths must be ABSOLUTE paths on the machine running the browser. Push files there first with adom-bridge-cli send_files, or pass files:[{name, contentBase64}] and the bridge stages them for you.' });+          if (missing.length) return resolve({ success: false, errorCode: 'file_missing', error: `file_missing: ${missing.join(', ')} not found on the laptop`, _hint: 'Paths must be ABSOLUTE paths on the machine running the browser. Push files there first with adom-bridge send_files, or pass files:[{name, contentBase64}] and the bridge stages them for you.' });         }       } catch (e) { return resolve({ success: false, error: 'upload staging failed: ' + ((e && e.message) || e) }); }     }@@ -2154,7 +2188,7 @@ async function onHostFrameInner(frame) {       let payload = frame.payload || {};       // Screenshot file-save: huge base64 over the relay times out, so when the caller passes       // toFile:true we write the PNG to a laptop temp file here and return its path instead of the-      // base64. Pull it with `adom-bridge-cli pull_file` (binary chunked) - fast + no relay timeout.+      // base64. Pull it with `adom-bridge pull_file` (binary chunked) - fast + no relay timeout.       const isShot = /screenshot/.test(p.verb);       const isRec = p.verb === 'nbrowser_record_stop';       if (payload.base64 && ((isShot && p.toFile) || isRec)) {@@ -2165,7 +2199,7 @@ async function onHostFrameInner(frame) {           const file = path.join(dir, `${isRec ? 'rec' : 'shot'}-${Date.now()}.${isRec ? 'webm' : 'png'}`);           fs.writeFileSync(file, Buffer.from(payload.base64, 'base64'));           const sizeKB = Math.round(Buffer.byteLength(payload.base64, 'base64') / 1024);-          payload = { ...payload, path: file, savedToFile: true, sizeKB, _hint: 'Pull this with `adom-bridge-cli pull_file {filePaths:["' + file.replace(/\\/g, '\\\\') + '"]}` (binary, chunked, no relay timeout).' };+          payload = { ...payload, path: file, savedToFile: true, sizeKB, _hint: 'Pull this with `adom-bridge pull_file {filePaths:["' + file.replace(/\\/g, '\\\\') + '"]}` (binary, chunked, no relay timeout).' };           delete payload.base64;         } catch (e) { payload._fileError = String((e && e.message) || e); }       }@@ -2186,7 +2220,7 @@ async function onHostFrameInner(frame) {           const f = payload.finder;           if (f.annotatedShot) spill(f.annotatedShot, 'annotated');           if (Array.isArray(f.shots)) f.shots.forEach((s, i) => spill(s, (s.label || 'shot') + '-' + i));-          f._hint = 'Pull annotatedShot.path / shots[].path with `adom-bridge-cli pull_file {filePaths:[...]}` (binary, no relay timeout). In the annotated overlay each candidate is a numbered box - ★=chosen, ⛔=occluded - and the blue crosshair is the click point.';+          f._hint = 'Pull annotatedShot.path / shots[].path with `adom-bridge pull_file {filePaths:[...]}` (binary, no relay timeout). In the annotated overlay each candidate is a numbered box - ★=chosen, ⛔=occluded - and the blue crosshair is the click point.';         } catch (e) { payload._finderFileError = String((e && e.message) || e); }       }       // taskbar: capture the driven window's hwnd at control-start, auto-flash per mode, and TEACH the

@@ -6,10 +6,10 @@ actually happens, step by step, the very first time?** There are several moving on two different machines, so it is worth laying out precisely.  > One-paragraph version: the **container never talks to the browser extension directly**. It talks to-> **Bridge (ab)** on the user's laptop over the relay, using the `adom-bridge-cli nbrowser_*` CLI.+> **Bridge (ab)** on the user's laptop over the relay, using the `adom-bridge nbrowser_*` CLI. > On first use you ask ab to install the **bridge** (one call), the user (or ab) gets the **extension** > loaded into Chrome/Edge, ab registers the tiny **native-messaging host**, and from then on every-> action is just `adom-bridge-cli nbrowser_*`. The container's only local artifact is the **skills** that+> action is just `adom-bridge nbrowser_*`. The container's only local artifact is the **skills** that > teach you those verbs. Nothing in the container listens for the browser; the laptop reaches back > through the relay. @@ -18,7 +18,7 @@ on two different machines, so it is worth laying out precisely. | Piece | Lives on | Role | |---|---|---| | **Your AI session + skills** | the **container** (cloud or ah/WSL2) | You. The installed skills (`driving-the-extension`, `native-browser-safety`, ...) teach you the `nbrowser_*` verbs and the safety rules. |-| **`adom-bridge-cli` (ab)** | the user's **laptop** | The hub. Receives your verbs over the relay, routes `nbrowser_*` to the bridge, ships results back. Always present. |+| **`adom-bridge` (ab)** | the user's **laptop** | The hub. Receives your verbs over the relay, routes `nbrowser_*` to the bridge, ships results back. Always present. | | **The bridge** (`bridge/server.js`) | the **laptop** (in ab's `bridges-cache`) | ab-spawned Node server. Binds an ephemeral loopback port, exposes `/command` to ab, and a raw-TCP loopback the host dials. Handles `nbrowser_*` and delegates `wgc` recording to ab. | | **The native-messaging host** (`host/native-host.js`) | the **laptop** | A tiny stdio<->TCP pump. Chrome/Edge launch it when the extension calls `connectNative`; it reads the bridge's discovery file and connects the extension to the bridge. | | **The extension** (`extension/`) | the user's **Chrome/Edge** | The hands. MV3 service worker that runs CDP + native `chrome.*` calls inside the user's real, signed-in profile. |@@ -28,7 +28,7 @@ on two different machines, so it is worth laying out precisely.  +---------------------------+      relay      +-------------------------------------------+  |  your AI session          |  wss://...:8765 |  Bridge (ab)                         |  |  + installed skills       |  ============>  |     |  routes nbrowser_*                  |- |  `adom-bridge-cli nbrowser_*`|                 |     v                                     |+ |  `adom-bridge nbrowser_*`|                 |     v                                     |  |  `adom-wiki ...` (install)|                 |  bridge/server.js  (ephemeral loopback)   |  +---------------------------+                 |     ^  raw-TCP loopback                   |                                                |     |                                     |@@ -41,7 +41,7 @@ on two different machines, so it is worth laying out precisely.  ## Endpoints: what talks to what (and what does NOT) -- **Container -> ab:** the relay, `wss://<container>.adom.cloud:8765`. You speak `adom-bridge-cli nbrowser_*`.+- **Container -> ab:** the relay, `wss://<container>.adom.cloud:8765`. You speak `adom-bridge nbrowser_*`. - **ab -> bridge:** HTTP `POST /command` on the bridge's ephemeral `127.0.0.1` port (written to a   discovery file; PORTS.md-compliant, never a fixed port). - **host -> bridge:** raw TCP on a second ephemeral loopback port the bridge writes to the same@@ -73,7 +73,7 @@ propagate*, below.) This step is container-local; it does not touch the laptop.  ### 2. Install the bridge on the laptop (one ab call) ```-adom-bridge-cli bridge_install '{"manifestUrl":"https://wiki.adom.inc/api/pages/adom/nb-bridge/files/native-browser-bridge-manifest.json"}'+adom-bridge bridge_install '{"manifestUrl":"https://wiki.adom.inc/api/pages/adom/nb-bridge/files/native-browser-bridge-manifest.json"}' ``` ab downloads the bridge zip the manifest points to, sha256-verifies it, and extracts it into `%LOCALAPPDATA%\Adom Bridge\bridges-cache\native-browser\`. ab's registry auto-discovers it and@@ -152,8 +152,8 @@ window in a driven profile), it calls `connectNative('inc.adom.native_browser')` host, the host reads the bridge discovery file and dials the bridge's loopback, and sends a `hello` with the profile id. **That is the moment the bridge knows the extension is live.** Check it: ```-adom-bridge-cli nbrowser_status     # ext connected? which browser/profile?-adom-bridge-cli nbrowser_profiles   # every BROWSER x PROFILE you can drive+adom-bridge nbrowser_status     # ext connected? which browser/profile?+adom-bridge nbrowser_profiles   # every BROWSER x PROFILE you can drive ``` If `nbrowser_status` says not connected, the usual cause is that the profile has **no open window** (an MV3 service worker sleeps when its profile has no windows). Opening a window wakes it. The bridge@@ -162,11 +162,11 @@ knows the extension is **connected**; it cannot see an installed-but-asleep exte ### 6. Your first useful action Always work in a window **you** open (never the user's existing ones - see `native-browser-safety`): ```-adom-bridge-cli nbrowser_open_window '{"url":"https://www.digikey.com","focused":false}'   # background; returns a sessionId-adom-bridge-cli nbrowser_screenshot  '{"sessionId":"<id>","maxWidth":1500}'                # see the page without foregrounding it-adom-bridge-cli nbrowser_credentials '{"match":"digikey"}'                                 # is there a saved login?+adom-bridge nbrowser_open_window '{"url":"https://www.digikey.com","focused":false}'   # background; returns a sessionId+adom-bridge nbrowser_screenshot  '{"sessionId":"<id>","maxWidth":1500}'                # see the page without foregrounding it+adom-bridge nbrowser_credentials '{"match":"digikey"}'                                 # is there a saved login? # ...click the sign-in field (Chrome autofills), submit, then fetch the CAD file behind the login.-adom-bridge-cli nbrowser_close_window '{"sessionId":"<id>"}'+adom-bridge nbrowser_close_window '{"sessionId":"<id>"}' ``` That round-trip - container -> relay -> ab -> bridge -> host -> extension -> back - is the whole point: it runs in the user's real, signed-in profile, so cookies/SSO/saved-logins/captcha all just work.@@ -176,7 +176,7 @@ it runs in the user's real, signed-in profile, so cookies/SSO/saved-logins/captc | Component | Installed by | Notes | |---|---|---| | Skills (in the container) | `adom-wiki pkg install` -> `install.sh` | Container-local; this is all the container keeps. |-| Bridge (laptop cache) | `adom-bridge-cli bridge_install` (once) | Auto-updates after that. |+| Bridge (laptop cache) | `adom-bridge bridge_install` (once) | Auto-updates after that. | | Native-messaging host (HKCU) | `install/install.ps1` (or the golden-image bake) | Per-browser; no UAC. | | Extension (in Chrome/Edge) | Web Store / managed policy, **or** ab-driven `Load unpacked`, **or** the user | **Not the bridge.** The bridge is the runtime server; it does not push the extension into the browser. | @@ -184,10 +184,10 @@ it runs in the user's real, signed-in profile, so cookies/SSO/saved-logins/captc extension arrives via the store or via ab driving `chrome://extensions`, and the bridge only ever *talks to* it once it connects. -## After the first install: it is all `adom-bridge-cli nbrowser_*`+## After the first install: it is all `adom-bridge nbrowser_*`  Once the four laptop pieces exist (bridge + host + extension + the connection), the container side is-just the `adom-bridge-cli nbrowser_*` CLI plus the skills that teach it. No re-install per task. The+just the `adom-bridge nbrowser_*` CLI plus the skills that teach it. No re-install per task. The bridge auto-updates; the extension auto-updates from the store (or you re-`Load unpacked` in dev).  ## How skills propagate