Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.
Windows VM installer should not enable boot-time restart by default
Reported by derekszen · filed Jul 28, 2026Closed upstream on 2026-07-30 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.
At a glance
- 1 · What is claimed?
- Only the report text below — no validator has restated it as checkable claims yet.
- 2 · What does it affect?
- Not yet mapped to any requirement or component.
- 3 · Is it reproducible?
- No validation has been run yet.
- 4 · What remains unclear?
- Not validated yet: no claims, no reproducer.
- 5 · What happens next?
- Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.
Original report
System details
AMD Ryzen 9 9950X3D, NVIDIA RTX 5090 D, 64 GiB RAM, Omarchy 3.8.4.
What's wrong?
omarchy-windows-vm install generates ~/.config/windows/docker-compose.yml with:
restart: unless-stoppedThis opts the Windows VM into Docker daemon restart behavior. If the VM is running when the machine reboots or crashes, Docker starts the VM again automatically during the next boot, before the user explicitly runs omarchy-windows-vm launch.
That behavior is surprising for an optional, resource-heavy desktop VM. On my system the VM is configured with 32 GiB RAM and consumed about 35 GiB of host memory immediately after boot. It contributed to severe memory pressure and OOM/swap exhaustion alongside other workloads.
The persistence is also not made sufficiently prominent during installation. The launch flow explains that the VM can keep running after RDP closes, but the generated Docker boot-restart policy is a separate and longer-lived behavior.
Steps to reproduce
- Run
omarchy-windows-vm install. - Observe
restart: unless-stoppedin~/.config/windows/docker-compose.yml. - Leave the Windows VM running.
- Reboot the machine, or recover from an unclean shutdown.
- Observe that Docker starts
omarchy-windowsautomatically during boot without an explicit Windows launch request.
Expected behavior
The safer default should be:
restart: "no"The VM would then start only through omarchy-windows-vm launch and stop through omarchy-windows-vm stop.
If automatic restart is intentionally retained, installation should make it an explicit opt-in and clearly warn that the VM will consume its configured RAM again whenever Docker starts after a reboot. A configurable choice between manual startup and persistent startup would also work.
Source
The policy is currently emitted by bin/omarchy-windows-vm in the generated Compose service.
View raw text
### System details AMD Ryzen 9 9950X3D, NVIDIA RTX 5090 D, 64 GiB RAM, Omarchy 3.8.4. ### What's wrong? `omarchy-windows-vm install` generates `~/.config/windows/docker-compose.yml` with: ```yaml restart: unless-stopped ``` This opts the Windows VM into Docker daemon restart behavior. If the VM is running when the machine reboots or crashes, Docker starts the VM again automatically during the next boot, before the user explicitly runs `omarchy-windows-vm launch`. That behavior is surprising for an optional, resource-heavy desktop VM. On my system the VM is configured with 32 GiB RAM and consumed about 35 GiB of host memory immediately after boot. It contributed to severe memory pressure and OOM/swap exhaustion alongside other workloads. The persistence is also not made sufficiently prominent during installation. The launch flow explains that the VM can keep running after RDP closes, but the generated Docker boot-restart policy is a separate and longer-lived behavior. ### Steps to reproduce 1. Run `omarchy-windows-vm install`. 2. Observe `restart: unless-stopped` in `~/.config/windows/docker-compose.yml`. 3. Leave the Windows VM running. 4. Reboot the machine, or recover from an unclean shutdown. 5. Observe that Docker starts `omarchy-windows` automatically during boot without an explicit Windows launch request. ### Expected behavior The safer default should be: ```yaml restart: "no" ``` The VM would then start only through `omarchy-windows-vm launch` and stop through `omarchy-windows-vm stop`. If automatic restart is intentionally retained, installation should make it an explicit opt-in and clearly warn that the VM will consume its configured RAM again whenever Docker starts after a reboot. A configurable choice between manual startup and persistent startup would also work. ### Source The policy is currently emitted by `bin/omarchy-windows-vm` in the generated Compose service.
Validation
Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.
Linked
Not linked to any known issue, other report or change yet.
Decision
Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.
No decision has been recorded yet.