NB - Native Browser Bridge

@@ -24,25 +24,31 @@ and the developer's own signed-in sessions. It is the **same category of capabil 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. -## What developers build and drive with it+## What it does for you -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:+Three real apps from the Adom ecosystem — and how the Extension helps you get the work done. -### Web-based oscilloscopes & instruments+### Driving a web-based oscilloscope ![A web-based oscilloscope — live waveform with channel, timebase, and trigger controls](/blob/app/adom-browser-extension/screenshots/usecase-oscilloscope.png)-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.+You're bringing up a browser-based scope and need to confirm the trigger and timebase behave against real+signals. Instead of clicking through every iteration by hand, your AI assistant drives the live app in+your own browser — sets the timebase, drags the trigger to CH1-rising, reads the measurements back, and+screenshots the result. You stay in flow while it verifies the instrument and flags a regression the+moment one appears. -### Web-based EDA & CAD+### Building in a web-based EDA / CAD tool ![A browser EDA tool showing a CAN-bus schematic alongside 3D / PCB / Schematic tabs](/blob/app/adom-browser-extension/screenshots/usecase-eda.png)-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.+Mid-design, you want to try a change and see it routed. Your AI opens the EDA tool in the browser you're+already signed into, fills the schematic, re-runs the autorouter, and inspects the nets — turning "try+this and tell me what breaks" into something it just does, in the same session where your part libraries+and logins already live. -### Apps that drive real circuit boards+### Controlling real circuit boards ![A 3D PCB rendered in a browser CAD viewer](/blob/app/adom-browser-extension/screenshots/usecase-board.png)-From a 3D board preview to flashing and driving real hardware — board software that runs in the browser,-operated hands-free by your AI.+When a board-control app talks to real hardware, the AI needs your *actual* browser — your device session,+your USB permissions, your dashboard login. The Extension gives it exactly that: it drives the live page,+flashes and operates the board, and reports back — so hardware-in-the-loop testing runs hands-free instead+of you babysitting every flash.  ## What's new @@ -161,12 +167,6 @@ Driving the user's real browser, verified end-to-end: screenshot / eval) is active — the bridge lazy-attaches and idle-detaches after ~8s. Native verbs never show it. Full breakdown + the verb-by-verb table: [`skills/driving-the-extension/SKILL.md`](skills/driving-the-extension/SKILL.md). -### ⭐ The use case it's built for-EE CAD sources (SnapEDA/SnapMagic, Ultralibrarian, Mouser, DigiKey) gate downloads behind **login +-captcha** — pup's empty profile hits the wall. The native browser uses the engineer's **real logged-in-session**, so the STEP / KiCad / Altium / Fusion `.lbr` bundles just download. Drive the chip-fetcher-ladder with `nbrowser_*` instead of `browser_*` — same flow, real session, no wall.- ### Try the handshake locally (dev)  ```bash

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