Omarchy

On Omarchy, Bogen takes its colours and font from your theme, the bar shows when an agent is drawing, and Bogen gets a launcher, keys and a user service.

Install

bogen omarchy install --dry-run   # prints every step, changes nothing
bogen omarchy install

From a checkout, integrations/omarchy/install.sh is the same script; build first with npm install && npm run build. It needs omarchy, jq and curl, asks nothing, and is safe to run again. Anything it replaces that it did not write goes to ~/.local/state/bogen/backups/ first.

Option	What it does
`--dry-run`	Print every step and change nothing.
`--no-service`	Leave out the user service.
`--no-plugin`	Leave out the bar widget.
`--no-hypr`	Leave out the window rules and keys.
`--tailnet`	Make the service also listen on this machine's Tailscale address, for device sync, and offer to open the firewall for it.

What it adds:

What	Where
`bogen` wrapper, only if you have no `bogen` yet	`~/.local/bin/bogen`
`bogen-launch`, `bogen-place-screenshot`	`~/.local/bin/`
User service running `bogen serve`	`~/.config/systemd/user/bogen.service`
Launcher and icon, through `omarchy webapp install`	`~/.local/share/applications/Bogen.desktop`
`.bogen` file type	`~/.local/share/mime/packages/bogen.xml`
Theme and font hooks	`~/.config/omarchy/hooks/{theme-set,font-set}.d/bogen-reload`
Bar widget	`~/.config/omarchy/plugins/dev.bogen.bogen/`
Window rules and keys	`~/.config/hypr/bogen.lua`, loaded from a marked block at the end of `hyprland.lua`

If Hyprland reports a new config error after the change, the installer takes its block back out. With the npm package or the AUR package, run bogen omarchy install as your own user.

Keys

Keys are checked against hyprctl binds and never replace a binding. Open Bogen gets the first free one of Super+Shift+D, Super+Shift+Alt+D, Super+Ctrl+Shift+D and Super+Shift+Alt+B, and place the newest screenshot gets the next. The installer prints which. On a stock Omarchy, Super+Shift+D is Docker, so Bogen moves along.

Theme and font

The editor's chrome takes its colours from your theme's colors.toml and its font from your system font, and follows omarchy theme set and font changes live. The canvas itself is never themed: your designs keep their own colours. A monospaced system font is ignored on purpose.

The Tokens panel has a button that brings the active palette into a file as tokens, such as omarchy-accent and omarchy-font.

The icon is muted while the server is stopped. While an agent works, it turns the accent colour with a slow pulse; the pulse stays off when Hyprland animations are off.

Left click opens the panel, middle click makes a new file, right click opens Bogen.
In the panel: N new file, O open, S start or stop the server, R refresh, arrows and Enter to move.
The panel lists open files, agent activity and the last runs over all files, and, with device sync, the other device and its state. It warns when that device runs another version.

The widget talks to the server over HTTP and starts no process: every 5 seconds while the server runs, every 15 while it does not, and faster only while the panel is open or an agent works.

Notifications

You get a notification when an agent finishes, when a comment arrives, and when a run started from a comment ends. Clicking one opens the file. Each kind can be turned off in the widget's settings.

Screenshots to the canvas

bogen-place-screenshot puts the newest screenshot from omarchy capture into the Bogen file you are working on. With --pick you choose one in Omarchy's image picker, from your screenshot folder or a folder you name. The installer binds a key to it (see Keys).

Uninstall

bogen omarchy uninstall --dry-run
bogen omarchy uninstall

Your designs in ~/.local/share/bogen stay where they are.

Limits

These parts have been checked with dry runs and stand-ins rather than on a live desktop:

the bar widget passes omarchy plugin validate and has run in a separate Quickshell, not yet in the real bar;
notifications have run against a stand-in for omarchy-notification-send;
the launcher, service and Hyprland rules have run as dry runs, and the window class is not yet confirmed;
theme following has been tested with copies of a theme and the live theme, not yet with a real theme switch;
the screenshot picker itself has not been run.

The widget is not published as its own plugin repository yet, so omarchy plugin add cannot install it alone.