chrome-sway
| Version | 2026.144.1443 |
| Repo | superproject |
Sway autostarts the Chrome CDP browser via a config.d drop-in that execs chrome-wrapper
A composition candy with one install of its own: a Sway config.d
drop-in (chrome-sway.conf) holding exec chrome-wrapper, so the
compositor launches Chrome on startup. It composes /charly-selkies:sway
(the headless compositor that reads config.d), /charly-selkies:chrome
(the browser), and /charly-selkies:chrome-cdp (which installs the
chrome-wrapper launcher the snippet execs). Every fact below is
observable: the installed drop-in, its exec directive, the
chrome-wrapper target it references, and the composed Chrome + Sway
binaries the autostart depends on.
Acceptance plan
Section titled “Acceptance plan”This candy’s plan: — the runnable spec charly check executes against a live deployment. check: steps are idempotent probes; run: steps change state.
| Intent | Step |
|---|---|
run |
mkdir=${HOME}/.config/sway/config.d |
run |
copy=chrome-sway.conf |
check |
the chrome-sway autostart snippet is installed in sway’s config.d drop-in dir |
check |
the snippet tells sway to exec the chrome-wrapper launcher on startup |
check |
the chrome-wrapper launcher the snippet execs is installed and executable |
check |
Google Chrome is installed for the compositor to launch |
check |
the sway compositor that reads the config.d drop-in is installed |