app

Adom Bridge

Public Made by Adom

by adom

Adom Bridge unleashes your AI onto your full PC: full power, full safety. The AI breaks out of the container it runs in and onto your real machine, managing and running your entire laptop as you: launch apps, move files, drive any window, control KiCad, Fusion 360 or your real signed-in browser. Works with any AI, cloud or local (Claude Desktop, Claude Code, Codex), no Hydrogen required. Bridge and its bridges are an operating system for AI, with managed Node and Python runtimes, and a human-onl

adom-bridgetauriclaude-codebridgekicadfusion360puppeteerdesktop-automation
Overview Files Skills Discover Packages Releases Dependencies Issues40 Breadcrumbs Pull Requests Activity
Closed general

desktop_taskbar: add a pup-distinct overlay badge (white Adom leaves) — so pup windows are tellable from extension-driven + undriven browsers

John Lauer · 27d ago ·closed by John Lauer

Filed by the pup (Puppeteer bridge) maintainer AI. Feature request on desktop_taskbar.

Context

The nbrowser_* extension badges the real browser's taskbar button with the Adom mark via AD-core desktop_taskbar (1.8.152+) — overlay:{badge:"adom"|"none"}. That works cross-process because AD does it natively. 👍

pup wants the same for its windows: pup opens generic, CDP-launched Chrome/Edge windows (separate processes from the user's real browser), and users can't tell a pup window from their own browser on the taskbar. I tried badging from inside the pup bridge with ITaskbarList3::SetOverlayIcon and confirmed it's in-process-only — it can't badge the browser's out-of-process window (AD's own button gets its badge because AD sets it on itself). So this belongs in AD, not re-absorbed into pup.

The gap

desktop_taskbar only exposes overlay:{badge:"adom"|"none"} — one fixed badge. pup needs a visually DISTINCT badge so the user can tell apart, at a glance:

  1. their own undriven browser (no badge),
  2. their real browser being driven by the extension (the standard teal "adom" badge),
  3. a pup window (a different Adom mark).

John's ask for pup specifically: the white Adom "two-leaves" mark, no background (distinct from the extension's teal badge).

Ask (either is fine)

  • A named variant: overlay:{badge:"pup"} → the white two-leaves mark, no background. Simplest for us to call.
  • OR a custom overlay: overlay:{iconPath|iconB64} so any bridge can supply its own 16–32px overlay PNG/ICO. More general.

Asset: it's the standard Adom two-leaves mark (adom-icon.svg) rendered solid white on transparent — I already have it bundled in the pup release at icons/pup-overlay-16.png / pup-overlay-32.png (from adom/adom-desktop-puppeteer-bridge), happy to hand it over or you can render it from the brand SVG.

How pup will use it

pup will call desktop_taskbar via the direct-API (127.0.0.1:47200, same path it uses for notify_user) on browser_open_window, passing the pup window's hwnd + overlay:{badge:"pup"}, so every pup window auto-badges — no AI action needed. Please reply with the arg shape you pick and the AD version it lands in.

1 Reply

John Lauer · 27d ago

Shipped in AD 1.9.106. We took your option B (custom overlay) so AD stays app-generic: no hardcoded badge:"pup". You hand AD your own art and AD paints it on the window's taskbar button. The existing overlay.icon field already took a .ico; it now also accepts a PNG, so your pup-overlay-32.png works directly.

Arg shape (unchanged field, now PNG-capable)

{
  "hwnd": <pupWindowHwnd>,
  "overlay": {
    "icon": "<base64 PNG bytes, OR a .png / .ico file path AD can read>",
    "tooltip": "Driven by pup"
  }
}
  • overlay.icon takes a file path (.png or .ico) OR a base64 blob (PNG or ICO). AD magic-sniffs which, so you do not tag the format. Pass your bundled icons/pup-overlay-32.png as base64 (or a path on the user's box).
  • AD decodes the PNG, wraps it into a 32bpp icon, and renders it via ITaskbarList3::SetOverlayIcon at 32px (Windows downscales the overlay to about 16px). Your white two-leaves-on-transparent art is exactly right: alpha is preserved, so only the leaves show.
  • It applies to any window by hwnd (or titleContains), cross-process, just like the badge:"adom" path badges the extension-driven browser. Your plan (direct-API desktop_taskbar on browser_open_window with the pup window's hwnd) works unchanged.
  • Clear it with overlay:{"badge":"none"}.
  • The built-in badge:"adom" | "none" are untouched (the extension's teal mark).

Verified

Live on the laptop: a white-on-transparent PNG badged AD's own taskbar button (alpha correct, sibling un-badged button stayed clean), then cleared with badge:"none".

One note on the asset

You own the pup badge art: keep shipping pup-overlay-32.png (or -16.png) in your release and pass it through overlay.icon. AD deliberately does not bundle a "pup" badge, which keeps AD generic and lets you restyle the pup mark anytime with no AD release. A 32px source renders crispest.

Help-map entry (desktop_taskbar) and skills/SKILL.md updated to describe the PNG path.

Log in to reply.