← Commit history
Reframe README to developer/vibe-coding tone + use-case screenshots (oscilloscope, EDA, board)
4 files changed
+39−23
README.md+39−23@@ -1,44 +1,60 @@ # Adom Browser Extension (Chrome + Edge) -**Drive your real, logged-in Chrome/Edge from the Adom ecosystem — the native-browser counterpart to-`pup`.** Same command surface as the puppeteer bridge (`nbrowser_*` mirrors `browser_*`), but every-verb runs inside the user's *actual* signed-in browser, so cookies, SSO, saved logins, shopping-carts, and "I'm not a robot" human-trust signals all just work.+**Your AI's hands inside your real, signed-in Chrome or Edge.** The native-browser counterpart to+`pup` — the same command surface (`nbrowser_*` mirrors `browser_*`), but every verb runs inside your+*actual* browser, so your Adom AI assistant can **build, drive, and test web software right alongside+you**, in the browser you already work in. Cloud containers, Hydrogen Desktop, and the AD CLI reach it through the exact same `relay → adom-desktop → bridge` path they already use for pup. -## Demo — credential-aware login → chip fetch (no bot wall)+## Who we are, and why this extension needs broad browser capabilities -+**Adom Industries is an AI electronics-prototyping company.** We build a full, AI-native development+environment for the entire electronics industry — and we let developers everywhere build *on top of us*.+Our ecosystem and our users are continuously writing and running code: **web-based oscilloscopes,+web-based electronic design automation (EDA) and CAD software, and applications that drive and control+real circuit boards** — all in the browser, all day, every day. -**▶ [Watch the full 36-second video](/blob/app/adom-browser-extension/demo/adom-native-browser-demo.mp4)** (the Mouser login + captions) — or see the stills in [Screenshots](#screenshots) below.+Because Adom is a complete **"vibe coding"** development environment — where an AI assistant and the+developer build software together in real time — the Extension is designed to **operate the browser the+same way a human developer does**: open and navigate pages, read and screenshot what's on screen, fill+forms, click controls, inspect the DOM, run and debug JavaScript, and manage tabs, windows, downloads,+and the developer's own signed-in sessions. It is the **same category of capability that AI coding+assistants such as the Claude browser extension use to drive a browser for the user** — the AI agent's+hands inside the developer's own browser. The powerful permissions exist to deliver that on your command. -Driving John's real Chrome, hands-free: **the Adom cursor signs in to Mouser** (Chrome autofills the-saved password — Adom never sees it), then **fetches the ST VL53L5CX 8×8 ToF sensor's CAD** from-ComponentSearchEngine — KiCad symbol + footprint, STEP 3D model, and datasheet — straight past the-login wall, with no captcha because it's a *real* session.+## What developers build and drive with it++The software our community builds runs in the browser — and the Extension lets your AI assistant build,+drive, and test it with you. A few examples from the Adom ecosystem:++### Web-based oscilloscopes & instruments++Real test instruments, controlled from a browser tab — your AI sets the timebase, drags a trigger, and+reads the measurements back, the same way you would by hand.++### Web-based EDA & CAD++Schematic capture, autorouting, and design tools that live entirely in the browser — your AI fills the+canvas, re-runs the autorouter, and inspects nets right in the live app.++### Apps that drive real circuit boards++From a 3D board preview to flashing and driving real hardware — board software that runs in the browser,+operated hands-free by your AI. ## What's new - **Drive ALL your browser profiles** ([email protected], [email protected], …), not just one — `nbrowser_profiles` / `nbrowser_use_profile` switch instantly, with a persistent **security blocklist** to exclude any.-- **Know which vendors you can log into** — `nbrowser_credentials` is a *read-only* query over the+- **Know which of your tools you're signed into** — `nbrowser_credentials` is a *read-only* query over the browser's own saved-login store (**Chrome + Edge**); it never stores or exposes passwords.-- **Automate any vendor login** — focus the field → the browser autofills → submit. Proven on Mouser + CSE.+- **Sign into your tools hands-free** — focus the field → the browser autofills → submit, so the services+ and dev tools you already use just work in your real, signed-in session. - **Window control** — `nbrowser_fullscreen` / `window_state` (fullscreen / maximize / move / tile), `login_state`, and a robust hover that reveals tooltips on non-interactive elements. -## Screenshots--### Driving a vendor login — autofill, no captcha--The Adom cursor focuses the **Username** field; Chrome autofills the saved username + password (**Adom never sees it**), then submits. Because it's the real session, there's no captcha or anti-bot slider.--### Fetching chip CAD past the login wall--Signed in to ComponentSearchEngine, the Adom cursor clicks **Download Model** on the ST VL53L5CX (8×8 ToF) — pulling the KiCad symbol + footprint, STEP 3D model, and datasheet.- ## Sub-skills `adompkg install adom-browser-extension` installs this whole skill set — the core driving mechanics
screenshots/usecase-board.pngadded⋯ 1 unchanged line ⋯
screenshots/usecase-eda.pngadded⋯ 1 unchanged line ⋯
screenshots/usecase-oscilloscope.pngadded⋯ 1 unchanged line ⋯