Skip to main content
hyprbaric
GitHub

Configure hyprbaric

Settings window

What each tab of hyprbaric’s settings window writes, and the behaviour that is not visible from the window itself.

The settings window is the interactive half of hyprbaric’s configuration. Open it from the bar menu or with Bar settings (Super + Shift + C).

Five tabs map onto a TOML table each, and a sixth, About, reports the build and the host capabilities it detected. Configuration surfaces pairs every tab with the table it writes, and the rest of that page gives the accepted values and defaults. This page covers only what the window decides on top of that.

The About tab can also reopen the setup guide. Finishing or skipping that guide is remembered, while reopening it from Settings remains available without changing its automatic-startup policy.

Appearance​

Restore defaults rewrites all five appearance keys, not only the one you last changed.

Changing the position moves the layer-shell exclusive zone, so Hyprland reflows tiled windows around the new edge.

The monitor selector can keep the bar on the primary display, place one bar on every connected display, or target a named display reported by GTK. Every display uses its own layer-shell surface while sharing the same application backend. If a named display is disconnected, the bar falls back to the primary display and returns when that display reconnects.

Modules​

Hiding a module removes it from the bar and nothing else. The backing service keeps running, so its global shortcuts continue to work and notifications are still recorded while the indicator is hidden.

System occupancy is on until you hide it. It places the CPU and memory chip to the left of the tray.

Global menu is the exception in spirit: enabling it also owns the AppMenu registrar name, so applications export their menus instead of drawing them. Qt works after a restart; Firefox, traditional GTK menus, and Swing need extra setup documented in Global menu.

Display​

Night light needs hyprsunset and hyprctl on PATH. Without them the tab reports the capability as unavailable, and the state you set is still persisted for the next launch.

Temperature is committed explicitly rather than on change, and 0 is rejected in place with Temperature must be above 0K instead of being written.

Display brightness is not configured here. It is adjusted from the Audio & Display popup or the brightness shortcuts, and its polling and DDC policy is TOML-only, in [brightness].

Keybinds​

  • Record writes the captured chord to the action’s table.
  • Disable writes state = "disabled". The action keeps working in the bar and loses only its hotkey.
  • Reset removes the action’s table, so the built-in default applies again.

See Shortcuts for the action list, the defaults, and what happens when a chord is already taken.

What the window does not cover​

The TOML-only runtime cadences have no GUI equivalent, and neither does session-only state such as do-not-disturb, caffeine, and volume. Not configurable in TOML draws the whole boundary.