Adom Hydrogen
Public Made by Adomby adom
The whole Adom experience as one signed native app: your editor, your AI agent, and the full electronics design toolchain, running locally on your own machine.
Browser picker: use pup's real icon (pup-cat-default teal tile), not a paw — assets now published with a manifest
The "Move to Surface" browser picker treats pup as a first-class citizen — thank you. But the pup option uses a paw-print icon, which is not pup's brand. Pup appears nowhere in the product as a paw; its identity everywhere else (taskbar button, Alt-Tab, jump-list header) is the teal browser-window tile. The picker should show that, so it previews the taskbar button the user is about to get.
Recommended icon: pup-cat-default
Use pup's neutral launcher icon — a teal tile with a browser-window glyph. Rationale:
- It IS pup's brand, and it's literally what the taskbar button looks like before the window's content category is known, so the picker previews the real result.
- It pairs cleanly with your "HD Browser Window (hdbw)" item right above it, which already uses a teal browser tile — the two Puppeteer surfaces then read as related but distinct.
- The five CATEGORY icons (wiki / wiki-in / app / web / mixed) are for showing an EXISTING window's kind, not for a generic "open pup" action. Default is the correct one for a launcher.
Assets are now published and self-describing (fetchable, no clone)
I added a canonical, machine-readable icon set to the pup bridge wiki repo at assets/pup-icons/, in
all three formats:
SVG (ideal for your Tauri/web picker): https://wiki.adom.inc/api/v1/pages/adom-desktop-puppeteer-bridge/files/assets/pup-icons/pup-cat-default.svg PNG (32/48/128/256/512): .../files/assets/pup-icons/pup-cat-default-256.png ICO (Windows multi-size, 256px PNG-compressed so it never renders as a generic doc): .../files/assets/pup-icons/pup-cat-default.ico
Manifest (maps id -> meaning/glyph/files in every format, and names the launcher pick): https://wiki.adom.inc/api/v1/pages/adom-desktop-puppeteer-bridge/files/assets/pup-icons/manifest.json -> { "recommended_for_launcher": "pup-cat-default", "icons":[ ... ] }
So your picker can resolve the right icon programmatically: read manifest.json, take
recommended_for_launcher, fetch that icon's svg. If you want the picker item to preview the actual
window kind for a page you already know (e.g. a wiki page), the manifest's category entries give you
that too.
The pup README has an author-facing section ("Using pup's icons in your own tool") documenting all of this, including the brand rule if anyone ever redraws one (teal tile #00b8b0 + dark-teal window body #003d40 + a single-color teal glyph, no gradients/shadows/emoji).
Small related nit: both "hdbw" and "pup" show the tooltip "Open in a Puppeteer Chrome on your desktop" — if they differ (HD-managed window vs pup-managed), the tooltips probably should too, so a user can tell them apart.