v4.0.3-1 (experimental)

⚠️ Experimental — not yet verified on hardware

This release is published untested on real machines. CI installs
it in a VM; a VM exposes no NPU, one graphics device and no firmware
quirks, so a VM install passing says very little about a laptop.
Real installs have failed where every check was green.

The flake route (nixos-rebuild against this repo, see the
README) is the mature one and is what to use on a machine you care
about. The ISO installer is the least mature part of the project
and it partitions the disk before it can fail.

If you install from this image, please say how it went on the
release discussion — success as much as failure. The experimental
label comes off a release only once someone has reported a
successful install on physical hardware.

What this release is

Omarchy v4.0.3, packaged for NixOS, up from v4.0.2 in
v4.0.2-12. Upstream's notes for it:
https://github.com/basecamp/omarchy/releases/tag/v4.0.3

Packages v4.0.3 changes

Upstream's install lists, v4.0.2 → v4.0.3. Each line is a decision
this port either mirrors or knowingly does not.

Added

• broadcom-wl-dkms

Removed

• broadcom-wl

A removal is the one worth reading twice: upstream dropping a package
is often a security decision, and a comment in this repo may still be
citing it as a reason for something.

Seeded config files that changed. A machine installed from this
release starts with these. One you already run keeps the copies in
your ~/.config, which are yours.

• config/kitty/kitty.conf
• default/hypr/apps/hermes.lua

Configuration changes

Defaults that changed. These take effect on a machine whose
configuration.nix says nothing about them.

• programs.nixarchy.package: "store:omarchy-4.0.2" → "store:omarchy-4.0.3"
• programs.nixarchy.tree: "store:omarchy-4.0.2/share/omarchy" → "store:omarchy-4.0.3/share/omarchy"

New options.

• programs.nixarchy.apps.aether (default {})
• programs.nixarchy.apps.openclaw (default {})

NixOS defaults this port sets. Not options of ours -- these are
settings nixarchy chooses on your behalf, and a machine that never
mentioned them follows the new value.

• now services.nixi.enable = lib.mkDefault true; in modules/home.nix
• now gpu-screen-recorder.enable = lib.mkDefault true; in modules/nixos.nix
• now zramSwap.enable = lib.mkDefault true; in modules/nixos.nix

Package changes

Packages this repo pins by hand, rather than taking from nixpkgs.

• aether 4.29.8, packaged here for the first time

Everything else

Every merged change, grouped by where in the tree it landed. This repo
writes commit subjects as full sentences, so they are already the notes.

The desktop and what it configures

