← Commit history
page.json+5−38@@ -9,11 +9,11 @@ "chrome", "edge", "nbrowser",- "pup",+ "ai-agent",+ "developer-tools",+ "vibe-coding", "native-messaging",- "adom-desktop",- "credentials",- "chip-fetcher"+ "adom-desktop" ], "status": "live", "discovery_triggers": [@@ -57,38 +57,5 @@ }, "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).",- "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]"- }+ "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)." }