feat(browser): add opt-in Google Chrome Beta support#5999
Open
kvncrw wants to merge 2 commits into
Open
Conversation
added 2 commits
May 29, 2026 17:03
Add `chrome-beta` as an optional, opt-in browser alongside the existing chrome/brave/edge/firefox/zen choices. This does NOT change the default browser (omarchy-chromium); it only adds a selectable install/remove target and an XDG default-browser mapping for users who explicitly choose it via Setup > Install > Browser > Chrome Beta. Motivation: users running AI coding agents that drive a browser via Playwright / Chrome DevTools Protocol (CDP) need a browser that tracks upstream Chromium closely - newer DevTools Protocol surface, reliable --remote-debugging-port behavior under Wayland, and fewer version-skew issues against Playwright's expected browser revision. Chrome Beta gives those users a browser that "just works" for automation without imposing a beta channel on everyone. Wiring mirrors the existing `chrome` channel: - omarchy-install-browser: new `chrome-beta` case installs the AUR `google-chrome-beta` package, writes chrome-beta-flags.conf, reuses the shared /etc/opt/chrome managed-policy dir, and applies the theme color. - omarchy-remove-browser: new `chrome-beta` case; both chrome and chrome-beta now guard removal of the shared color.json so removing one channel does not strip the policy while the other is still installed. - omarchy-default-browser: maps chrome-beta <-> google-chrome-beta.desktop. - omarchy-theme-set-browser: refreshes a running google-chrome-beta. - omarchy-menu: adds Chrome Beta to the install, remove, and default browser submenus (specific glob arm ordered before *Chrome*).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds an opt-in way to install and use Google Chrome Beta (
google-chrome-betafrom the AUR) as a selectable browser in Omarchy, alongside the existing chrome/brave/edge/firefox/zen choices.This does not change the default browser. omarchy-chromium remains the default for everyone. Chrome Beta only appears as an additional choice a user explicitly opts into via
Setup > Install > Browser > Chrome Beta(oromarchy install browser chrome-beta). Nobody who doesn't ask for it is affected.Motivation
A growing number of Omarchy users run AI coding agents that drive a browser programmatically — via Playwright or the Chrome DevTools Protocol (CDP) — for tasks like end-to-end testing, scraping, and agentic web automation. That workload has a hard requirement that ordinary browsing doesn't: the local browser has to stay close to upstream Chromium.
Concretely:
--remote-debugging-portreliability under Wayland. Headless and remote-controlled launches on Wayland are sensitive to the exact Chromium build and its packaging. The upstream-tracking Google channel behaves predictably here, where distro-patched builds sometimes don't.A stable distro Chromium is the right default for daily browsing, but for the automation use case it's frequently either behind upstream or patched in ways that make headless/remote-controlled use flaky. An opt-in Chrome Beta gives those users a browser that "just works" for automation without imposing a beta channel on everyone else.
Chrome Beta (not Dev/Canary) is deliberately chosen: it tracks upstream closely enough to solve the skew problem while still being stable enough for real use.
What changed
Wiring mirrors the existing
chromechannel exactly — no new patterns introduced:bin/omarchy-install-browserchrome-betacase: installs AURgoogle-chrome-beta, writes~/.config/chrome-beta-flags.conf(the flags file the Chrome Beta wrapper actually reads), reuses the shared/etc/opt/chrome/policies/managedpolicy dir, applies the current theme color.bin/omarchy-remove-browserchrome-betacase. Bothchromeandchrome-betanow guard removal of the sharedcolor.jsonso removing one Chrome channel doesn't strip the managed policy while the other channel is still installed (same shared-dir guard pattern already used for Brave / Brave Origin).bin/omarchy-default-browserchrome-beta↔google-chrome-beta.desktop(both directions).bin/omarchy-theme-set-browsergoogle-chrome-betaso theme color changes apply live.bin/omarchy-menu*"Chrome Beta"*glob arm is ordered before*Chrome*(same specific-before-general ordering already used for Brave Origin vs Brave).Command metadata (
omarchy:args/ usage strings) updated to includechrome-beta.How a user opts in
Via the menu:
Or directly:
The install prints
Chrome Beta browser installed. Make it the default via Setup > Defaults > Browser.— it intentionally leaves the default browser untouched. Setting it as default (optional) is a separate explicit step:Removal:
Testing
bash test/omarchy-cli-test.sh— full suite passes (including the metadata/route assertions).bash -nclean on all five modified scripts.omarchy install browser --helpand the usage strings surfacechrome-beta.Opened as a draft for maintainer review of the approach before finalizing.