← Commit history
README.md+18@@ -182,6 +182,24 @@ Third parties are welcome to build their own version. The **[Fork & develop ## Sub-skills +### Three version numbers, three different things (they are NOT the same)++This page carries three independent version streams. Confusing them is the usual cause of a "why won't+it connect" dead end:++| Stream | What it is | Where you see it | Current |+|---|---|---|---|+| **Bridge runtime** | the local server Adom Desktop runs (`bridge.json` version) | the **Download** card | 0.1.50 |+| **Extension + host** | the MV3 extension + native host loaded into Chrome/Edge (`extension/manifest.json`) | `chrome://extensions` | 0.1.3 |+| **Skills package** | the docs your AI reads (`pkg install`, root `package.json`) | the **Install** card | 0.4.x |++The bridge and the extension are BOTH `0.1.x` but are **different numbers** and update independently.+The skew that matters for connectivity is **extension vs `bridge.json` `expectedExtensionVersion`** (the+extension the running bridge speaks to) — NOT the `0.4.x` skills-package number. If the native host keeps+exiting ("Native host has exited"), your extension/host is too old for the running bridge: re-sync the+`extension/` + `host/` folders to the current build and reload. `nbrowser_readiness` (bridge 0.1.50+)+reports this directly as `staleOnDisk`.+ > **What `pkg install` gives you:** this package installs the bridge's SKILLS into your container so your > AI knows how to drive your real signed-in Chrome and Edge; Adom Desktop loads the bridge runtime itself > from the release zip. The skills alone give you no bridge, and a bridge alone gives a calling AI no
package.json+1−1@@ -1,6 +1,6 @@ { "slug": "adom-browser-extension",- "version": "0.4.14",+ "version": "0.4.15", "type": "app", "title": "Adom Browser Extension", "description": "This package installs the bridge's SKILLS into your container so your AI knows how to drive your real signed-in Chrome and Edge; Adom Desktop loads the bridge runtime itself from the release zip.",
page.json+38−5@@ -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.15",+ "type": "app",+ "description": "This package installs the bridge's SKILLS into your container so your AI knows how to drive your real signed-in Chrome and Edge; Adom Desktop loads the bridge runtime itself from the release zip.",+ "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]"+ } }