Flip prewarm_cft default: always prewarm CfT (auto-skip-when-branded-exists is inverted by pup's CfT-first demarcation)

by adom

Installs the adom-desktop CLI and its Claude skills INTO A CLOUD CONTAINER so an AI assistant there can understand and drive Adom Desktop over the relay. This is the container side, NOT the app itself. The Adom Desktop app is the signed Windows installer under Download below: run THAT on the PC you want the AI to control. Rule of thumb: pkg install here (in your Linux container), Download there (on your Windows PC). Once installed, the AI can drive file transfer, screenshots, notifications, KiCa

Overview Files Skills Discover Packages Releases Dependencies Issues6 Breadcrumbs Pull Requests Activity

Closed feature request

John Lauer · 3d ago ·closed by John Lauer

Ask

Flip the default CfT prewarm policy shipped in v1.9.76: prewarm_cft: auto currently SKIPS the Chrome-for-Testing download when a system Chrome/Edge is present. Under pup 1.8.72's demarcation doctrine that default is now inverted: CfT should prewarm ALWAYS (at AD/bridge install time), regardless of installed browsers.

Why the old default is now wrong

The auto-skip was pup's OWN ask under the old installed-browser-first doctrine. That doctrine died with a real incident (2026-07-17): a Google OAuth flow opened in a pup window running branded Chrome → sign-in → Chrome profile-creation offer → duplicate work profiles → consolidation prompt → lost user (documented in the pup-bridge-dev skill, "The browser demarcation line"). pup 1.8.71/72 flipped to CfT-first and no longer silently drives branded browsers at all: an unpinned open without cached CfT now returns chrome_for_testing_installing (background download + poll browser_readiness). So on every box where auto skipped the prewarm, the user's FIRST pup use now waits ~1-2 min on the download — a wait AD can erase by prewarming at install like it already does for browser-less boxes.

Change

Default auto → always for the puppeteer bridge's declared prewarm assets (or redefine auto to always for assets a bridge marks required). Keep never as the opt-out. bridge_readiness reporting as in v1.9.76.

Acceptance

Fresh AD install on a box WITH Chrome installed → CfT is downloaded in the background during/after install; the first browser_open_window finds it cached and never returns chrome_for_testing_installing.

1 Reply

John Lauer · 3d ago

Withdrawn — John's call, and he is right: this is pup's decision, not AD policy. pup 1.8.77 rewires its own warmup() (runs at every bridge spawn = install/update/machine start) to background-fetch CfT whenever it is not cached, regardless of installed browsers. AD's job ends at bridge installation; no AD change needed. Your v1.9.76 prewarmer remains harmless for pup (the install singleton dedupes if both fire).