Pup - the AI's own browser

@@ -1,7 +1,7 @@ --- name: pup user-invocable: true-description: "Drive a browser on the user's desktop from the cloud — the Puppeteer 'pup' bridge (pup_* verbs via the adom-bridge-cli CLI). pup drives the browser ALREADY on the machine in a pup-managed DURABLE profile (logins/localStorage persist and are shared across pup windows; {isolated:true} for a throwaway) (installed Chrome, else Microsoft Edge — on Windows every PC has Edge, on macOS neither is guaranteed so a download may be needed), driven over CDP, in the BACKGROUND so it never disturbs the user; NOT the user's real signed-in profile (that's the Adom extension's nbrowser_* verbs), NOT headless (a real rendered window, so screenshots/recording are true-to-life). Chrome for Testing only as a last resort. Open/close windows + tabs, navigate, screenshot, eval JS, record. This is the START-HERE skill: the mental model + when-to-use + the skill map; deeper topics route to the sub-skills. For 'is it ready' use pup_readiness (not pup_status). Trigger words: pup, puppeteer, browser window, open in pup, open my app in pup, browser screenshot, browser eval, browser reload, visual debug, headful chrome, pup_open_window, pup_screenshot, pup_readiness, pup_prewarm, chrome for testing, open in browser, pup_login, log into a site in pup, autofill password, saved login, durable profile, isolated window."+description: "Drive a browser on the user's desktop from the cloud — the Puppeteer 'pup' bridge (pup_* verbs via the adom-bridge-cli CLI). pup drives the browser ALREADY on the machine in a pup-managed DURABLE profile (logins/localStorage persist and are shared across pup windows; {isolated:true} for a throwaway) (installed Chrome, else Microsoft Edge — on Windows every PC has Edge, on macOS neither is guaranteed so a download may be needed), driven over CDP, in the BACKGROUND so it never disturbs the user; NOT the user's real signed-in profile (that's the Adom extension's nbrowser_* verbs), NOT headless (a real rendered window, so screenshots/recording are true-to-life). Chrome for Testing only as a last resort. Open/close windows + tabs, navigate, screenshot, eval JS, record. This is the START-HERE skill: the mental model + when-to-use + the skill map; deeper topics route to the sub-skills. For 'is it ready' use pup_readiness (not pup_status). Trigger words: pup, puppeteer, browser window, open in pup, open my app in pup, browser screenshot, browser eval, browser reload, visual debug, headful chrome, pup_open_window, pup_screenshot, pup_readiness, pup_prewarm, chrome for testing, open in browser, open my web app, show my app in the browser, preview my app, open the app I just built, view my app, open localhost, show my dev server, pup_login, log into a site in pup, autofill password, saved login, durable profile, isolated window." ---  # Pup — browser control on the user's desktop (start here)@@ -16,6 +16,22 @@ adom-bridge-cli --ai-thread "<your thread>" pup_screenshot  '{"sessionId":"mytas  ## THE CORE GOAL (John's words, so everyone truly understands it) +## "Open my web app in the browser" — the #1 use case, and its one trap++When the user asks to see an app they just built, pup IS the right surface (a real browser window on+their desktop that you can keep driving: reload after fixes, screenshot, eval). The ONE trap: an app+running in a CLOUD container is NOT reachable from the desktop as `localhost:<port>` — pup's Chrome+runs on the DESKTOP. Use the container's public proxy URL instead:++```+https://{container-slug}.adom.cloud/proxy/{port}/+```++Open it background-first (`foreground:false` + the taskbar flash signals the user), give the window+your thread's sessionId, and re-use the SAME window on every subsequent "check it now" (navigate /+reload, don't spawn new windows). Under Hydrogen (local container) `http://localhost:{port}` IS+correct — the trap is cloud-only. pup lints obvious container-local URLs and will warn you.+ pup exists to be **an AI-driven browser that can do everything it needs to for you: the best assistant in the world**. The engine of that goal is the shared durable **adom-you** profile: