Adom Browser Extension

Five real vendor sites. One logged-in session. No bot walls.

The native-browser extension drives your actual signed-in Chrome/Edge — so every vendor's cookies, SSO, saved logins and "I'm not a robot" human-trust come for free. Here it is on Mouser, SnapMagic, ComponentSearchEngine, DigiKey and TI, signing in and fetching chip CAD past the login walls that stop a headless bot cold.

▶ 36-second demo. 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 (KiCad symbol + footprint, STEP 3D model, datasheet) from ComponentSearchEngine. No captcha, because it's a real session.

Five vendors, one real session

live

Adom drives the Mouser sign-in — the cursor on the Username field, johnAdom + password autofilled

✓ login automated

Mouser — autofill sign-in

The Adom cursor focuses the Username field; Chrome autofills johnAdom + the saved password (Adom never sees it) and submits. Real session → no captcha, no anti-bot slider.

SnapMagic login with john@adom.inc + password autofilled and the Adom debug bar visible

✓ login automated · invisible reCAPTCHA

SnapMagic (SnapEDA) — credential-aware login

nbrowser_credentials knew snapeda.com, so Chrome pre-filled john@adom.inc + password. SnapMagic's login is gated by an invisible reCAPTCHA bound to the button — the real, trusted session clears it silently on submit.

SnapMagic signed in — VL53L5CX search returns 9 parts with one-click KiCad/STEP download icons

▸ past the guest wall

SnapMagic — signed in, downloads unlocked

Signed in, the VL53L5CX search returns 9 parts with one-click KiCad symbol + footprint and STEP downloads — the guest "log in to download" wall is gone.

ComponentSearchEngine VL53L5CX page, the Adom cursor on Download Model, signed in as John Lauer

▸ chip CAD fetch

ComponentSearchEngine — fetch past the wall

Signed in, the cursor clicks Download Model on the ST VL53L5CX (8×8 ToF) — pulling the KiCad symbol + footprint, STEP 3D model, and the datasheet in one go.

▸ driven live

DigiKey — driven in your real profile

The native browser renders and drives DigiKey inside your actual Chrome — full page, real cookies, your cart. DigiKey is already in your saved-login vault.

nbrowser_credentials → auth.digikey.com ✓

▸ driven live

TI.com — driven, SSO-ready

TI.com driven live in your real session. Your TI SSO login is in the vault, so signing in for a reference-design or sample download is one autofill away.

nbrowser_credentials → login.ti.com ✓

"I'm not a robot?" — handled

human-trust

The reCAPTCHA 'I'm not a robot' checkbox in the real browser

The gate that stops headless bots

UltraLibrarian, ComponentSearchEngine and SnapEDA/SnapMagic throw reCAPTCHA at anonymous, headless automation. The native browser runs in your real, trusted session, so the human-trust signals are already there:

✓Invisible reCAPTCHA (like SnapMagic's login) passes silently on submit — verified above, the sign-in just went through.

✓When the visible "I'm not a robot" checkbox appears, the Adom cursor clicks it — and because the session is trusted, it clears with no "select all the traffic lights" image grid.

✓During a real human-gate (2FA / a hard challenge), the taskbar turns yellow and flashes "come look" — it hands control back instead of guessing.

One AI, two browsers — at the same time

parallel

Every browser × profile is its own independently-addressable connection, keyed browser:profile. Here the same AI session drives Microsoft Edge and Google Chrome at once — each on its own page, each its own key. Separate Claude/Codex threads can each take a different browser/profile; nothing collides.

Edge driving the wiki extension page — **EDGE** · `edge:john@adom.inc` — driving the extension's own wiki page (note Edge's **Chat**/Copilot button)

Chrome driving the Adom apps grid — **CHROME** · `chrome:john@adom.inc` — driving the Adom apps grid (note Chrome's **Ask Gemini** button)

Address either with profile:"edge:john@adom.inc" on any verb. The host even self-detects its browser from its own process tree, so a browser registers correctly with no extension reload.

Drive it yourself: "load my native browser and log into Mouser" · adompkg install adom-browser-extension · full docs in the README below.