David Heinemeier HanssonandClaude Opus 5
aa9f0c54c5
Laptop speakers ship voiced by the vendor's Windows DSP layer, which Linux does not get. A tuning restores that as a PipeWire filter-chain in front of the internal speaker sink, matched to the machine by DMI string and expected sink. Adding a laptop is a directory under default/audio/tunings with two files and no new code: matching is data. The XPS 14 DA14260 tuning included here was derived by measuring the xps-audio-linux EasyEffects profile (MIT) and fitting a biquad chain to it, so no impulse response or other upstream asset is redistributed. It measures 1.24 dB RMS against that reference, and matches its dynamic range within 0.1 LU -- the reference's multiband compressor turned out to contribute nothing, so a linear chain replaces it. Bass Q is capped deliberately: a closer magnitude fit swung group delay 31 ms across 63-80 Hz, which smears bass transients. The graph runs as its own PipeWire client under its own config name rather than loading into the audio daemon. The daemon only reads its config at startup, so a daemon-loaded tuning could only be switched by restarting PipeWire -- which drops every PulseAudio client's connection, and applications that do not reconnect (Spotify) then have to be restarted by hand. Hosting it separately also contains failure, since a malformed tuning breaks only that service. Three things about the surrounding audio graph needed fixing for this to behave: - Volume must live downstream of the tuning. omarchy-audio-output-sink is now the single definition of which sink an output's volume really uses, shared by the volume keys, the output switcher's OSD and the audio panel, so they cannot disagree. It resolves the current default output, which keeps it correct when headphones are selected while a tuning exists. - The tuning's own output is a movable sink input, so rerouting "all streams" to a newly selected output would drag the processing onto headphones, or into the tuning's own sink, which is a cycle. It is pinned, and stream moves are limited to streams carrying an application.name. - The physical sink a tuning fronts is not independently selectable, since picking it would only bypass the tuning, so it is kept out of the output list. Applying happens at first-run, not finalize-user, because finalize-user also runs in the ISO chroot where there is no audio server and nothing would retry. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
First-party plugins
These plugins ship with Omarchy and are discovered by the shell at startup.
They use the same manifest.json contract as third-party plugins; the
only difference is that the shell flags them with __isFirstParty: true.
First-party non-bar plugins are always enabled; omarchy.bar is the default
bar option and becomes inactive only while a third-party kind: "bar" plugin is
selected. Services and keep-loaded panels are mounted at startup; other panels,
overlays, and menus are loaded on demand.
User-installed plugins live alongside these conceptually but on disk under
~/.config/omarchy/plugins/<plugin-id>/ rather than in this directory.
| Plugin | id | kinds | entry point |
|---|---|---|---|
| Bar | omarchy.bar |
bar |
bar/Bar.qml |
| Image picker | omarchy.image-picker |
overlay |
image-picker/ImagePicker.qml |
| Emojis | omarchy.emojis |
overlay |
emojis/Emojis.qml |
| Clipboard mgr | omarchy.clipboard |
overlay |
clipboard/Clipboard.qml |
| Reminders | omarchy.reminders |
overlay |
reminders/ReminderFlow.qml |
| Omarchy menu | omarchy.menu |
menu, bar-widget |
menu/Menu.qml, menu/BarWidget.qml |
| Notifications | omarchy.notifications |
service, bar-widget |
notifications/Service.qml, notifications/BarWidget.qml |
| Audio | omarchy.audio |
bar-widget |
panels/audio/Panel.qml |
| Bluetooth | omarchy.bluetooth |
bar-widget |
panels/bluetooth/Panel.qml |
| Monitor | omarchy.monitor |
bar-widget |
panels/monitor/Panel.qml |
| Network | omarchy.network |
bar-widget |
panels/network/Panel.qml |
| Power | omarchy.power |
bar-widget |
panels/power/Panel.qml |
| Tailscale | omarchy.tailscale |
bar-widget |
panels/tailscale/Panel.qml |
| Model usage | omarchy.model-usage |
bar-widget |
model-usage/Widget.qml |
| Weather | omarchy.weather |
bar-widget |
panels/weather/BarWidget.qml |
| Media | omarchy.media |
service, bar-widget |
services/media/Service.qml, services/media/BarWidget.qml |
| Battery | omarchy.battery |
service |
services/battery/Service.qml |
| Idle | omarchy.idle |
service |
services/idle/Service.qml |
| Night light | omarchy.nightlight |
service |
services/nightlight/Service.qml |
| Lock screen | omarchy.lock |
service |
lock/Service.qml |
| OSD | omarchy.osd |
panel |
osd/Osd.qml |
| Polkit agent | omarchy.polkit |
service |
polkit/PolkitAgent.qml |
First-party bar-only widgets also carry manifests next to their QML files,
e.g. bar/widgets/Clock.manifest.json. Rich popup widgets live in their
own plugin directories, each with its own manifest.json.
Bar
The built-in status bar and default full-bar option. Layout lives in the
top-level bar: subtree of ~/.config/omarchy/shell.json (with the shell
providing config/omarchy/shell.json when
the user has no file). See bar/README.md for the widget catalogue
and customization schema.
Image picker
Fullscreen image-grid selector overlay. Used by omarchy-menu-images
(wallpaper picker) and omarchy-theme-switcher (theme picker) and any
other caller that wants to present a directory of images with previews.
Two ways to drive it:
- Shell-level summon:
omarchy-shell shell summon omarchy.image-picker '<jsonPayload>'. The payload can carryimageDirs,imageRows,selectedImage,selectionFile,doneFile,showLabels,filterable. Best for in-shell callers that already speak JSON. - Direct IPC target:
omarchy-shell image-selector open <imageDirs> <imageRowsB64> <selectedImage> <selectionFile> <doneFile> <showLabels> <filterable>. Positional args;imageRowsB64is base64-encoded so embedded newlines / tabs survive the bash argv handoff. This is whatomarchy-menu-imagesuses. Colors come from the central shell theme singleton; there is no per-call override surface.
The selection round-trip remains file-based: callers create a
selection_file and done_file (both mktemp), pass the paths, and
poll done_file for existence. The plugin writes the chosen path into
selection_file and touches done_file when it's done. cancel IPC
clears it without writing a selection.
The plugin has keepLoaded: true so the layer-shell window survives
between summons within a single shell session.
Lock screen
Session-lock surface using Quickshell's native WlSessionLock and two
separate PAM services: omarchy-lock-password for password auth and,
only when fingerprints are enrolled, omarchy-lock-fingerprint for
fingerprint auth. It mirrors the previous lock screen field dimensions,
colors, blurred wallpaper, placeholder, and Hyprland-driven corners.
Polkit agent
Theme-aware authentication dialog for privileged actions. It uses
Quickshell's native Quickshell.Services.Polkit.PolkitAgent backend and
runs inside the long-lived omarchy-shell process, replacing the old
polkit-gnome-authentication-agent-1 autostart.
Omarchy menu
Quickshell-powered Omarchy command menu.
The menu UI lives in menu/Menu.qml as a first-party menu plugin and is
summoned through the shell (omarchy-shell shell summon omarchy.menu ...),
so it shares the long-running omarchy-shell process instead of starting a
second Quickshell instance.
The menu definition lives outside the shell host code:
- defaults:
default/omarchy/omarchy-menu.jsonc - user extensions:
~/.config/omarchy/extensions/omarchy-menu.jsonc
The shell parses both JSONC files at startup (with watchChanges: true
so edits take effect without a restart), evaluates when: / checked:
bash expressions in a single batched subprocess, and executes the
selected action: string directly via Quickshell.execDetached. The
long-running shell process keeps the parsed menu in memory, so the
keybind → IPC → visible path costs ~30ms cold.
Coming soon
omarchy.theme-switcher— folds theme switching into the shell.