agent-browser is a CLI for driving a headless Chromium from the terminal, made for AI agents. It ships as an npm package and downloads its own Chromium, so it does not need Playwright, Puppeteer or a system Chrome.
# 1. Install the CLI globally (any Node 20+ works; on a mise-managed machine this lands under the active node)
npm install -g agent-browser
Omarchy used to add the install user to the docker group. As of 4.x it does
not, and an update migration removes the group from existing installs. The
Docker daemon is still installed and enabled, but reaching it now requires
sudo or a polkit prompt.
The reasoning is recorded in /usr/share/omarchy/install/config/docker.sh,
Running OpenCode inside Ghostty on Omarchy produced a near-unreadable light-gray-on-light-gray interface. The logo, prompt text, and status bar were all washed out. Switching Omarchy themes didn't help — the TUI stayed stuck in a light palette regardless of whether the system was using Catppuccin (dark), Tokyo Night, or anything else.
First I checked what OpenCode thought the system theme was. Its tui.json was set to "theme": "system", which means it tries to auto-detect light vs dark mode.
I ran omarchy-update today and noticed a couple of packages weren't getting the love they deserved. One was an orphaned foreign package no longer in the AUR, and another was stuck on an outdated AUR build. Here's how I fixed it — and automated it for the future.
First, I checked what foreign packages I had installed:
pacman -Qm
A merge commit landed on master, breaking the project's linear history requirement.
* 5fc5d7ecc Merge remote-tracking branch 'origin/develop' (HEAD → master)
|\
| * 1172ababb fix: rescue PaymentError and render error from Stripe (#5469)