NB - Native Browser Bridge

@@ -1,6 +1,6 @@ {   "slug": "adom-browser-extension",-  "version": "0.4.12",+  "version": "0.4.13",   "type": "app",   "title": "Adom Browser Extension",   "description": "What this install gives you: the AI SKILLS for driving this bridge, nothing else. It copies the nbrowser_* skill files into your container (Claude + Codex homes) and, via its dependency on adom/adom-desktop, pulls the AD CLI your AI uses to talk to the bridge. It does NOT put any binary of this project on your machine: the bridge runtime (the Release zip below) is downloaded and kept current AUTOMATICALLY by Adom Desktop on your desktop machine, and the browser extension itself is installed into Chrome/Edge separately (your AI can do that for you - just ask). Layer 1 (open/manage your real browser windows, e.g. OAuth consent) works with no extension installed; installing the extension unlocks layer 2: full driving (navigate, click, read, screenshot) of your real, signed-in Chrome/Edge.",

@@ -9,11 +9,11 @@     "chrome",     "edge",     "nbrowser",-    "ai-agent",-    "developer-tools",-    "vibe-coding",+    "pup",     "native-messaging",-    "adom-desktop"+    "adom-desktop",+    "credentials",+    "chip-fetcher"   ],   "status": "live",   "discovery_triggers": [@@ -57,5 +57,38 @@   },   "visibility": "public",   "brief": "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.",-  "discovery_pitch": "The native-browser extension drives the user's REAL signed-in Chrome/Edge via nbrowser_* verbs: use it for LOGGING IN, filling forms, and downloading behind auth with their OWN saved passwords - pup cannot (it is a fresh Chrome-for-Testing with no logins). Next moves: run 'adom-desktop bridge_list' to check it is installed; if not, OFFER to install it (see the installing-the-extension skill) - never make the user do it. If this container lacks the skills, 'adom-wiki pkg install adom/adom-browser-extension'. Check readiness with 'adom-desktop nbrowser_readiness' (state:needs-extension means offer the install)."+  "discovery_pitch": "The native-browser extension drives the user's REAL signed-in Chrome/Edge via nbrowser_* verbs: use it for LOGGING IN, filling forms, and downloading behind auth with their OWN saved passwords - pup cannot (it is a fresh Chrome-for-Testing with no logins). Next moves: run 'adom-desktop bridge_list' to check it is installed; if not, OFFER to install it (see the installing-the-extension skill) - never make the user do it. If this container lacks the skills, 'adom-wiki pkg install adom/adom-browser-extension'. Check readiness with 'adom-desktop nbrowser_readiness' (state:needs-extension means offer the install).",+  "version": "0.4.13",+  "type": "app",+  "description": "What this install gives you: the AI SKILLS for driving this bridge, nothing else. It copies the nbrowser_* skill files into your container (Claude + Codex homes) and, via its dependency on adom/adom-desktop, pulls the AD CLI your AI uses to talk to the bridge. It does NOT put any binary of this project on your machine: the bridge runtime (the Release zip below) is downloaded and kept current AUTOMATICALLY by Adom Desktop on your desktop machine, and the browser extension itself is installed into Chrome/Edge separately (your AI can do that for you - just ask). Layer 1 (open/manage your real browser windows, e.g. OAuth consent) works with no extension installed; installing the extension unlocks layer 2: full driving (navigate, click, read, screenshot) of your real, signed-in Chrome/Edge.",+  "install": {+    "binary_name": "adom-browser-extension"+  },+  "files": [+    "skills/adom-browser-extension/SKILL.md",+    "skills/driving-sites/SKILL.md",+    "skills/driving-the-desktop/SKILL.md",+    "skills/driving-the-extension/SKILL.md",+    "skills/driving-the-extension-demo/SKILL.md",+    "skills/installing-the-extension/SKILL.md",+    "skills/native-browser-recording/SKILL.md",+    "skills/native-browser-safety/SKILL.md",+    "skills/reading-google-messages/SKILL.md",+    "skills/uninstalling-the-extension/SKILL.md",+    "install.sh",+    "uninstall.sh",+    "package.json"+  ],+  "scripts": {+    "install": "./install.sh",+    "uninstall": "./uninstall.sh"+  },+  "dependencies": {+    "adom/adom-desktop": "^1.9.47"+  },+  "org": "adom",+  "author": {+    "name": "John Lauer",+    "email": "[email protected]"+  } }\ No newline at end of file

@@ -394,10 +394,13 @@ When a task only needs the user's real browser OPENED at a URL in the right prof CONSENT (adom-google, Autodesk APS: the user is already signed in; they just click Approve and your CLI's token poll picks up the result) - you do NOT need the extension installed: `nbrowser_open_os_window {sessionId, thread, purpose, profile, url}` (registration required, like every-window). It opens **BACKGROUND by default**: the window is minimized the instant it exists (a laptop-side-watcher at 30ms resolution, v0.1.35+ - no visible flash of the window) and its taskbar button flashes-ORANGE - the user clicks it when THEY are ready. `foreground:true` needs-`foregroundReason` + a `notify_user` first, same as everywhere else.+window). It opens **BACKGROUND by default** (v0.1.41+): it launches the window the same way Hydrogen+Desktop's browser picker does (a clean launch, no `--profile-directory=Default`), lets it fully build,+then minimizes it once with a gentle no-activate call - so it never steals focus and, importantly, never+crashes the browser (an earlier version minimized mid-construction in a tight loop and crashed the whole+Edge process - fixed). Its taskbar button flashes ORANGE so the user clicks it when THEY are ready. To+raise it later: `desktop_bring_to_front {hwnd}` (returned in the result) - only when the user asks to see+it. `foreground:true` needs `foregroundReason` + a `notify_user` first, same as everywhere else. - You CANNOT read, drive, or screenshot that window (no extension there) - poll the outcome   out-of-band or ask the user. - Close it when the flow is done: `nbrowser_close_window {sessionId}` (handled bridge-side for these).