• Omarchy 4.0.3, and a bump that asks instead of blocking (#437)
• Every nixarchy desktop ships with the guide (#429)
• Two rows that could never have worked, and the checks that would have said so (#425)
• Aether builds here, and the cache carries it so nobody else builds it (#424)
• A machine with no swap has no headroom, and ours had none (#422)

Installing, and the ISO

• The machine's name stops being an input to its system (#434)
• extraDependencies carries runtime outputs, not a build graph (#433)
• The offline rescue says what it would build, and why, with no network (#432)
• The two files the installer invents are written to the log (#431)

Packaged programs and the vendored tree

• aether's updateScript was missing --flake, and the nightly said so (#440)
• Zed was the one editor whose colours never followed the theme (#421)

Checks and CI

• One script owns every derived number, with --check and --fix (#445)
• The cache probe could only ever pass on the commit that pushed (#442)
• The encrypted-install assertion could never pass, whatever the installer did (#444)
• doctor-wireless names the string it wanted and not what it got (#443)
• The offline image stops being published until it can install again (#430)
• The install log was thrown away, and it held the only answer (#426)
• A probe for a push that cannot fail, and a reason that stopped being true (#428)
• CI stops rebuilding what it can already prove, and stops building what a change cannot alter (#427)

Documentation

• The bus section said the room exists but never said when to use it (#420)
• COPILOT.md said post was off while the live config had it on (#415)

Elsewhere

• nixpkgs: 6 app version(s) move (#441)
• Smoke-test agent-bus connectivity from the Copilot cloud agent (#423)
• Smoke-test agent-bus MCP connectivity from Copilot environment (#418)

24 changes since v4.0.2-12.

Getting it

Omarchy 4.0.3, packaged for NixOS. One image this time.

nixarchy-v4.0.3-1-net.iso — 1.6G, downloads the desktop as it installs.
One file, no reassembly, and it needs a working network: its first
screen offers Wi-Fi if there is no cable. This is the image people
have been installing from, and it works.

The offline image is not in this release. It carried the whole
system closure and promised an install with no network at all, and
it stopped keeping that promise: the machine it produces evaluates a
closure the image does not carry, so it tries to build the world and
cannot, with no network to fall back on. The installer notices and
refuses rather than leaving a half-installed disk, but an image whose
only reason to exist is "no network needed" is not worth shipping
while it needs one. It returns when the check that installs from it
offline is green again.

sha256sum -c --ignore-missing SHA256SUMS

(--ignore-missing because one SHA256SUMS covers both images, and
nobody downloads both.)

Then write one to a USB stick and boot it. See
Fresh-machine install
for what happens next.

What's Changed

• COPILOT.md said post was off while the live config had it on by @olafkfreund in #415
• The bus section said the room exists but never said when to use it by @olafkfreund in #420
• A machine with no swap has no headroom, and ours had none by @olafkfreund in #422
• Aether builds here, and the cache carries it so nobody else builds it by @olafkfreund in #424
• Smoke-test agent-bus MCP connectivity from Copilot environment by @olafkfreund with @Copilot in #418
• Smoke-test agent-bus connectivity from the Copilot cloud agent by @olafkfreund with @Copilot in #423
• Two rows that could never have worked, and the checks that would have said so by @olafkfreund in #425
• Zed was the one editor whose colours never followed the theme by @olafkfreund in #421
• CI stops rebuilding what it can already prove, and stops building what a change cannot alter by @olafkfreund in #427
• A probe for a push that cannot fail, and a reason that stopped being true by @olafkfreund in #428
• The install log was thrown away, and it held the only answer by @olafkfreund in #426
• The offline image stops being published until it can install again by @olafkfreund in #430
• The two files the installer invents are written to the log by @olafkfreund in #431
• Every nixarchy desktop ships with the guide by @olafkfreund in #429
• The offline rescue says what it would build, and why, with no network by @olafkfreund in #432
• extraDependencies carries runtime outputs, not a build graph by @olafkfreund in #433
• Omarchy 4.0.3, and a bump that asks instead of blocking by @olafkfreund in #437
• aether's updateScript was missing --flake, and the nightly said so by @olafkfreund in #440
• nixpkgs: 6 app version(s) move by @olafkfreund in #441
• doctor-wireless names the string it wanted and not what it got by @olafkfreund in #443
• The encrypted-install assertion could never pass, whatever the installer did by @olafkfreund in #444
• The machine's name stops being an input to its system by @olafkfreund in #434
• The cache probe could only ever pass on the commit that pushed by @olafkfreund in #442
• One script owns every derived number, with --check and --fix by @olafkfreund in #445

New Contributors

• @olafkfreund with @Copilot made their first contribution in #418

Full Changelog: v4.0.2-12...v4.0.3-1

v4.0.2-12 (experimental)

⚠️ Experimental — not yet verified on hardware

This release is published untested on real machines. CI installs
it in a VM; a VM exposes no NPU, one graphics device and no firmware
quirks, so a VM install passing says very little about a laptop.
Real installs have failed where every check was green.

The flake route (nixos-rebuild against this repo, see the
README) is the mature one and is what to use on a machine you care
about. The ISO installer is the least mature part of the project
and it partitions the disk before it can fail.

If you install from this image, please say how it went on the
release discussion — success as much as failure. The experimental
label comes off a release only once someone has reported a
successful install on physical hardware.

What this release is

Omarchy v4.0.2, packaged for NixOS -- the same upstream release
v4.0.2-11 vendored. Everything below is this port's own work.

Configuration changes

No option was added, removed or given a different default:
programs.nixarchy means what it meant under v4.0.2-11.

No NixOS default this port sets moved.

Package changes

Packages this repo pins by hand, rather than taking from nixpkgs.

None of them moved. Still at the versions v4.0.2-11 shipped:

• grok-bot 0.24.0
• hey-cli 1.4.1
• omacalc 0.2.2
• omacut 0.4.0
• omawrite 0.5.0
• once 0.3.2
• ttfx 0.3.2

Everything else

Every merged change, grouped by where in the tree it landed. This repo
writes commit subjects as full sentences, so they are already the notes.

Installing, and the ISO

• Installer hardening and CI hardening, together (#413)

Checks and CI

• Copilot can join the bus, and the kit's own install works again (#414)
• Two nightly checks were failing on their own assertions, not on the product (#406)

Documentation

• Document what v4.0.2-11 changed, where people will look for it (#403)

Elsewhere

• nixpkgs: 3 app version(s) move (#405)

5 changes since v4.0.2-11.

Getting it

Omarchy 4.0.2, packaged for NixOS. Two images, and the difference
is what they carry.

nixarchy-v4.0.2-12.iso — 6.1G, carries the whole system closure. The install
copies rather than downloads and needs no network at all. Take this
one unless the download is what you mind.

GitHub will not accept a file that size, so it is split. Put it back
together and check it:

cat nixarchy-v4.0.2-12.iso.part-* > nixarchy-v4.0.2-12.iso
sha256sum -c --ignore-missing SHA256SUMS

nixarchy-v4.0.2-12-net.iso — 1.6G, downloads the desktop as it installs.
One file, no reassembly, and it needs a working network: its first
screen offers Wi-Fi if there is no cable.

sha256sum -c --ignore-missing SHA256SUMS

(--ignore-missing because one SHA256SUMS covers both images, and
nobody downloads both.)

Then write one to a USB stick and boot it. See
Fresh-machine install
for what happens next.

What's Changed

• Document what v4.0.2-11 changed, where people will look for it by @olafkfreund in #403
• nixpkgs: 3 app version(s) move by @olafkfreund in #405
• Two nightly checks were failing on their own assertions, not on the product by @olafkfreund in #406
• Copilot can join the bus, and the kit's own install works again by @olafkfreund in #414
• Installer hardening and CI hardening, together by @olafkfreund in #413

Full Changelog: v4.0.2-11...v4.0.2-12

v4.0.2-11 (experimental)

⚠️ Experimental — not yet verified on hardware

This release is published untested on real machines. CI installs
it in a VM; a VM exposes no NPU, one graphics device and no firmware
quirks, so a VM install passing says very little about a laptop.
Real installs have failed where every check was green.

The flake route (nixos-rebuild against this repo, see the
README) is the mature one and is what to use on a machine you care
about. The ISO installer is the least mature part of the project
and it partitions the disk before it can fail.

If you install from this image, please say how it went on the
release discussion — success as much as failure. The experimental
label comes off a release only once someone has reported a
successful install on physical hardware.

What this release is

Omarchy v4.0.2, packaged for NixOS -- the same upstream release
v4.0.2-10 vendored. Everything below is this port's own work.

Configuration changes

No option was added, removed or given a different default:
programs.nixarchy means what it meant under v4.0.2-10.

NixOS defaults this port sets. Not options of ours -- these are
settings nixarchy chooses on your behalf, and a machine that never
mentioned them follows the new value.

• no longer hardware.i2c.enable = lib.mkDefault true; in modules/nixos.nix
• now i2c.enable = lib.mkDefault true; in modules/nixos.nix
• no longer hardware.bluetooth.enable = lib.mkDefault true; in modules/nixos.nix
• now bluetooth.enable = lib.mkDefault true; in modules/nixos.nix
• now cpu.intel.updateMicrocode = lib.mkDefault config.hardware.enableRedistributableFirmware; in modules/nixos.nix
• now cpu.amd.updateMicrocode = lib.mkDefault config.hardware.enableRedistributableFirmware; in modules/nixos.nix
• now enableRedistributableFirmware = lib.mkDefault true; in modules/nixos.nix

Package changes

Packages this repo pins by hand, rather than taking from nixpkgs.

None of them moved. Still at the versions v4.0.2-10 shipped:

• grok-bot 0.24.0
• hey-cli 1.4.1
• omacalc 0.2.2
• omacut 0.4.0
• omawrite 0.5.0
• once 0.3.2
• ttfx 0.3.2

Everything else

Every merged change, grouped by where in the tree it landed. This repo
writes commit subjects as full sentences, so they are already the notes.

The desktop and what it configures

• "maybe ship iwctl?" -- no: with no netdev every wireless UI shows the same nothing (#399)

Installing, and the ISO

• Omarchy runs on anything because of 35 quirk scripts; NixOS has 439 modules (#401)

Checks and CI

• Every install test targeted /dev/vda; real laptops are NVMe (#400)
• The release notes stopped being derived because we re-shallowed the clone (#396)

Documentation

• Teach the USB path with no trap in it (#397)
• The roadmap listed a closed epic as planned, and its own check said so (#398)

6 changes since v4.0.2-10.

Getting it

Omarchy 4.0.2, packaged for NixOS. Two images, and the difference
is what they carry.

nixarchy-v4.0.2-11.iso — 6.1G, carries the whole system closure. The install
copies rather than downloads and needs no network at all. Take this
one unless the download is what you mind.

GitHub will not accept a file that size, so it is split. Put it back
together and check it:

cat nixarchy-v4.0.2-11.iso.part-* > nixarchy-v4.0.2-11.iso
sha256sum -c --ignore-missing SHA256SUMS

nixarchy-v4.0.2-11-net.iso — 1.6G, downloads the desktop as it installs.
One file, no reassembly, and it needs a working network: its first
screen offers Wi-Fi if there is no cable.

sha256sum -c --ignore-missing SHA256SUMS

(--ignore-missing because one SHA256SUMS covers both images, and
nobody downloads both.)

Then write one to a USB stick and boot it. See
Fresh-machine install
for what happens next.

What's Changed

• The release notes stopped being derived because we re-shallowed the clone by @olafkfreund in #396
• The roadmap listed a closed epic as planned, and its own check said so by @olafkfreund in #398
• "maybe ship iwctl?" -- no: with no netdev every wireless UI shows the same nothing by @olafkfreund in #399
• Teach the USB path with no trap in it by @olafkfreund in #397
• Every install test targeted /dev/vda; real laptops are NVMe by @olafkfreund in #400
• Omarchy runs on anything because of 35 quirk scripts; NixOS has 439 modules by @olafkfreund in #401

Full Changelog: v4.0.2-10...v4.0.2-11

v4.0.2-10 (experimental)

⚠️ Experimental — not yet verified on hardware

This release is published untested on real machines. CI installs
it in a VM; a VM exposes no NPU, one graphics device and no firmware
quirks, so a VM install passing says very little about a laptop.
Real installs have failed where every check was green.

The flake route (nixos-rebuild against this repo, see the
README) is the mature one and is what to use on a machine you care
about. The ISO installer is the least mature part of the project
and it partitions the disk before it can fail.

If you install from this image, please say how it went on the
release discussion — success as much as failure.

This release is shown as the latest one so testers can find it without
hunting through tags. That is a visibility decision, not a verification
one: the (experimental) in the title and this banner stay until
someone reports a successful install on physical hardware.

What this release is

Omarchy v4.0.2, packaged for NixOS -- the same upstream release
v4.0.2-9 vendored. Everything below is this port's own work.

Configuration changes

No option was added, removed or given a different default:
programs.nixarchy means what it meant under v4.0.2-9.

No NixOS default this port sets moved.

Package changes

Packages this repo pins by hand, rather than taking from nixpkgs.

None of them moved. Still at the versions v4.0.2-9 shipped:

• grok-bot 0.24.0
• hey-cli 1.4.1
• omacalc 0.2.2
• omacut 0.4.0
• omawrite 0.5.0
• once 0.3.2
• ttfx 0.3.2

Everything else

Every merged change, grouped by where in the tree it landed. This repo
writes commit subjects as full sentences, so they are already the notes.

Installing, and the ISO

• Hyprland from hyprwm again, tracking their branch rather than a commit (#393)

Checks and CI

• Every nix job gets both caches, through the path the daemon trusts (#394)
• box-boot recognises distrobox's third way of failing offline (#392)

3 changes since v4.0.2-9.

Getting it

Omarchy 4.0.2, packaged for NixOS. Two images, and the difference
is what they carry.

nixarchy-v4.0.2-10.iso — 5.7G, carries the whole system closure. The install
copies rather than downloads and needs no network at all. Take this
one unless the download is what you mind.

GitHub will not accept a file that size, so it is split. Put it back
together and check it:

cat nixarchy-v4.0.2-10.iso.part-* > nixarchy-v4.0.2-10.iso
sha256sum -c --ignore-missing SHA256SUMS

nixarchy-v4.0.2-10-net.iso — 1.6G, downloads the desktop as it installs.
One file, no reassembly, and it needs a working network: its first
screen offers Wi-Fi if there is no cable.

sha256sum -c --ignore-missing SHA256SUMS

(--ignore-missing because one SHA256SUMS covers both images, and
nobody downloads both.)

Then write one to a USB stick and boot it. See
Fresh-machine install
for what happens next.

What's Changed

• box-boot recognises distrobox's third way of failing offline by @olafkfreund in #392
• Every nix job gets both caches, through the path the daemon trusts by @olafkfreund in #394
• Hyprland from hyprwm again, tracking their branch rather than a commit by @olafkfreund in #393

Full Changelog: v4.0.2-9...v4.0.2-10

v4.0.2-9 (experimental)

⚠️ Experimental — not yet verified on hardware

This release is published untested on real machines. CI installs
it in a VM; a VM exposes no NPU, one graphics device and no firmware
quirks, so a VM install passing says very little about a laptop.
Real installs have failed where every check was green.

The flake route (nixos-rebuild against this repo, see the
README) is the mature one and is what to use on a machine you care
about. The ISO installer is the least mature part of the project
and it partitions the disk before it can fail.

If you install from this image, please say how it went on the
release discussion — success as much as failure. The experimental
label comes off a release only once someone has reported a
successful install on physical hardware.

These notes could not be derived. The tooling that
reads what changed between v4.0.2-8 and v4.0.2-9 refused
rather than report nothing; see this job's log.
The images below are unaffected.

Getting it

Omarchy 4.0.2, packaged for NixOS. Two images, and the difference
is what they carry.

nixarchy-v4.0.2-9.iso — 5.6G, carries the whole system closure. The install
copies rather than downloads and needs no network at all. Take this
one unless the download is what you mind.

GitHub will not accept a file that size, so it is split. Put it back
together and check it:

cat nixarchy-v4.0.2-9.iso.part-* > nixarchy-v4.0.2-9.iso
sha256sum -c --ignore-missing SHA256SUMS

nixarchy-v4.0.2-9-net.iso — 1.6G, downloads the desktop as it installs.
One file, no reassembly, and it needs a working network: its first
screen offers Wi-Fi if there is no cable.

sha256sum -c --ignore-missing SHA256SUMS

(--ignore-missing because one SHA256SUMS covers both images, and
nobody downloads both.)

Then write one to a USB stick and boot it. See
Fresh-machine install
for what happens next.

What's Changed

• Make the lock screen, the user services, and first run actually work by @olafkfreund in #3
• Let another desktop's input method win by @olafkfreund in #4
• Cut an option that did nothing and a factory with one product by @olafkfreund in #5
• Tell the agent it is on NixOS, not Arch by @olafkfreund in #21
• omarchy reinstall does exist here, it just cannot finish by @olafkfreund in #22
• Relink agent skills on every rebuild, not once ever by @olafkfreund in #23
• Stop racing systemd-logind, and test the skill links by @olafkfreund in #24
• Web app keybindings opened the wrong browser, or none by @olafkfreund in #25
• Package the HEY CLI by @olafkfreund in #26
• Doctor: say when the default browser cannot be changed from the menu by @olafkfreund in #27
• The menu jsonc is the one file under ~/.config/omarchy you cannot edit by @olafkfreund in #28
• Package omawrite and omacalc by @olafkfreund in #29
• Package omacut and ttfx by @olafkfreund in #30
• A rebuild does not update a running session, and now we say so by @olafkfreund in #31
• Fail a hung job in half an hour, not six by @olafkfreund in #33
• Disk Usage opened nothing, and LocalSend could not be reached by @olafkfreund in #34
• Pin quickshell 0.3.1: 0.3.0's lock screen aborts on DPMS by @olafkfreund in #36
• The doctor was looking for commands that do not exist by @olafkfreund in #37
• ttfx is what the screensaver is made of, not an optional extra by @olafkfreund in #38
• README: what changed, and what proves each of it by @olafkfreund in #39
• A manual for the port, not a fork of Omarchy's by @olafkfreund in #40
• The manual looks like a manual now by @olafkfreund in #42
• Add nixarchy-pkg-add, and drive rebuilds through nh by @olafkfreund in #43
• A wordmark, instead of the word by @olafkfreund in #44
• The option index is not there to be found in a test VM by @olafkfreund in #52
• Answer "is it already installed" with the table, not with PATH by @olafkfreund in #55
• The front page never mentioned you can search for anything by @olafkfreund in #54
• Omarchy's Neovim config, without taking anyone's editor away by @olafkfreund in #56
• Two names, and the commands say which is which by @olafkfreund in #58
• Allow unfree by default, behind an option that actually works by @olafkfreund in #57
• One disk layout, declared once by @olafkfreund in #59
• Separate the machine from the guest it was hiding in by @olafkfreund in #60
• The flake the installer writes, written once and correctly by @olafkfreund in #61
• Ask, format, write the flake, install by @olafkfreund in #62
• Install without being asked by @olafkfreund in #63
• Make the installer actually install, and give it a VM to prove it in by @olafkfreund in #64
• An ISO that boots into an installer that looks like one by @olafkfreund in #65
• Say that the installer exists, and show it by @olafkfreund in #66
• Name the splash after the thing it is splashing by @olafkfreund in #67
• Show the install happening, not just its beginning and end by @olafkfreund in #68
• The installer, screen by screen — and a floppy disk we were offering to format by @olafkfreund in #71
• Bump pinned packages by @github-actions[bot] in #70
• Show what you do after the install finishes by @olafkfreund in #72
• The installer copies the system instead of rebuilding it by @olafkfreund in #73
• Say when the machine is rebuilding by @olafkfreund in #74
• Let the skill guard know about the eight skills that landed by @olafkfreund in #76
• An ISO that installs with no network by @olafkfreund in #77
• Fix checks.install, and measure the install by @olafkfreund in #78
• The install does not need a network, and the README said it did by @olafkfreund in #79
• Run the checks that need a real machine on a real machine by @olafkfreund in #80
• A tag builds an ISO somebody can download by @olafkfreund in #81
• The nightly's first real run found three bugs, all mine by @olafkfreund in #83
• The install check passed every time and never said so by @olafkfreund in #84
• A second image that downloads the desktop instead of carrying it by @olafkfreund in #82
• A size budget that fails, rather than a number in a comment by @olafkfreund in #85
• The installer owns the screen, from the first frame to the last by @olafkfreund in #88
• Tell people they can download it by @olafkfreund in #86
• install-iso hangs the same way install did by @olafkfreund in #89
• A catalogue of services, and a check that it stays usable by @olafkfreund in #97
• Bundled services, and the discipline that keeps them out of the way by @olafkfreund in #98
• Three files to edit, one line to import by @olafkfreund in #99
• A release short enough to finish by @olafkfreund in #101
• Services you can pick, rather than a list you can read by @olafkfreund in #100
• Tell people what the catalogue learned since they installed by @olafkfreund in #103
• Ollama the user already runs is theirs, not ours by @olafkfreund in #104
• Every rebuild leaves the last one bootable, and nothing said so by @olafkfreund in #110
• A roadmap, and CI to stop it lying by @olafkfre...