OpenWA installs without downloading a browser
Version 5.5.1 prefers installed Chrome and provisions a missing selected browser on demand, reusing its cache on later runs.
OpenWA 5.5.1 removes browser downloads from CLI installation. Startup prefers an installed Chrome, and a missing browser can be provisioned when it is actually selected. Subsequent launches reuse the per-user cache rather than downloading the same executable again.
npx @open-wa/wa-automate@5.5.1 --use-chromeChrome, Chromium and Lightpanda are explicit choices. When no browser is available, the interactive flow offers the selection. Existing custom executable paths remain explicit operator choices; provisioned executables use cache coordination, download policy and integrity checks.
This changes when the cost occurs. Package installation stays free of browser downloads, but choosing a missing browser still needs a download and usable host dependencies. A cached executable avoids a repeated download, not the RAM needed by a running browser.
Where Lightpanda fits
The Lightpanda driver provides an experimental lightweight path for basic automation. It uses puppeteer-core, downloads its pinned executable only when needed and verifies its release digest. Lightpanda has no rendering, screenshots or video and has limited WhatsApp compatibility. Windows needs WSL2.
It isn't a substitute for Chrome's sticker rendering or the calling dashboard. Reload recovery, outbound delivery and full media parity remain unconfirmed. Choose Chrome for the widest supported media and browser behavior; choose Lightpanda deliberately for experiments with its current boundaries.
Read the quickstart for startup and the Lightpanda package guide for executable and cache settings.