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.
omarchy reminder: multi-day reminders silently lost on shutdown/reboot (no persistence)
Reported by N3onStack · filed Sep 10, 2026 · open at source
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?
- AreaOutside the audited area· Decided by agents · verified
- 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?
- Decided by agents and verified by a second, independent agent — see the decision.
Original report
omarchy reminder (/usr/bin/omarchy-reminder) implements reminders as transient systemd-run --user --collect --on-active=<N>m units, with the message text stored under $XDG_RUNTIME_DIR/omarchy-reminders/*.message (tmpfs).
Neither the timer unit nor the message file is persisted anywhere durable, and nothing replays "reminders that were due while the machine was off" on the next boot. So a reminder set for anything longer than "until the next shutdown" is silently lost the moment the machine powers off — with no warning to the user at set time.
Repro:
$ omarchy reminder 4320 "Check something in 3 days"
You'll be reminded at <time>
$ # shut the machine down, e.g. `systemctl poweroff`
$ # boot back up
$ omarchy reminder show --json
{"count":0,"active":false,"tooltip":"Set Reminder","reminders":[]}No notification, no log, no trace that a reminder ever existed — it's just gone.
I hit this concretely: set two 3-day reminders via omarchy reminder, then powered the machine off about two minutes later (planned shutdown, not a crash). Confirmed via journalctl --user that the corresponding omarchy-reminder-*.timer transient units were torn down with the rest of the user session at poweroff, and never fired.
Suggested fixes (any of):
- Persist reminders to a small state file under ~/.local/state/omarchy/reminders/ and re-arm anything still in the future (or fire anything now-past, e.g. within a grace window) from a post-boot/login hook.
- At minimum, warn the user at omarchy reminder <minutes> time if <minutes> is large enough that it's likely to outlive an uptime session (e.g. "this won't survive a shutdown/reboot").
Environment: Omarchy 4.0.3-1.
View raw text
`omarchy reminder` (`/usr/bin/omarchy-reminder`) implements reminders as transient `systemd-run --user --collect --on-active=<N>m` units, with the message text stored under `$XDG_RUNTIME_DIR/omarchy-reminders/*.message` (tmpfs).
Neither the timer unit nor the message file is persisted anywhere durable, and nothing replays "reminders that were due while the machine was off" on the next boot. So a reminder set for anything longer than "until the next shutdown" is silently lost the moment the machine powers off — with no warning to the user at set time.
**Repro:**
```
$ omarchy reminder 4320 "Check something in 3 days"
You'll be reminded at <time>
$ # shut the machine down, e.g. `systemctl poweroff`
$ # boot back up
$ omarchy reminder show --json
{"count":0,"active":false,"tooltip":"Set Reminder","reminders":[]}
```
No notification, no log, no trace that a reminder ever existed — it's just gone.
I hit this concretely: set two 3-day reminders via `omarchy reminder`, then powered the machine off about two minutes later (planned shutdown, not a crash). Confirmed via `journalctl --user` that the corresponding `omarchy-reminder-*.timer` transient units were torn down with the rest of the user session at poweroff, and never fired.
**Suggested fixes (any of):**
- Persist reminders to a small state file under `~/.local/state/omarchy/reminders/` and re-arm anything still in the future (or fire anything now-past, e.g. within a grace window) from a post-boot/login hook.
- At minimum, warn the user at `omarchy reminder <minutes>` time if `<minutes>` is large enough that it's likely to outlive an uptime session (e.g. "this won't survive a shutdown/reboot").
Environment: Omarchy 4.0.3-1.
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.
- Out of scopeDecided by agents · verified · 2026-10-09 11:26 UTC