haus.* options · hausfold

Every option you can set in your host file — types, defaults, and what each one changes.

These are the haus.* options you set in your host file at ~/.config/nix/hosts/<hostname>/default.nix. Everything here is optional unless noted; the defaults are a complete, working system.

The page is grouped by room — the same rooms the sidebar is organised around — and each room lists the haus.* namespaces it owns. A room can own more than one: the Bar room is haus.sill (its own bar) and haus.menuBar (macOS's).

Apply changes with haus rebuild. Each option lists its type and default under its name, and links to the file that declares it.

Apps

The apps a finished machine has: the curated picks, the packs that switch a whole set on in one line, the file types they claim, App Store policy, and what a rebuild does to anything you installed by hand. The list they all land in is haus.roster, a shared surface below.

haus.appStore

Whether a rebuild may install the roster's appStoreId entries. Off by default: it reaches the network and acts on your Apple Account, and it can never be complete — mas cannot sign in, and cannot buy a paid app.

`haus.appStore.install`

boolean · default false

Install roster entries that set appStoreId from the Mac App Store during activation, skipping any already installed.

Off by default: this reaches the network and acts on your Apple ID, which shouldn't happen as a side effect of turning on a window manager. It also can't be complete — mas cannot sign in (do that once in App Store.app) and cannot make a first-time PURCHASE, so a paid app you don't already own is reported and skipped rather than installed.

Deliberately NOT nix-darwin's homebrew.masApps: that runs mas install through brew bundle as your user, and since macOS 13 the App Store install path requires root — so it stops for a password prompt that a rebuild has no terminal to show, and the rebuild hangs. The activation step this option enables is already running as root, so it neither prompts nor wedges.

Declared in modules/options.nix.

haus.apps

The apps haus picks for you, the saved collections you can switch on in one line, and the file types they claim — the ones a finished machine has rather than the ones a room needs to work. Each is one switch you can turn off; what it installs is a roster entry like any other, so you can retune or replace it by app id.

`haus.apps.packs.writing.enable`

boolean · default false

Install the writing collection: Obsidian, Zotero, Anki and calibre — a Mac that reads and writes rather than compiles.

These arrive as ordinary roster entries at mkDefault, so anything you say about one of them in your own host file wins per FIELD and the rest of the entry survives:

haus.roster.zotero.key = "y"; # a letter of your own haus.roster.obsidian.appId = "…"; # osascript -e 'id of app "Obsidian"'

Two of them claim a leader letter (o, l, k) and none claims a workspace — a workspace names its own members, so give one to Obsidian in your host with haus.workspaces. The file is modules/apps/packs/writing.nix, and it is readable data: four casks and the keys to reach them.

Example:

true

Declared in modules/apps/options.nix.

`haus.apps.videoPlayer.claimFileTypes`

boolean · default true

Make IINA the default handler for the everyday video extensions — mp4, m4v, mov, mpg, mpeg, mkv, webm, avi, wmv, flv, 3gp, ogv, vob — so double-clicking a video opens IINA instead of QuickTime Player, TV or a browser. Ignored unless the player is installed.

A short list on purpose: it covers what you actually double-click, not everything IINA can decode. Dead, professional and DRM'd containers (qt, divx, asf, f4v, 3g2, ogm, rm, rmvb, mxf, dv, …) are left alone — they still play via Open With, they just don't get the default, and every extension haus claims is a binding it re-asserts on every rebuild.

Video only. Audio (mp3, flac, m4a, wav, …), .gif and playlists keep whatever owns them today, since "open videos in IINA" rarely means "and my music library too". The transport-stream extensions .ts, .mts and .m2ts are excluded too: on a developer's machine they are TypeScript far more often than video, and haus.hearth.hijackFileAssociations claims them for the editor. Claiming them here as well made macOS stop and ask which app should win on every single rebuild, because .mts and .m2ts share one UTI.

This sets the USER default (via duti) — the same record Finder's Get Info ▸ Change All writes, so it is undoable by hand. Set false to install the app and leave every association alone.

Declared in modules/apps/options.nix.

`haus.apps.videoPlayer.enable`

boolean · default false

Install IINA — haus's video player — as the roster entry iina. A nixpkgs build, so it lands in ~/Applications/Home Manager Apps rather than /Applications.

The nebelhaus desktop turns this on, because macOS ships QuickTime Player, which refuses most of what you actually double-click (mkv, webm, and anything not in Apple's codec list) — so "a video player that plays videos" is part of what that desktop considers a finished machine. The bare layer installs nothing you didn't ask for.

Set false and nothing is installed or rebound — bring your own player via the pounce "Install App" palette command or a roster entry. Once on it is a roster entry like any other: give it a leader letter with haus.roster.iina.key, or pin a different build with haus.roster.iina.package.

Declared in modules/apps/options.nix.

haus.homebrew

How rebuilds treat Homebrew packages you did not declare.

`haus.homebrew.autoUpdate`

boolean · default false

Run brew update before activating the Homebrew step on every rebuild. Off by default — reproducible rebuilds shouldn't silently pull newer formulae. Turn on if you want brew to track upstream.

Declared in modules/den/options.nix.

`haus.homebrew.cleanup`

one of "none", "uninstall", "zap" · default "none"

How darwin-rebuild switch treats Homebrew casks/brews that are installed but NOT declared anywhere in your config.

"none" (default, safe): leave undeclared formulae/casks alone. haus never deletes apps you installed yourself.
"uninstall": remove undeclared formulae/casks (keeps their data).
"zap": remove undeclared formulae/casks AND their app data. Fully declarative, but a stray cask you forgot to list is deleted — with no backup — on the very next rebuild. Only choose this once every app you keep is declared (bootstrap can adopt your current casks).

Declared in modules/den/options.nix.

`haus.homebrew.upgrade`

boolean · default false

Upgrade outdated Homebrew packages on every rebuild. Off by default for the same reproducibility reason as autoUpdate.

Declared in modules/den/options.nix.

Appearance

How the machine looks: the palette and its accent, the wallpaper, the fonts, and the macOS surfaces that follow them — motion, screenshots, sound and the accessibility keys. The interface scale every room reads is haus.ui, a shared surface below.

haus.appearance

The Appearance room's own profile — one named answer to a whole-machine question, where the groups below are the individual dials. largePrint sets the interface scale, the high-contrast palette, macOS's own contrast lift and the screen's scaled resolution together, each as a default you can still pin by hand.

`haus.appearance.largePrint`

boolean · default false

Make everything haus controls bigger and sharper, in one line. Deliberately NARROW: it is about seeing, not about who you are, so it says nothing about which rooms you run — set it in any desktop, or in your host on top of one.

It moves four things, each as a DEFAULT, so pinning any single one by hand still wins — with one asymmetry worth knowing: a DESKTOP that sets one of the four beats this profile even when the profile was switched on in your host, because the desktop's values sit above a room's defaults in the priority ladder. Set the value itself in your host to settle it:

haus.ui.scale = 1.4 the terminal font (19 → 27 pt), the whole command palette, the bar's type (to its ceiling, see below), Dock icons 48 → 67, Finder's large sidebar rows, prowl's gaps haus.theme.contrast = "high" body text 11.3:1 → 19.9:1 against the background, across every tool haus colours. Measured in nebelung's CI. haus.accessibility.increaseContrast = true the same lift for NATIVE macOS apps, which the palette cannot reach. FDA-gated at the option, so it sharpens the result where it applies and is skipped where it doesn't. haus.displays.main.uiScale = "larger-text" one step of the screen's scaled resolution toward larger text. The only line here that reaches apps haus has never heard of, because it changes what a point MEANS.

main rather than internal on purpose: on a laptop they are the same panel, but on a Mac mini or a clamshelled MacBook internal matches nothing — so keying on the built-in panel would quietly do nothing on the desk setup most likely to need this. Name a specific monitor by UUID in your host file for per-display control; hausdisp list prints them.

What it does NOT move, stated here because a large-print machine that quietly under-delivers is worse than one that says where it stops:

macOS's own text-size setting. universalaccess's FontSizeCategory key stores a value and posts no change notification, so apps never re-read it. Display scaling is the lever that works.
Third-party apps' own font settings. Nothing outside haus follows ui.scale — they follow the display, which is why the line above matters.
The perch shelf, which sizes itself from the screen because it hangs off the notch. Scaling the display shrinks its width in points by exactly the factor that makes a point bigger.
The menu bar's HEIGHT. Its type grows to a 1.25x ceiling and stops: 36pt of bar with 28pt pills is what keeps them inside the 32pt band macOS's own hover-reveal covers, and that band is macOS's. The lever that does move it is the display scaling above.
A more legible FONT FAMILY, which is a choice rather than a limit. A typeface is taste and a legibility profile should not decide yours; Atkynson Mono is Atkinson Hyperlegible's monospaced sibling, drawn by the Braille Institute for exactly this problem:

haus.fonts.mono.packageName = "nerd-fonts.atkynson-mono"; haus.fonts.mono.name = "AtkynsonMono Nerd Font";
Light mode, if it reads better for you: haus.theme.flavor = "latte".

Example:

true

Declared in modules/appearance/options.nix.

haus.theme

Colour: the palette's flavour and contrast, the accent every themed tool spends, and whether macOS's own Light/Dark follows it.

`haus.theme.accent`

one of "rosewater", "flamingo", "pink", "mauve", "red", "maroon", "peach", "yellow", "green", "teal", "sky", "sapphire", "blue", "lavender" · default "mauve"

The accent colour, by Catppuccin name (the Nebelung palette is a grey-tinted Catppuccin, so the fourteen names are the same in both flavors — the hue you pick follows haus.theme.flavor). It recolours the tools nebelhaus injects colours into — lazygit, fzf, yazi (including glow-rendered Markdown headings), and the Zen browser — via the matching Nebelung per-accent ports.

perch follows it too, and is the one surface handed the NAME rather than a hex: the shelf resolves it against whichever half of its dark/light pair macOS is showing, so the ember under the notch and a pinned tile wear this accent in both polarities from one key. Left at perch's default it accents with its own mark green.

Three more things follow it: the generated desktop (the bloom behind the mark in minimal, and the whole sweep in bold — see haus.wallpaper.style), any roster app whose Nebelung port ships a per-accent matrix (zed, gh-dash, mpv), placed by haus.theme.ports, and the bar's far-left logo pill. Those ports name the theme file after the accent, so changing the accent renames the file the app's own theme key points at — re-pick it in the app, or it falls back to stock.

The bar is the newest and the narrowest of the three: haus.sill.logo is the ONLY pill that follows this option. Every other colour on the bar is a fixed palette key, and the palette itself doesn't move — so a machine that changes its accent sees exactly one pill change hue, unless haus.sill.logo.color names one of its own.

Honest scope: this moves the accent on those tools, NOT literally everything. Single-file dotfiles that bake the palette at their own theme slot (ghostty, starship, tmux, bat, zellij, …) keep their built-in colour and don't follow this option. The base palette stays the same Nebelung grey either way — only the accent hue changes.

Zen means Zen's own UI, and the web is a separate story. haus places the Nebelung userChrome/userContent pair, but userContent only styles about: pages — github.com and youtube.com are themed by the Stylus extension, whose Catppuccin-derived styles carry their OWN accentColor var (default mauve) inside the extension's storage, where no stylesheet can reach it. Declare haus.zen.extensions.stylus and haus stamps that var with this accent and tells you, once, when there's a new bundle to import; the import itself stays a click, because Stylus has no file interface. Until you make it, the web keeps the accent you last imported.

Both halves of that are pinned by the accent-reach flake check, which fingerprints every surface under three accents and fails if one starts or stops following the accent without anyone deciding it should.

Example:

"sapphire"

Declared in modules/theme/options.nix.

`haus.theme.contrast`

one of "normal", "high" · default "normal"

How far the interface separates from its background.

"high" swaps in the Nebelung high-contrast palette: the same hues and the same accents, with the neutral ramp pulled apart in OKLCH so text and background separate further at every step. Measured rather than eyeballed — body text goes from 11.3:1 to 19.9:1 against the base, clearing WCAG AAA (nebelung's own CI asserts it).

Composes with flavor, and the boost is tuned per flavor rather than shared: light mode has far less room above its background before the ramp clips to white, so latte goes 7.0:1 → 9.9:1 where mocha goes 11.3 → 19.9. Both keep all twelve ramp steps distinct, which is the property nebelung's tests actually assert.

Honest scope. This recolours what haus injects colours into: Ghostty, bat, delta, lsd, yazi, zellij, glow, starship, lazygit, the bar, pounce and perch (at runtime, via ~/.config/{pounce,perch}/themes/ — and unlike flavor, contrast reaches both on BOTH halves of their light/dark pair), Zen and Obsidian. It does NOT reach:

macOS itself. For system-wide contrast see haus.accessibility.increaseContrast — a separate, FDA-gated setting. The two are complementary, and a genuinely high-contrast machine wants both.

Example:

"high"

Declared in modules/theme/options.nix.

`haus.theme.flavor`

one of "mocha", "latte" · default "mocha"

Light or dark. "mocha" (the default) is the dark half of Nebelung, which is what haus has always shipped; "latte" is light mode.

Not an inversion of the dark palette — a different SOURCE palette. Nebelung is "Catppuccin with the blue stripped out", and those rules say nothing about dark, so they apply to Catppuccin Latte just as well: same warm-grey neutral ramp, same calmed accents, the other polarity. Light mode lands at 7.0:1 for body text on its own, so it's legible before you reach for contrast = "high" (which takes it to 9.9:1).

It composes with contrast: the two axes give four palettes, and nebelung's CI measures each one's contrast ratio rather than eyeballing it.

Honest scope, in two parts.

What follows it: every tool haus injects colours into or points at a rendered theme — Ghostty, bat, delta, lsd, yazi, fzf, glow, starship, lazygit, zellij, opencode, the bar, Zen and Obsidian, plus helix whenever it is the editor haus.hearth.editorName selects (Nebelung has a port for helix and none for the alternatives). These are genuinely re-rendered for the flavor, not recoloured in place: whiskers takes different branches for a light flavor (terminal ANSI 0/7/8/15 swap, Zen switches its prefers-color-scheme block, delta sets light = true).

What does NOT follow it:

pounce and perch, by default. Both read their palette at runtime and can pick per polarity, so haus.pounce.followSystemAppearance and haus.perch.followSystemAppearance (default true) hand that choice to macOS Light/Dark instead: haus installs every rendered variant into ~/.config/{pounce,perch}/themes/ and writes the dark/light PAIR at your contrast. Set either option false to pin that app to this flavor like everything else.
macOS's own Light/Dark appearance, unless you opt in with haus.theme.systemAppearance = "flavor". Left at its default haus does not touch system appearance in either direction, so latte on a dark macOS looks half-done and that half is yours — except in pounce and perch, which read the appearance themselves.
three of the six desktops (haus.wallpaper.style). The hand-made "orbits", "constellation" and "flow" have the dark palette baked into their pixels; "bold" is generated but follows theme.accent rather than the flavor. "minimal" DOES follow it, in every part — field, mark, glow and debug band.

Example:

"latte"

Declared in modules/theme/options.nix.

`haus.theme.ports.enable`

boolean · default false

Theme the apps in your roster (haus.roster) that Nebelung ships a port for, without wiring each one by hand.

haus already themes every tool it installs itself — the shell, the terminal, the git stack, Zen, Obsidian. This covers the other direction: an app YOU added to the roster that Nebelung happens to have a theme for. Add zed, warp or xcode to haus.roster and its Nebelung theme lands where that app looks for themes, in the flavor and contrast you selected, following them on every rebuild. Matching is by roster id, so the entry has to be named after the port (zed, not zed-editor).

Honest scope, and it is the whole point of the option: this drops the theme FILE. Whether that alone makes the theme active is the app's choice, not ours, and Nebelung records which is which per port. Ghostty reads a config key we own, so it just works. Xcode, Warp, OBS and friends offer no file interface for picking a theme — the file is put where they look, and the one click that selects it stays yours. haus doctor lists exactly which apps are waiting on that click, so the difference is visible rather than something you discover months later.

Ports whose install is a merge into an existing config file, or that need a compile step first, are reported but never written: silently half-applying someone's config is worse than saying so.

Declared in modules/theme/options.nix.

`haus.theme.systemAppearance`

one of "unmanaged", "flavor", "light", "dark" · default "unmanaged"

Whether haus also sets macOS's OWN Light/Dark appearance — the one in System Settings ▸ Appearance, which paints Finder, the menu bar and every native app haus can't reach.

unmanaged (default) leave it alone, in both directions. Your Mac's appearance stays yours; nothing about a rebuild moves it. flavor follow haus.theme.flavor — latte sets Light, mocha sets Dark. This is the one that makes light mode complete rather than half-done. light pin Light, whatever the flavor is. dark pin Dark, whatever the flavor is.

Default "unmanaged" on purpose: a managed default would silently revert an appearance you picked in System Settings on the next rebuild, which is a worse surprise than a half-light machine.

How it is applied, and why it is not a system.defaults key. Measured on macOS 26.6 (2026-08-08), NOT recalled from docs: NSGlobalDomain.AppleInterfaceStyle is INERT in both directions. Writing "Dark" from a light session does nothing; deleting the key from a dark one does nothing; activateSettings -u does not help; a process launched fresh afterwards still reports the old appearance, and no AppleInterfaceThemeChangedNotification is posted. That key is a mirror the appearance system writes, not a lever. So haus drives appearance through System Events (AppleScript) at each home-manager activation, which does flip it live in ~0.3s — and confirms the result with hausax (AppKit's effective appearance), never by reading the key back.

Reachability, the same shape as haus.accessibility.increaseContrast: driving System Events needs an Automation grant for whichever app runs the rebuild (System Settings ▸ Privacy & Security ▸ Automation). Without it macOS refuses, the rebuild says so in a named warning and carries on — the appearance just doesn't move, and nothing else is affected.

One more thing macOS can undo: System Settings ▸ Appearance ▸ Auto switches polarity on its own schedule. haus sets the appearance at rebuild time and does not fight it afterwards, so on an Auto machine this option holds only until the next scheduled switch. Pick Light or Dark there if you want it to stick.

Interaction worth knowing: haus.{pounce,perch}.followSystemAppearance hand polarity to macOS. Set this to "flavor" and macOS's polarity is in turn haus's, so those two end up following flavor transitively — which is usually what you wanted, but it does mean followSystemAppearance stops being an independent axis on this machine.

Example:

"flavor"

Declared in modules/theme/options.nix.

haus.wallpaper

The desktop behind everything. minimal is generated on this machine — a flat field at whatever depth you pick out of the palette, the haus mark ⌂ at its centre, a bloom in your accent, and enough grain that none of it bands. The other looks are the hand-made Nebelung ones.

`haus.wallpaper.background`

null or string matching the pattern #[0-9a-fA-F]{6} · default null

The field colour, as a literal hex — an escape hatch out of the palette for a desktop that wants a colour Nebelung doesn't have.

Null (the default) resolves it from haus.wallpaper.depth against the flavour's ladder, which is the arrangement that keeps following the theme. Setting this pins the field and depth stops meaning anything.

Example:

"#0b0b0e"

Declared in modules/wallpaper/options.nix.

`haus.wallpaper.debug.enable`

boolean · default false

Print this machine's lock edges in the bottom-left corner — which revision of each family repo the running system was built from.

It is a detail rather than a readout. It sits at exactly the inset a tiled window covers (see debug.inset), so it is invisible the moment anything is on screen and only ever surfaces on a bare desktop; it is set small, dim and wide-tracked; and it names four repos rather than everything the flake pins. Off by default.

Example:

true

Declared in modules/wallpaper/options.nix.

`haus.wallpaper.debug.inputs`

list of string · default [ "self" "nebelung" "pounce" "perch" "holt" ]

Which flake inputs the band names, in the order it prints them. self is haus itself and prints as haus; every other entry is an input name out of haus's own flake, and one that isn't there is skipped rather than failing the build.

The default is the family chain, which is the one thing a rev is worth knowing on a desktop: it's what bench status calls the lock edges, and the answer to "is this machine running the branch I just merged".

Example:

[
  "self"
  "nixpkgs"
]

Declared in modules/wallpaper/options.nix.

`haus.wallpaper.debug.inset`

null or (unsigned integer, meaning >=0) · default null

How far in from the bottom-left corner the band sits, in PICTURE PIXELS.

Null derives it from the tiling gaps — the widest outer reservation any attached display could be using (../lib/gaps.nix, the same numbers prowl writes into aerospace.toml), doubled for a Retina display's two pixels per point. That lands the band exactly at a tiled window's bottom-left corner, which is the whole trick: the text is under the windows, not beside them, so a tiled desktop hides it completely and a bare one doesn't.

Set a number if your display isn't 2× — or if you'd rather see it.

Example:

Declared in modules/wallpaper/options.nix.

`haus.wallpaper.debug.size`

integer or floating point number between 0.002 and 0.1 (both inclusive) · default 0.011

The band's type size, as a fraction of the picture's short edge. It is set in haus.fonts.mono, so the desktop and the terminal in front of it are the same typeface.

Example:

0.02

Declared in modules/wallpaper/options.nix.

`haus.wallpaper.depth`

integer between 0 and 5 (both inclusive) · default 1

How far in from the palette's outermost tone the field sits — the answer to "I want it blacker" without anyone having to name a colour.

Nebelung's background tones are a ladder of six, ordered here from the end nearest the polarity's extreme inwards, so the SAME number means the same distance from black in a dark flavour and from white in a light one:

depth dark (mocha) light (latte) 0 crust #121212 base #f1f1f1 1 mantle #191919 mantle #e9e9e9 ← default 2 base #202020 crust #e0e0e0 3 surface0 #343434 surface0 #d0d0d0 4 surface1 #494949 surface1 #c0c0c0 5 surface2 #5c5c5c surface2 #b0b0b0

0 is as far out as the palette goes — our blackest black, our whitest white. The default of 1 lands exactly one rung inside that extreme in EITHER polarity, which is what keeps the desktop reading as material rather than as a hole cut in the screen while still being properly dark in a dark flavour — a full screen of base reads as a big terminal window, not as a wall behind one.

The two columns are NOT symmetric, and the asymmetry is the palette's rather than a choice: mocha's canvas (base) sits at depth 2 because two tones are darker than it, while latte's canvas is the LIGHTEST tone it has, so it sits at depth 0. So the ONE number moves the two flavours in opposite directions relative to their canvas — the default puts a dark flavour one step BELOW the colour its terminal draws on (#191919) and a light one one step below the canvas too (#e9e9e9), which is the agreement worth having, since a full screen of near-white is the one field size where latte's canvas stops being comfortable. depth = 0 is the way to match the terminal exactly in a light flavour; depth = 2 is the way to match it in a dark one.

Which flavour's column applies follows haus.theme.flavor, like every other themed surface. haus.wallpaper.background overrides the whole thing with a literal hex.

Example:

Declared in modules/wallpaper/options.nix.

`haus.wallpaper.glow.color`

null or string matching the pattern #[0-9a-fA-F]{6} · default null

The colour the bloom tends towards at its centre. Null takes haus.theme.accent's hex, which is what makes the desktop change temperature with the accent without anyone wiring a second colour.

Example:

"#8db4f3"

Declared in modules/wallpaper/options.nix.

`haus.wallpaper.glow.enable`

boolean · default true

A single broad bloom behind the mark, so the field reads as lit rather than as a fill. Subtle by construction — see glow.strength.

Declared in modules/wallpaper/options.nix.

`haus.wallpaper.glow.spread`

integer or floating point number between 0.2 and 4.0 (both inclusive) · default 1.15

The bloom's diameter, as a multiple of the picture's long edge. Above 1 its falloff runs off the edges and the field reads as evenly lit from the middle; below 1 it closes into a halo around the mark.

Example:

0.6

Declared in modules/wallpaper/options.nix.

`haus.wallpaper.glow.strength`

integer between 0 and 100 (both inclusive) · default 3

How much of the bloom is mixed into the field, as a percentage.

Small numbers on purpose: at 3 the accent is a few levels of lift you'd struggle to name and would miss if it went. Past ~25 it stops being light on a wall and starts being a coloured wallpaper, which is a different desktop than this one. (Was 7 until it turned out to read as the field simply not being dark enough, rather than as a glow.)

Example:

Declared in modules/wallpaper/options.nix.

`haus.wallpaper.grain`

integer or floating point number between 0.0 and 0.1 (both inclusive) · default 0.01

Film grain over the whole field, as a fraction of full scale — and the reason the glow doesn't band.

This is dither, dressed as texture. A soft glow across two thousand pixels spends perhaps ten of the 256 levels an 8-bit PNG has, so it quantises into visible contour rings — the "steppy gradient" every hand-made wallpaper picks up on the way out of an image editor. Noise of a couple of levels, added BEFORE the render is reduced to 8 bits, breaks those contours into something the eye integrates back to smooth. 0.004 is enough to hide them; the default is comfortably past that.

0 turns it off. Do that only with glow.enable = false too — a glow on an ungrained field is exactly the picture this exists to prevent.

Measured at the shipped defaults (3456x2234), since the effect is easier to state in numbers than to argue about — distinct colours, and what the PNG costs, noise being the one thing that doesn't compress:

grain colours size 0 137 0.1 MB ← rings, visibly 0.004 193 1.1 MB ← the floor worth using 0.010 329 2.5 MB ← the default 0.020 625 4.2 MB

Example:

0.0

Declared in modules/wallpaper/options.nix.

`haus.wallpaper.mark.color`

one of "muted", "ink", "accent", "spectrum" · default "spectrum"

What the mark is drawn in.

muted the palette's overlay1 — present, not loud. The mark as it sits on hausfold.co untouched. ink the palette's text colour, for a mark meant to be read rather than noticed. accent haus.theme.accent's hex, flat. spectrum the whole family at once: a conic sweep through the six product accents — nebelung, holt, perch, trill, pounce, nebelhaus — clipped to the stroke. This is the ⌂ as it looks with a pointer on it on hausfold.co, held still.

spectrum is the default, and follows the flavour like everything else: the six are the Nebelung pastels in a dark flavour and their darker counterparts in a light one, because a pastel sheen on a white wall is invisible. It is the loudest of the four on purpose — one small piece of colour is the whole of what this desktop says out loud, and it says the family rather than any one product. muted is the quiet way back, and mark.opacity turns the sweep down without leaving it.

Example:

"muted"

Declared in modules/wallpaper/options.nix.

`haus.wallpaper.mark.enable`

boolean · default true

Draw the haus mark ⌂ at the centre. Off leaves the field, the glow and the grain — which is a perfectly good desktop, and the fastest way to get one flat colour that still isn't flat.

Declared in modules/wallpaper/options.nix.

`haus.wallpaper.mark.opacity`

integer or floating point number between 0.0 and 1.0 (both inclusive) · default 1.0

The mark's opacity over the field. Worth reaching for with spectrum — the default, and the one colour here loud enough to want turning down.

Example:

0.55

Declared in modules/wallpaper/options.nix.

`haus.wallpaper.mark.rise`

integer or floating point number between -0.5 and 0.5 (both inclusive) · default 0.0

How far above centre the mark sits, as a fraction of the picture's height. Optical centre is a little above geometric centre, and a bar along the top edge moves it further — a small positive number is the usual correction.

Example:

0.06

Declared in modules/wallpaper/options.nix.

`haus.wallpaper.mark.size`

integer or floating point number between 0.01 and 0.9 (both inclusive) · default 0.1

The mark's height, as a fraction of the picture's SHORT edge — so it keeps its proportion whatever size and whatever display.

Example:

0.3

Declared in modules/wallpaper/options.nix.

`haus.wallpaper.mark.weight`

integer or floating point number between 0.005 and 0.25 (both inclusive) · default 0.09

Stroke width, as a fraction of the mark's own height.

The mark's SHAPE is the real U+2302, traced off the outline hausfold.co renders, and the default weight is now the site's too: that glyph's stems are a tenth of its height, which is 0.094 here once the miter at the apex is counted, and 0.09 is that within a hair. So the desktop and the site draw the same mark, which is the agreement worth having when the two sit side by side.

It used to default to 0.055 — a little under 60% of the glyph's own weight — on the grounds that a stem which reads right in a line of type is heavy drawn a foot wide on a wall. That is true of a mark filling the screen; it is not true of one at mark.size, where the lighter stroke reads as a hairline rather than as the ⌂. Go back to it if you want the outline to recede.

Example:

0.055

Declared in modules/wallpaper/options.nix.

`haus.wallpaper.size`

string matching the pattern [0-9]+x[0-9]+ · default "3456x2234"

The pixel size minimal is rendered at, WIDTHxHEIGHT.

Set it to your display's NATIVE pixel count and macOS has nothing left to do: the picture lands one image pixel per screen pixel, which is the only arrangement where the grain that keeps the glow smooth survives at the size it was dithered for. Anything else is resampled, and resampling is where a gradient that was clean in the file starts to look stepped.

The default is the 16" MacBook Pro panel — the largest built-in Retina display, so a smaller one scales DOWN (soft, harmless) rather than up. system_profiler SPDisplaysDataType prints yours.

Aspect matters as much as size: macOS fills the screen and crops the overflow, so a picture narrower than the display loses its top and bottom — which is where debug draws. On a display of a different shape, set this to that display's own numbers.

Example:

"3024x1964"

Declared in modules/wallpaper/options.nix.

`haus.wallpaper.style`

one of "none", "minimal", "orbits", "constellation", "flow", "bold" · default "none"

Which desktop this machine wears, set at each home-manager activation (osascript, every desktop on the current Space).

minimal GENERATED here — a flat field in your palette, the haus mark ⌂ at its centre, and nothing else. The one haus-themed look, and the one every option below tunes. orbits hand-made Nebelung PNGs, the palette baked into their constellation pixels — they do not follow haus.theme.flavor. flow bold generated from haus.theme.accent alone (a diagonal accent→crust sweep), which predates minimal.

The default is none, and it is a real value rather than an absence: nothing here runs and whatever wallpaper you already have stays exactly where it was. Replacing someone's desktop picture is the most visible thing this layer can do, so the bare room does not do it uninvited — a DESKTOP says which look it wants, and nebelhaus picks minimal.

That is the second change of mind on this option, and the reasoning survives both: minimal was made the default so a desktop wouldn't ship looking like nothing in particular, which is still true of nebelhaus and is why its desktop sets it. What changed is that a desktop is now the thing making that choice, rather than every install of the layer.

Every option below tunes minimal, and all of them keep their tuned values — the choice being opt-in is not a reason for the look to be worse once chosen.

Example:

"minimal"

Declared in modules/wallpaper/options.nix.

haus.fonts

The terminal font. The bar keeps its own font at its own tuned sizes.

`haus.fonts.mono.baseSize`

positive integer, meaning >0 · default 13

The terminal-font baseline, before haus.ui.scale multiplies it. The neutral room uses 13pt; nebelhaus selects 19pt in its desktop.

This exists so a desktop can carry that tuned baseline WITHOUT breaking the scale relationship. Setting size directly pins an absolute number, which would make haus.ui.scale (and haus.appearance.largePrint, built on it) stop moving the terminal font at all — a silent regression, since everything else would still grow. Say the baseline here; say the exception with size.

Example:

Declared in modules/den/options.nix.

`haus.fonts.mono.name`

string · default "JetBrainsMono Nerd Font Mono"

haus's type family, as Ghostty's font-family names it.

It reaches the terminal AND the menu bar: every pill label and icon sill draws is in this family, at sizes of its own (see haus.ui.scale). The workspace-logo glyphs are the one exception — those are sketchybar-app-font, which sill installs itself.

This should be a NERD FONT patched build: starship's prompt, lsd's icons, yazi previews and half the bar's icons draw with glyphs a stock font renders as tofu. If you change this, set package (or packageName) too — haus can only install a font it's been given, and it warns when you name a family without one.

The name is taken verbatim, so a "… Nerd Font Mono" family is drawn in the bar as well: the bar mixes icon glyphs into its labels, which is the same reason the terminal wants a patched font.

Example:

"Berkeley Mono"

Declared in modules/den/options.nix.

`haus.fonts.mono.package`

null or package · default null

The package providing name. null (the default) installs haus's own JetBrains Mono Nerd Font, which is what name defaults to.

Set this whenever you change name, or the family simply won't exist on the machine and Ghostty will silently fall back — haus warns if it spots that combination.

A shared desktop can't set this one — it needs pkgs, and a data-only desktop has no arguments. Use packageName there.

Example:

pkgs.nerd-fonts.fira-code

Declared in modules/den/options.nix.

`haus.fonts.mono.packageName`

null or string · default null

The same thing as package, NAMED rather than evaluated: an attribute path into nixpkgs, so "nerd-fonts.fira-code" means pkgs.nerd-fonts.fira-code.

This exists so a data-only desktop or app pack can change the font FAMILY and not just its size — reaching pkgs is precisely what those formats forbid, which made fonts.mono.package unreachable to every shared file. A name is data; a package is code.

Set one or the other, never both. A name that resolves to nothing, or to a set of packages rather than a package, fails at eval with the spelling to try instead.

Example:

"nerd-fonts.fira-code"

Declared in modules/den/options.nix.

`haus.fonts.mono.size`

positive integer, meaning >0 · default fonts.mono.baseSize, scaled by haus.ui.scale and rounded

Terminal font size in points. The single most useful knob for a larger-text machine, since it moves everything haus actually lives in.

nebelhaus's 19pt baseline exists for a reason worth knowing: the Ghostty window is tiled to a fixed pixel height by prowl, and sizes that don't divide that height evenly used to leave a gap under zellij's status bar. That's since been fixed properly (window-padding-balance + extend-always), so any size is safe now — 19 is simply the tuned starting point.

Example:

Declared in modules/den/options.nix.

haus.accessibility

macOS accessibility keys haus can actually apply. These write to a TCC-protected domain, so they take effect only when the app you run the rebuild from holds Full Disk Access — otherwise haus warns and moves on.

`haus.accessibility.closeViewScrollWheelToggle`

null or boolean · default null

Hold ⌃ (Control) and scroll to magnify the whole display. macOS calls it "Use scroll gesture with modifier keys to zoom"; scroll the other way to come back.

The fastest zoom on the Mac and the one people forget exists. Worth having on a machine you demo, present or pair from, where the alternative is asking everyone to lean in.

null (the default) leaves whatever you have alone — this is a personal setting, so haus never picks a value for you.

HOW THIS ONE WAS VERIFIED — by a person looking at the screen on real hardware (macOS 26.6.1, 2026-08-14), because no API reports it: NSWorkspace exposes no pointer size and no zoom state, so hausax cannot read it back and haus diff will tell you it compared the plist and nothing more. haus's other accessibility options are checked against macOS's own answer on YOUR Mac; this one carries evidence from one Mac. That is a real difference and it is worth knowing which kind you are getting — it is written here rather than in a changelog because the option is where you will be standing when it matters.

NEEDS A DAEMON RESTART, which the rebuild does for you: the write alone changes nothing on screen until universalaccessd restarts, which is exactly why this key spent three weeks looking dead. haus rebuild kills it whenever this option family is set, so you should never meet the stale state; set the key by hand with defaults write and you will, with killall universalaccessd as the fix.

REACHABILITY — com.apple.universalaccess is TCC-protected, and this is the one property in the whole option surface that can differ between two machines running byte-identical config, so it is worth reading once. The write lands only when the app that runs the rebuild holds Full Disk Access (System Settings ▸ Privacy & Security ▸ Full Disk Access; on macOS 26 a stale grant often needs removing and re-adding with (+), then restarting the terminal). The grant follows the APP, not you and not root — so an agent-driven rebuild in a pane of a terminal that has it works fine, and the same agent under a different app does not.

Without the grant haus warns and carries on: you lose this setting and nothing else. That containment is the whole reason com.apple.universalaccess has options here at all — written the other way, through system.defaults.universalaccess.*, a missing grant aborts the rest of activation and takes every background service haus installs with it.

haus plan says up front when a rebuild needs the grant, and haus doctor's Permissions section says whether this app has it.

Example:

true

Declared in modules/den/options.nix.

`haus.accessibility.closeViewZoomFollowsFocus`

null or boolean · default null

Keep a zoomed display on whatever has keyboard focus. ⇥ into a field outside the magnified area and the view goes to it — KEYBOARD focus specifically, not the pointer.

Needs a zoom to follow, so it does nothing on its own: pair it with closeViewScrollWheelToggle (or turn on Zoom in System Settings ▸ Accessibility). nix-darwin's own option says the same, and it is the first thing to check if this appears to do nothing.

Expect it to SNAP rather than glide — the view jumps to the focused control in one step. That is the feature behaving, not a rendering fault, and it is the first thing anyone reports as one. Note also that pushing the POINTER at a screen edge pans the zoomed view whether or not this is set: that behaviour is not this option, which matters if you are trying to tell whether it took.

null (the default) leaves whatever you have alone — this is a personal setting, so haus never picks a value for you.

haus plan says up front when a rebuild needs the grant, and haus doctor's Permissions section says whether this app has it.

Example:

true

Declared in modules/den/options.nix.

`haus.accessibility.differentiateWithoutColor`

null or boolean · default null

macOS's "Differentiate without colour" — native UI adds shapes and text where it would otherwise rely on hue alone. The setting to pair with a desktop built for colour-blind readability.

null (the default) leaves whatever you have alone — this is a personal setting, so haus never picks a value for you.

haus plan says up front when a rebuild needs the grant, and haus doctor's Permissions section says whether this app has it.

Example:

true

Declared in modules/den/options.nix.

`haus.accessibility.increaseContrast`

null or boolean · default null

macOS's "Increase contrast" — stronger borders and reduced use of colour alone to convey state, across native apps. This is the system-level companion to a high-contrast nebelhaus theme: the theme restyles the tools nebelhaus colours, this reaches everything else.

null (the default) leaves whatever you have alone — this is a personal setting, so haus never picks a value for you.

haus plan says up front when a rebuild needs the grant, and haus doctor's Permissions section says whether this app has it.

Example:

true

Declared in modules/den/options.nix.

`haus.accessibility.mouseDriverCursorSize`

null or integer or floating point number between 1.0 and 4.0 (both inclusive) · default null

How big the mouse pointer is — 1.0 normal, 4.0 the biggest. That range is macOS's own, and the scale is linear: 2.0 is twice the normal pointer, 4.0 is the largest System Settings offers.

The one accessibility key here that is useful with no accessibility need at all: on a 5K display, or from across a desk, or in a screen recording someone else has to follow, the default pointer is simply too small to find. Set it to 1.5 and you keep noticing you can see it.

Deliberately NOT wired to haus.ui.scale, which would be the obvious thing and is the wrong thing. ui.scale is the foundation every machine gets; this domain needs Full Disk Access. Deriving one from the other would make ui.scale = 1.4 start warning about a TCC grant on machines that never asked for a bigger pointer, for a write that would then be skipped. Reach for this key when you want it — it sharpens a large-text desktop, it does not underpin one.

null (the default) leaves whatever you have alone — this is a personal setting, so haus never picks a value for you.

haus plan says up front when a rebuild needs the grant, and haus doctor's Permissions section says whether this app has it.

Example:

4.0

Declared in modules/den/options.nix.

`haus.accessibility.reduceMotion`

null or boolean · default null

macOS's "Reduce motion" — Spaces cross-fade instead of sliding, Mission Control and the Dock drop their zoom animations, and window minimise/restore is stripped back.

BIGGER THAN IT LOOKS, which is why it is here rather than inside haus.animations. This is the single flag every browser maps to the prefers-reduced-motion: reduce CSS media query, through NSWorkspace.accessibilityDisplayShouldReduceMotion — hausax reads that exact property, so hausax | jq .reduceMotion is how you check it landed. Turning it on rewrites the web: mostly for the better, except on sites whose scroll-reveal animation is what makes the content visible in the first place, which then never appears at all.

If what you want is a snappier Dock and nothing else, haus.animations = "fast" is five plain timing keys in two ordinary domains, moves no accessibility flag, and needs no TCC grant.

null (the default) leaves whatever you have alone — this is a personal setting, so haus never picks a value for you.

haus plan says up front when a rebuild needs the grant, and haus doctor's Permissions section says whether this app has it.

Example:

true

Declared in modules/den/options.nix.

`haus.accessibility.reduceTransparency`

null or boolean · default null

macOS's "Reduce transparency" — the menu bar, Control Center, sheets and sidebars stop sampling what is behind them and go opaque. The setting to reach for if Liquid Glass costs you more legibility than it buys, and it pairs naturally with increaseContrast.

Worth knowing if you run the bar: sill paints its own background, so its pills look the same either way — what changes is the macOS menu bar band behind them, which stops being translucent.

null (the default) leaves whatever you have alone — this is a personal setting, so haus never picks a value for you.

haus plan says up front when a rebuild needs the grant, and haus doctor's Permissions section says whether this app has it.

Example:

true

Declared in modules/den/options.nix.

haus.animations

How much motion macOS spends on its own Dock and windows: the slide, the launch bounce, minimise, Mission Control, window open/close. Unset by default like the rest of this block — "fast" opts in, and going back only stops writing rather than restoring. Deliberately not the Accessibility "Reduce motion" switch, which every browser also reads as prefers-reduced-motion.

`haus.animations`

one of "fast", "system" · default "system"

How much motion macOS spends on its own Dock and windows — how long three animations run, and two it plays at all.

"system" (the default) writes NOTHING — not the macOS values, nothing at all — so whatever your Dock does today, it keeps doing. Same policy as haus.hotCorners: haus doesn't overwrite a setting you didn't ask it about.

"fast" writes five keys, all mkDefault, so any one of them can be overridden by name in your host file:

  com.apple.dock  autohide-time-modifier         0.15   Dock slide
  com.apple.dock  expose-animation-duration      0.1    Mission Control
  com.apple.dock  launchanim                     false  the bouncing icon
  com.apple.dock  mineffect                      scale  minimise (not genie)
  NSGlobalDomain  NSAutomaticWindowAnimationsEnabled  false  window open/close

GOING BACK IS NOT AUTOMATIC, which is the one thing about this group that can surprise you and the reason it isn't on by default. Setting "system" again means STOP WRITING, not RESTORE: a defaults write is sticky and macOS keeps no memory of what was there before, so once you've rebuilt on "fast", the five keys keep haus's numbers. Undoing it means naming the values you want back in your host file (they're mkDefault, so a plain value wins), or a defaults delete. Worth knowing before you try "fast" on a Dock you tuned by hand.

WHY THIS ISN'T "REDUCE MOTION". macOS's accessibility switch of that name (com.apple.universalaccess reduceMotion) would cover all of this and more — but it is also the single flag every browser maps to the prefers-reduced-motion: reduce CSS media query, via NSWorkspace.accessibilityDisplayShouldReduceMotion. Turning it on rewrites the web: mostly for the better, except on sites whose scroll-reveal animation is what sets the content visible in the first place, which then never appears at all. These five keys are in two entirely different domains and move no accessibility flag — hausax reads that exact NSWorkspace property, so hausax | jq .reduceMotion stays false with this set to "fast" (on a machine that hasn't also set haus.accessibility.reduceMotion, which is the option that DOES move it) — that's the whole reason this group exists as five curated keys instead of one switch. If you DO want the accessibility switch, it is haus.accessibility.reduceMotion: a separate option, in a TCC-protected domain, with that blast radius spelled out on it. Setting both is coherent and neither implies the other.

WHEN YOU'LL FEEL IT. The four Dock keys are live the moment activation finishes — nix-darwin restarts the Dock whenever anything in its domain is written, and haus always writes autohide. The NSGlobalDomain one is read by each app AT LAUNCH, so apps you already have open keep animating their windows until you relaunch them; activateSettings can't reach back into a running NSApplication.

These are timings, not a state haus can prove from a plist — unlike the haus.accessibility keys, there's no oracle for "did the Dock slide faster". They're felt, not measured. The one measurable claim here is the negative one above.

Example:

"fast"

Declared in modules/den/options.nix.

haus.screenshots

Where ⇧⌘4 puts its files, in what format, and whether it draws a window shadow or a preview thumbnail. Unset by default, so macOS's own choices stand.

`haus.screenshots.format`

null or one of "png", "jpg", "pdf", "tiff", "heic", "gif" · default null

The image format new screenshots are saved in. null (the default) leaves macOS's own choice alone, which is png.

png is lossless and the right default for UI and text — a jpg screenshot of a terminal has visible ringing around every glyph. jpg is worth choosing only when you screenshot photographs often enough for the file sizes to matter.

Example:

"png"

Declared in modules/den/options.nix.

`haus.screenshots.includeDate`

null or boolean · default null

Whether filenames carry the date and time ("Screenshot 2026-08-03 at 13.37.20.png") or just a counter ("Screenshot 1.png"). null (the default) leaves macOS's own choice alone, which is to include it.

Example:

true

Declared in modules/den/options.nix.

`haus.screenshots.location`

null or string · default null

Where ⇧⌘3 / ⇧⌘4 / ⇧⌘5 write their files. null (the default) leaves macOS's own choice alone, which is the Desktop.

Absolute, or starting with ~/ — haus expands the ~ for you and CREATES the directory during activation. Both halves matter: macOS stores this string verbatim and expands nothing, and if the path does not exist screencapture silently falls back to the Desktop, so a typo'd or not-yet-created folder looks exactly like the setting having been ignored.

Example:

"~/Pictures/Screenshots"

Declared in modules/den/options.nix.

`haus.screenshots.shadow`

null or boolean · default null

Whether a window capture (⇧⌘4 then Space) keeps macOS's big soft drop shadow. null (the default) leaves macOS's own choice alone, which is to include it.

false is the setting to want if screenshots go into documentation: the shadow is transparent padding, so it adds a wide invisible margin that every layout then has to fight. Holding ⌥ while you click suppresses it for one capture either way.

Example:

false

Declared in modules/den/options.nix.

`haus.screenshots.thumbnail`

null or boolean · default null

Whether the floating preview thumbnail appears in the bottom-right corner after a capture. null (the default) leaves macOS's own choice alone, which is to show it.

false writes the file immediately instead of after the ~5s the thumbnail waits around — the setting to want if you screenshot in quick succession, or if you script anything that reads the file. The cost is losing the markup/drag affordance the thumbnail offers.

Example:

false

Declared in modules/den/options.nix.

haus.sound

Alert volume and sound, interface sound effects, and the boot chime. Volume is 0–100 the way the slider reads it — macOS stores a curve, and haus does the conversion.

`haus.sound.alertSound`

null or one of "Basso", "Blow", "Bottle", "Frog", "Funk", "Glass", "Hero", "Morse", "Ping", "Pop", "Purr", "Sosumi", "Submarine", "Tink" · default null

Which sound the alert beep plays, by name:

  Basso  Blow  Bottle  Frog  Funk  Glass  Hero  Morse  Ping  Pop  Purr  Sosumi  Submarine  Tink

null (the default) leaves macOS's own choice alone.

An enum rather than a path on purpose. macOS stores an absolute path here and validates nothing, and a path that doesn't resolve does not fall back to the default beep — it goes SILENT (measured by ear, 2026-08-08), while the plist still reads like a working setting. haus builds the path from the name and skips the write with a warning if that file is missing, so a macOS release retiring a sound can't quietly mute you.

Example:

"Submarine"

Declared in modules/den/options.nix.

`haus.sound.alertVolume`

null or integer between 0 and 100 (both inclusive) · default null

How loud the alert beep is, 0–100, exactly as the slider in System Settings ▸ Sound reads. null (the default) leaves macOS's own choice alone.

haus converts to the exponential value macOS actually stores (e^(v/100 − 1), with 0 meaning silence), because that key is not a fraction: writing the obvious 0.5 gets you 31%.

TWO WRITERS: the volume keys and the Sound pane write this same key. Declaring it means every rebuild reasserts your number over anything you changed by hand since — which is the point of declaring it, but leave it null if you'd rather the slider win.

Example:

Declared in modules/den/options.nix.

`haus.sound.startupChime`

null or boolean · default null

The chime a Mac plays at boot. null (the default) leaves it alone.

The odd one in this group: it is firmware state (nvram StartupMute), not a preference, so it survives an OS reinstall and a wiped home directory — and it is the only setting here that needs the rebuild to run as root, which activation already does.

Example:

false

Declared in modules/den/options.nix.

`haus.sound.uiSounds`

null or boolean · default null

Play user-interface sound effects — the Trash whoosh, the screenshot shutter, the Mail whoosh. null (the default) leaves macOS's own choice alone.

Example:

false

Declared in modules/den/options.nix.

`haus.sound.volumeFeedback`

null or boolean · default null

Play a sound when the volume keys change the volume. null (the default) leaves macOS's own choice alone.

Example:

true

Declared in modules/den/options.nix.

Displays

Resolution and per-display behaviour, addressed by which screen you mean rather than by a panel's serial number.

haus.displays

Per-display overrides, keyed by which screen you mean.

`haus.displays`

attribute set of (submodule) · default { }

Per-display settings, keyed by which screen you mean:

internal the built-in panel main whichever display is currently main <uuid> a persistent display UUID, for a specific external monitor — run hausdisp list to print the UUIDs of what's attached

Default is the empty set, and then nothing about your displays is touched. A key naming a display that isn't plugged in right now is skipped with a note, not an error, so a displays.<uuid> entry for the monitor at the office can't fail a rebuild on the train.

Why this option exists at all: display scaling is the only lever macOS 26 gives us for "make EVERYTHING bigger", system-wide, including apps haus knows nothing about. macOS's own text-size setting writes a value no running app re-reads, while the accessibility scalars that do work affect contrast or motion rather than system-wide size — measured, not assumed (the workshop's notes/macos-settings-matrix.md records the sweep). So haus.ui.scale and haus.fonts make haus's own tools bigger, and this makes the Mac bigger.

Example:

{
  "37D8832A-2D66-02CA-B9F7-8F30A301B230" = {
    uiScale = "more-space";
  };
  internal = {
    uiScale = "larger-text";
  };
}

Declared in modules/displays/options.nix.

`haus.displays.<name>.uiScale`

null or one of "more-space", "default", "larger-text", "largest-text" · default null

The scaled resolution, as an intent rather than a pixel count — the same four positions System Settings ▸ Displays offers, named:

more-space the largest resolution the panel offers (smallest UI) default the panel's own default mode larger-text between the default and the smallest resolution largest-text the smallest resolution the panel offers (biggest UI)

Resolved per panel from the modes that panel actually reports, so the same value means the same thing on a 14" laptop and a 27" monitor rather than the same number of pixels. On the 14" MacBook Pro this was developed on that resolves to 1800x1169 · 1512x982 · 1147x745 · 1024x665.

Applied at each home-manager activation and set permanently, so it survives a reboot; re-applying an already-current mode is a no-op, so a rebuild doesn't flash your screen. null (the default) leaves the display alone.

When more than one selector names the same attached panel, the more specific setting wins: UUID over internal over main. This lets a host-specific display setting refine a broad profile such as haus.appearance.largePrint without depending on activation order.

Honest scope: this is a real, system-wide size change — every app gets bigger, not just haus's own tools — and the cost is desk space, because a larger UI means less of it. It also can't run from a rebuild with no GUI session attached (over SSH, say); the setting applies at the next activation you run while logged in.

Example:

"larger-text"

Declared in modules/displays/options.nix.

Development

The terminal stack — terminal, shell, multiplexer, editor — plus the browser, the CLI toolbelt, Git tooling and language runtimes. Your commit identity itself is a fact about you rather than this room's, and stays in your host. The terminal lives here because a terminal with no tools in it is not a separate thing anyone wants.

haus.hearth

The shell and terminal experience.

`haus.hearth.editor`

string · default the command for haus.hearth.editorName — hx for helix

The ONE editor command haus uses everywhere. It's the shell command for $EDITOR / $VISUAL (git, etc.) AND what every "open in an editor" action launches — the "Nix Config" palette command, the bar's nix-open item, and the file-association hijack. Those open the target in a new zellij tab running this command, so a terminal editor is the natural fit for haus; a GUI editor's CLI works too (e.g. "code" or "code -w" to block).

It defaults to the command for haus.hearth.editorName, so choosing an editor there is enough. Set this only for the case that option cannot express: pointing haus at something it does not install. Naming a command here does NOT install it — that machine has to already have it.

Example:

"code -w"

Declared in modules/hearth/options.nix.

`haus.hearth.editorName`

one of "helix", "nano", "neovim", "vim" · default "helix"

Which editor this room installs. helix (the default) is the one haus is themed around; neovim, vim and nano are installed as-is, with no Nebelung theme — Nebelung has a port for helix and not for them.

Setting this also moves haus.hearth.editor, since that defaults to whatever the chosen editor answers to on PATH (hx, nvim, vim, nano). Choosing here is the whole gesture: the editor is installed AND every "open in an editor" action follows it.

A desktop may set this. To point haus at an editor it does not install — a GUI one, or something from your own host file — leave this alone and set haus.hearth.editor instead.

Example:

"neovim"

Declared in modules/hearth/options.nix.

`haus.hearth.floatBorder`

one of "accent", "grey", "off", "rosewater", "flamingo", "pink", "mauve", "red", "maroon", "peach", "yellow", "green", "teal", "sky", "sapphire", "blue", "lavender" · default "accent"

The outline drawn around every floating terminal float-term.sh spawns: the Super-y yazi peek panel, the bar's agent peek, and the palette's Rebuild System / Install App / Settings and zscratch windows. They all land on top of a tiled desktop, where a dark terminal over a dark window behind it has no edge at all.

accent (the default) — haus.theme.accent, so a summoned window announces itself and the whole desktop keeps one accent.
grey — Nebelung's surface0, one step off the terminal's own background: the same relationship the bar's dropdowns wear (popup.background.border_color in modules/sill), for an edge that defines the window without drawing the eye.
off — no outline; the look before this option existed. It also keeps floatring out of the closure entirely, so nothing is compiled for it.
any Nebelung accent name (lavender, sapphire, …) — one colour for these popups that ISN'T haus.theme.accent, the same escape hatch haus.sill.logo.color offers.

2pt, following the window's own corner curve. Drawn by a tiny overlay window (modules/hearth/floatring.swift) that lives and dies with the popup, because Ghostty has no border setting of its own and aerospace draws none — that file's header has the rest, including why it isn't JankyBorders. Switch it with haus set hearth.floatBorder grey && haus rebuild; to compare colours first, without a rebuild, outline any window by hand (the process name is lower-case — pgrep -x Ghostty matches nothing and rings nothing): ~/.config/zellij/float-term.sh ring "$(pgrep -x ghostty | head -1)" '#cba6f7'

Example:

"grey"

Declared in modules/hearth/options.nix.

`haus.hearth.ghDash.enable`

boolean · default false

Whether to enable the themed gh-dash GitHub dashboard and its Cmd-G fullscreen Zellij overlay.

Enabling it gets you the issue and notification tabs (yours, assigned, unread, participating). The four PR tabs — open / green / red / shipped — need haus.git.org as well, since a PR section is a search filter scoped to an owner. A host can compose or replace any of it through home-manager's programs.gh-dash.settings: every section list Hearth writes is a mkDefault, per list.

Needs haus.developer.git.enable (an assertion enforces it): gh-dash authenticates out of gh's own credentials, so the Git pack is where its login comes from.

Example:

true

Declared in modules/hearth/options.nix.

`haus.hearth.hijackFileAssociations`

boolean · default false

When true, build a small opener app and make it the default handler for ~80 text/code extensions (json, md, ts, nix, rs, go, kdl, …), so opening or clicking those files opens them in haus.hearth.editor in a terminal tab. The app declares the types itself (not just duti) so extensions nothing else on the machine declares still bind. Off by default: silently rewriting your file associations is a jarring, hard-to-undo change, so it's strictly opt-in. (Extensionless executables like bench are NOT covered — macOS gates the public.unix-executable handler behind an interactive dialog; set it by hand once if wanted: duti -s org.nebelhaus.editoropen public.unix-executable all.)

Declared in modules/hearth/options.nix.

`haus.hearth.lanes.backend`

one of "zellij", "zmx" · default "zellij"

Where an agent lane's terminal actually lives.

zellij (the default) is the behaviour haus has always had: a lane is a pane in the main zellij session, and holt execs the client in the pane you ran it from. Panes are cheap, but a lane's identity is then a (session, pane-id) pair that only zellij understands — which is why the bar keeps a state file per pane and joins it back to a checkout path to work out which window to raise.

zmx makes the lane its own zmx session, viewed through its own Ghostty window, tiled by prowl — all three named holt.<repo>.<lane>. Three consequences, in the order you'd feel them:

Closing the window stops meaning parking the work. A zmx session outlives every client attached to it, so ⌘W detaches and the agent keeps thinking; holt <name> reopens a window onto the live conversation instead of resuming a transcript.
The name is the join. zmx ls --where state=waiting, AeroSpace's window-title-regex, and the lane in holt --json all key off one string.
Splits are gone, because zmx has none by design. Prowl tiles the windows instead, which is the trade: a real window manager rather than a second one nested inside a terminal.

Both backends can be installed at once — this only picks which one holt opens into, through the [hooks] open/resume seam in ~/.config/holt/config.toml. If zmx is somehow missing at runtime the hook defers (exit 3) and holt falls back to its built-in, so the worst case is the zellij behaviour you already had.

Declared in modules/hearth/options.nix.

`haus.hearth.obsidianVaults`

list of string · default [ ]

Home-relative paths to existing Obsidian vaults that should use the Nebelung theme. On each activation, Hearth copies the rendered theme.css + manifest.json into each vault's .obsidian/themes/Nebelung/ directory, selects Nebelung's dark appearance in appearance.json, and removes the obsolete "nebelung" CSS snippet from the enabled list.

Empty (the default) leaves every vault untouched. Paths must be relative to the user's home, may not contain "..", and are skipped with a warning unless their .obsidian directory already exists.

Example:

[
  "Library/Mobile Documents/iCloud~md~obsidian/Documents/notes"
]

Declared in modules/hearth/options.nix.

`haus.hearth.rightClickFullscreen`

boolean · default true

When true (the default), a bare right-click on any pane zooms it fullscreen — the same MouseAction::ToggleFullscreen Ctrl+Click already triggers, just a different, easier-to-reach trigger. It's a whole zellij-unwrapped patch, not a config toggle (mouse buttons still aren't bindable in config.kdl — see naked-click-links.patch's header for why link gestures hit the same wall), so flipping this rebuilds zellij; it does not take effect on a running server. The real cost: right-click stops reaching the pane's own program, so a TUI's own right-click context menu (lazygit, vim, mc, …) goes with it. Set false to leave right-click alone and keep zooming with Ctrl+Click or Super Enter.

Declared in modules/hearth/options.nix.

`haus.hearth.zellijStartLocked`

boolean · default true

When true (the default), zellij boots into Locked input mode instead of Normal — its single-key submode leaders (pane, tab, resize, …) stay inert until you unlock with Ctrl-g, so a stray keystroke can't jump you into a submode. The Super-prefixed launchers (claude / pane / tab / yazi-peek / fullscreen) are bound in shared and keep working while locked, as do Alt [ / Alt ] (cycle swap layouts) — the rest of zellij's Alt row stays inert while locked, since those keys are readline/vim word motions the pane's app wants. The bar's bottom-right quick-hint block only shows in Locked mode. Set false to start in Normal mode (zellij's own default).

Declared in modules/hearth/options.nix.

haus.zen

Zen browser policy, extensions and the optional native tab bridge.

`haus.zen.extensions`

attribute set of (submodule) · default { }

Browser extensions to deploy into Zen, by a stable id of your choosing.

The mechanism is Firefox's enterprise policies — haus renders an ExtensionSettings block — so it reaches Zen the way an IT department reaches Firefox, without a profile to hand-edit. haus.roster deliberately cannot do this: a roster entry installs from a cask, a brew, a nixpkgs package or the App Store, and a browser add-on is none of those.

Two consequences of HOW the policies are delivered, both visible. Firefox only ever looks for a policies.json inside the app bundle, which haus has no business writing into (it breaks the code signature and a cask upgrade wipes it), so haus uses the other route macOS offers: a managed preference at /Library/Preferences/app.zen-browser.zen.plist. That file is root-owned, so it's written during system activation and a haus rebuild that can't reach it warns instead of installing anything. And because enterprise policies are on, Zen will tell you it is "managed by your organization" — that organization is haus.

haus knows the id and slug of the extensions it themes (stylus), so those need only be named. Everything else needs id — see that option for where to find it.

Naming stylus here also turns on the stamped userstyle bundle (see haus.theme.accent): the Catppuccin-derived styles Stylus imports carry their own accent and flavor variables, which no palette file can reach, so haus stamps the bundle from your theme — accent, flavor, and the contrast it's rendered for — and tells you when there's a new one to import.

Example:

{
  # Known to haus — id and slug are filled in.
  stylus = { };
  # Anything else: bring the id.
  ublock-origin = {
    id = "uBlock0@raymondhill.net";
    slug = "ublock-origin";
  };
}

Declared in modules/hearth/options.nix.

`haus.zen.extensions.<name>.enable`

boolean · default true

Whether to deploy this extension. Set false to remove one an imported desktop added.

Declared in modules/hearth/options.nix.

`haus.zen.extensions.<name>.id`

null or string · default null

The extension's own id — the key Firefox's policy engine matches on, NOT its AMO slug. Usually a brace-wrapped UUID, sometimes an email-shaped string (addon@example.org).

Find it by installing the add-on once and reading Extension ID under about:debugging ▸ This Firefox, or from the browser_specific_settings block of its source. Wrong id and the policy silently installs nothing — which is why this has no guessable default.

Example:

"{7a7a4a92-a2a0-41d1-9fd7-1e92480d612d}"

Declared in modules/hearth/options.nix.

`haus.zen.extensions.<name>.mode`

one of "force_installed", "normal_installed", "allowed", "blocked" · default "force_installed"

Firefox's installation_mode. force_installed installs it and stops the user removing it (the point, for a desktop that wants an extension present); normal_installed installs it but leaves it removable.

Declared in modules/hearth/options.nix.

`haus.zen.extensions.<name>.slug`

null or string · default null

The add-on's AMO slug — the last path segment of its addons.mozilla.org URL. Only used to build the default url; set url directly and this is ignored.

Example:

"styl-us"

Declared in modules/hearth/options.nix.

`haus.zen.extensions.<name>.url`

string · default ""

Where the .xpi comes from. Defaults to AMO's "latest" endpoint for slug, so the add-on updates itself; point it at a pinned version or a self-hosted file to freeze it.

A file:// url has a second effect, and it is not local to this extension: a file on disk cannot have been signed by Mozilla, and Zen refuses an unsigned add-on (ERROR_SIGNEDSTATE_REQUIRED) unless xpinstall.signatures.required is off. So naming one makes haus lock that pref off for the whole browser — the same switch haus.zen.tabBridge.enable documents, since the bridge is haus's own file:// install. An https:// AMO url never turns it on.

Declared in modules/hearth/options.nix.

`haus.zen.extraPolicies`

attribute set · default { }

Anything else to put in Zen's policy set, merged beside the ExtensionSettings block haus.zen.extensions renders. haus OWNS the file these land in — /Library/Preferences/app.zen-browser.zen.plist, written as root — so this is the escape hatch for the rest of the policy surface rather than a reason to take the file back by hand. Keys here win over haus's on a collision.

Write the policy names as Firefox documents them, nested: this becomes the top level of a plist beside EnterprisePoliciesEnabled, so { Extensions.Install = [ "…" ]; } is an Extensions dict with an Install array in it, not a key called Extensions.Install. Setting every policy back to { } (and naming no extensions) takes the file down again on the next rebuild.

The merge is one level deep, so naming a policy takes that policy over WHOLE. Two of them haus writes itself: ExtensionSettings (from haus.zen.extensions) and Preferences (which is where the signature switch a file:// install needs ends up). Restate what you still want if you set either — dropping the signature switch this way is invisible until you notice the add-on isn't there.

Values are passed to a plist writer, so null is not a value: it renders as a key with nothing under it, which makes the whole file invalid and drops every policy, not just that one. Omit the key instead.

Example:

{ DisableTelemetry = true; }

Declared in modules/hearth/options.nix.

`haus.zen.tabBridge.enable`

boolean · default false

Deploy haus's own tiny extension into Zen, so the bar can find and switch to the tab that is making noise.

This is what makes the media pill's ⌘ click land on the tab rather than just bringing Zen forward. Safari and the Chromium browsers need nothing here — they hand their tab list to AppleScript and the pill uses that. Firefox and its forks hand out nothing at all, to AppleScript or to accessibility, so without this the pill falls back to driving Firefox's own address-bar tab search with synthetic keystrokes, which needs the Accessibility permission and is exactly as pleasant as it sounds.

Off by default because it force-installs an add-on into your browser, which is not a thing haus should do to you unasked. Turning it on costs one derivation, a native-messaging manifest, and two keys in haus's root-owned policy plist — one of which is the signature switch below. Turning it back off stops haus deploying it — what Zen then does with the add-on already installed is Firefox's policy engine's business, not haus's, so check about:addons and remove it there if it outstays the option.

Zen only, and that's a signing constraint rather than a choice. Release Firefox refuses an extension Mozilla hasn't signed, and it is built so that no pref and no policy can say otherwise. Zen is built the other way (MOZ_REQUIRE_SIGNING = false), which is the whole reason haus can build the .xpi itself and install it out of the nix store.

It still costs a switch. Zen carries Firefox's own preference defaults, which turn signature enforcement back on, so turning this option on also makes haus lock xpinstall.signatures.required = false — for the browser, not just for its own add-on. Without it Zen refuses the bridge with ERROR_SIGNEDSTATE_REQUIRED and the option quietly does nothing; with it, an unsigned add-on from anywhere would also install if something asked. That is the second reason this is off by default.

Firefox support would mean an AMO account and unlisted self-distribution signing — packaging, not a code change — and would drop the pref.

Declared in modules/hearth/options.nix.

haus.developer

The developer pack: the CLI toolbelt, Git tooling and language runtimes. Coding agents left this pack on 2026-08-13 and are their own room now (haus.ai.*). Off is a nebelhaus machine for someone who never opens a terminal by choice.

`haus.developer.enable`

boolean · default false

The Development room: the CLI toolbelt, Git tooling and language runtimes. The neutral catalogue leaves it off; nebelhaus selects it in its desktop.

Coding agents left this pack on 2026-08-13 and are their own room now (haus.ai.*). The two rooms are independent: a desktop or host selects each one explicitly.

false is what makes a non-developer nebelhaus possible — it strips those tools rather than merely hiding them. What remains is the product: haus, awake, the theme, the terminal, the bar, the tiler and the palette.

The Git and toolbelt sub-options below default to this value, so a host can turn the room on and then remove one piece:

haus.developer.enable = true; haus.developer.git.enable = false; # …but leave Git tooling out

Example:

true

Declared in modules/options.nix.

`haus.developer.git.enable`

boolean · default config.haus.developer.enable

Git and its surroundings: the shell alias vocabulary, the themed git config, delta (diff pager), lazygit, gh, and gnupg for commit signing. Off drops all of them, and haus.git.* then has nothing to configure.

Declared in modules/options.nix.

`haus.developer.languages`

list of value "node" (singular enum) · default [ ]

Language runtimes to install. Currently only "node" (bun + fnm, with fnm's --use-on-cd shell hook).

Deliberately a list rather than one bool per language, so adding "rust" or "python" later doesn't change this option's shape.

Example:

[ ]

Declared in modules/options.nix.

`haus.developer.toolbelt.enable`

boolean · default config.haus.developer.enable

The terminal toolbelt: bat, fzf, fd, ripgrep, yazi, zoxide, lsd, glow, jq, tree, chafa, ttyd and fastfetch — the themed replacements for cat, find, grep, ls and friends that haus's shell is built around.

Off leaves a plain shell. The prompt (starship) and the colour scheme stay: these are the tools, not the appearance.

Declared in modules/options.nix.

Windows

Tiling, window navigation, hot corners, and the leader key that launches an app or throws it somewhere. The workspaces themselves (haus.workspaces) and the keys haus claims (haus.keys) are shared surfaces below, because the bar and the launcher read them too.

haus.hotCorners

What each corner of the screen does when the pointer reaches it. Every corner is unset by default, so haus never overwrites one you set yourself.

`haus.hotCorners.bottomLeft`

null or one of "disabled", "mission-control", "application-windows", "desktop", "launchpad", "notification-center", "quick-note", "screen-saver", "prevent-screen-saver", "sleep-display", "lock-screen" · default null

What happens when the pointer reaches the bottom-left corner of the main display.

              disabled  nothing happens — the corner is explicitly claimed and left inert
       mission-control  Mission Control: every window and Space, zoomed out
   application-windows  App Exposé: every window of the app you're in
               desktop  push all windows aside and show the desktop
             launchpad  the grid of installed apps (on macOS 26 this opens the Apps view)
   notification-center  slide out Notification Center and its widgets
            quick-note  start a Quick Note — Apple's own default for the bottom-right corner
          screen-saver  start the screen saver immediately
  prevent-screen-saver  hold the screen saver off while the pointer rests here
         sleep-display  put the display to sleep (the machine keeps running)
           lock-screen  lock the screen and return to the login window

null (the default) writes nothing at all, which is not the same as "disabled": corners are a setting people have usually already made by hand, and a desktop that names one it doesn't care about would silently erase it. Use "disabled" to explicitly claim a corner and make it inert.

Setting a corner also clears its MODIFIER key. macOS stores "hold ⌘ for this corner" separately (wvous-*-modifier), and a leftover modifier from an earlier setup makes a corner you just declared look broken — nothing happens, because you weren't holding the key nobody told you about. Corners left at null keep whatever modifier they have.

Worth knowing if you also run tiling: mission-control and desktop are macOS's own window and Space management, which prowl replaces. They still work, they just show you a view of the windows prowl is arranging.

Example:

"mission-control"

Declared in modules/den/options.nix.

`haus.hotCorners.bottomRight`

What happens when the pointer reaches the bottom-right corner of the main display.

              disabled  nothing happens — the corner is explicitly claimed and left inert
       mission-control  Mission Control: every window and Space, zoomed out
   application-windows  App Exposé: every window of the app you're in
               desktop  push all windows aside and show the desktop
             launchpad  the grid of installed apps (on macOS 26 this opens the Apps view)
   notification-center  slide out Notification Center and its widgets
            quick-note  start a Quick Note — Apple's own default for the bottom-right corner
          screen-saver  start the screen saver immediately
  prevent-screen-saver  hold the screen saver off while the pointer rests here
         sleep-display  put the display to sleep (the machine keeps running)
           lock-screen  lock the screen and return to the login window

Example:

"mission-control"

Declared in modules/den/options.nix.

`haus.hotCorners.topLeft`

What happens when the pointer reaches the top-left corner of the main display.

              disabled  nothing happens — the corner is explicitly claimed and left inert
       mission-control  Mission Control: every window and Space, zoomed out
   application-windows  App Exposé: every window of the app you're in
               desktop  push all windows aside and show the desktop
             launchpad  the grid of installed apps (on macOS 26 this opens the Apps view)
   notification-center  slide out Notification Center and its widgets
            quick-note  start a Quick Note — Apple's own default for the bottom-right corner
          screen-saver  start the screen saver immediately
  prevent-screen-saver  hold the screen saver off while the pointer rests here
         sleep-display  put the display to sleep (the machine keeps running)
           lock-screen  lock the screen and return to the login window

Example:

"mission-control"

Declared in modules/den/options.nix.

`haus.hotCorners.topRight`

What happens when the pointer reaches the top-right corner of the main display.

              disabled  nothing happens — the corner is explicitly claimed and left inert
       mission-control  Mission Control: every window and Space, zoomed out
   application-windows  App Exposé: every window of the app you're in
               desktop  push all windows aside and show the desktop
             launchpad  the grid of installed apps (on macOS 26 this opens the Apps view)
   notification-center  slide out Notification Center and its widgets
            quick-note  start a Quick Note — Apple's own default for the bottom-right corner
          screen-saver  start the screen saver immediately
  prevent-screen-saver  hold the screen saver off while the pointer rests here
         sleep-display  put the display to sleep (the machine keeps running)
           lock-screen  lock the screen and return to the login window

Example:

"mission-control"

Declared in modules/den/options.nix.

haus.prowl

Tiling window management and the Caps-Lock leader launcher.

`haus.prowl.enable`

boolean · default false

AeroSpace tiling window management + the leader-key launcher.

This is the room switch: off drops AeroSpace, its launch agent, the wake-time window re-sort and the key remap entirely. To keep the tiler but leave the keyboard alone, use haus.keys.leader = "none" and haus.keys.windowNav = "none" instead of turning the room off.

Declared in modules/prowl/options.nix.

Bar

The menu bar: where it draws, which pills it carries, and what each one reads.

haus.menuBar

The stock menu bar: what the clock shows, and which Control Center glyphs sit beside it. (The nebelhaus bar itself is sill.)

`haus.menuBar.clock.analog`

null or boolean · default null

Draw an analog clock face instead of a digital readout. null (the default) leaves macOS's own choice alone (digital).

Example:

false

Declared in modules/den/options.nix.

`haus.menuBar.clock.format`

null or one of "12h", "24h" · default null

12-hour or 24-hour menu bar clock. null (the default) leaves macOS's own choice alone (region-dependent, usually 12h in the US).

Example:

"24h"

Declared in modules/den/options.nix.

`haus.menuBar.clock.showDate`

null or one of "when-space-allows", "always", "never" · default null

Whether the full date appears next to the time. null (the default) leaves macOS's own choice alone ("when-space-allows").

Example:

"always"

Declared in modules/den/options.nix.

`haus.menuBar.clock.showDayOfWeek`

null or boolean · default null

Show the day of the week next to the clock. null (the default) leaves macOS's own choice alone.

Example:

true

Declared in modules/den/options.nix.

`haus.menuBar.clock.showSeconds`

null or boolean · default null

Show the clock to second precision instead of minutes. null (the default) leaves macOS's own choice alone.

Example:

false

Declared in modules/den/options.nix.

`haus.menuBar.controlCenter.airdrop`

null or boolean · default null

Whether the AirDrop control has a menu bar icon of its own. null (the default) leaves macOS's own choice alone.

Example:

false

Declared in modules/den/options.nix.

`haus.menuBar.controlCenter.batteryPercentage`

null or boolean · default null

Show the battery percentage next to its menu bar icon. null (the default) leaves macOS's own choice alone.

Example:

true

Declared in modules/den/options.nix.

`haus.menuBar.controlCenter.bluetooth`

null or boolean · default null

Whether the Bluetooth control has a menu bar icon of its own. null (the default) leaves macOS's own choice alone.

Example:

true

Declared in modules/den/options.nix.

`haus.menuBar.controlCenter.displayBrightness`

null or boolean · default null

Whether the Screen Brightness control has a menu bar icon of its own. null (the default) leaves macOS's own choice alone.

Example:

true

Declared in modules/den/options.nix.

`haus.menuBar.controlCenter.focus`

null or boolean · default null

Whether the Focus control has a menu bar icon of its own. null (the default) leaves macOS's own choice alone.

Example:

true

Declared in modules/den/options.nix.

`haus.menuBar.controlCenter.nowPlaying`

null or boolean · default null

Whether the Now Playing control has a menu bar icon of its own. null (the default) leaves macOS's own choice alone.

Example:

false

Declared in modules/den/options.nix.

`haus.menuBar.controlCenter.sound`

null or boolean · default null

Whether the Sound control has a menu bar icon of its own. null (the default) leaves macOS's own choice alone.

Example:

true

Declared in modules/den/options.nix.

haus.sill

The menu bar, and which pills it draws.

`haus.sill.aiUsage.provider`

one of "latest", "claude", "codex", "opencode" · default "latest"

Which AI provider to display in the main pill: latest (default, automatically shows whichever provider reported most recently), or one of claude, codex, opencode. Clicking the pill always displays the full dropdown with all reporting providers.

Note this is about usage readouts, not about which client holt can spawn: a provider reports here whenever it has data for your account — Codex notably does so from a ChatGPT login alone, with no CLI installed — so it is deliberately not tied to haus.ai.clients.

Example:

"claude"

glyph	codepoint	what it is
``	`U+F015`	`nf-fa-home` — solid house (the default)
``	`U+F46D`	`nf-oct-home` — outlined house at icon weight
``	`U+EB06`	`nf-cod-home` — the same, slightly rounder
`⌂`	`U+2302`	the hausfold mark, hairline
``	`U+F302`	`nf-fa-apple` — the logo this pill replaced
``	`U+F313`	`nf-linux-nixos` — the snowflake