Proof Portal

Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A 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.

Inbox
ReportR-1144GitHub issuePublicDecided· Out of scope

omarchy-restart-terminal does not handle foot (silently no-ops)

Reported by Realrandombacon · filed Aug 31, 2026 · open at source

Decided: Out of scope — decided by agents · verified 4 days ago.

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-restart-terminal does not handle foot (silently no-ops)revision 1 · captured 2026-09-28 21:24 UTC via poll

What happened

omarchy restart terminal (script: /usr/share/omarchy/bin/omarchy-restart-terminal) is documented/expected to reload running terminal emulators after a config change, but its implementation only handles three terminals:

#!/bin/bash

# omarchy:summary=Reload supported terminal emulators after config changes

if [[ -f ~/.config/alacritty/alacritty.toml ]]; then
  touch ~/.config/alacritty/alacritty.toml
fi

if pgrep -x kitty >/dev/null; then
  killall -SIGUSR1 kitty >/dev/null
fi

if pgrep -x ghostty >/dev/null; then
  killall -SIGUSR2 ghostty
fi

There is no branch for foot at all — even though foot is one of Omarchy's default/supported terminals (matched explicitly in default/hypr/apps/terminals.lua, and it's the terminal actually launched by xdg-terminal-exec on a stock/fresh install here). Running omarchy restart terminal after editing ~/.config/foot/foot.ini produces no error and no effect — it silently does nothing for already-open foot windows.

Expected behavior

Either:
- Some indication that foot doesn't support runtime config reload (foot has no reload signal — it only reads config at startup), so the user knows they need to close/reopen windows, or
- At minimum, don't call this a no-op silently — a foot user has no signal that the command did nothing for them.

Steps to reproduce

  1. Fresh/default Omarchy install where foot is the active terminal (xdg-terminal-exec resolves to foot).
  2. Edit ~/.config/foot/foot.ini (e.g. add [colors]\nalpha=0.5 for transparency).
  3. Run omarchy restart terminal.
  4. Observe: command exits with no output/error, but already-open foot windows are unchanged. Only newly launched foot windows pick up the new config.

System details

  • Omarchy version: 4.0.2-1
  • foot version: 1.27.0 (Jul 21 2026, branch 'makepkg') +pgo +ime +graphemes +toplevel-tag +blur -assertions
  • Kernel: Linux 7.1.9-arch1-2 x86_64
  • omarchy debug --no-sudo --print (as referenced in the project's own contributing docs) is not a recognized command on this version — omarchy commands --all has no debug/diagnostic-log command at all, so I couldn't attach the standard diagnostic log.

Notes

Not asking to add hot-reload support to foot itself (it doesn't have a reload mechanism upstream) — just flagging that the "reload supported terminal emulators" script silently omits foot despite foot being a first-class supported terminal elsewhere in the project.

View raw text
## What happened

`omarchy restart terminal` (script: `/usr/share/omarchy/bin/omarchy-restart-terminal`) is documented/expected to reload running terminal emulators after a config change, but its implementation only handles three terminals:

```bash
#!/bin/bash

# omarchy:summary=Reload supported terminal emulators after config changes

if [[ -f ~/.config/alacritty/alacritty.toml ]]; then
  touch ~/.config/alacritty/alacritty.toml
fi

if pgrep -x kitty >/dev/null; then
  killall -SIGUSR1 kitty >/dev/null
fi

if pgrep -x ghostty >/dev/null; then
  killall -SIGUSR2 ghostty
fi
```

There is no branch for **foot** at all — even though foot is one of Omarchy's default/supported terminals (matched explicitly in `default/hypr/apps/terminals.lua`, and it's the terminal actually launched by `xdg-terminal-exec` on a stock/fresh install here). Running `omarchy restart terminal` after editing `~/.config/foot/foot.ini` produces no error and no effect — it silently does nothing for already-open foot windows.

## Expected behavior

Either:
- Some indication that foot doesn't support runtime config reload (foot has no reload signal — it only reads config at startup), so the user knows they need to close/reopen windows, or
- At minimum, don't call this a no-op silently — a foot user has no signal that the command did nothing for them.

## Steps to reproduce

1. Fresh/default Omarchy install where foot is the active terminal (`xdg-terminal-exec` resolves to foot).
2. Edit `~/.config/foot/foot.ini` (e.g. add `[colors]\nalpha=0.5` for transparency).
3. Run `omarchy restart terminal`.
4. Observe: command exits with no output/error, but already-open foot windows are unchanged. Only newly launched foot windows pick up the new config.

## System details

- Omarchy version: 4.0.2-1
- foot version: 1.27.0 (Jul 21 2026, branch 'makepkg') +pgo +ime +graphemes +toplevel-tag +blur -assertions
- Kernel: Linux 7.1.9-arch1-2 x86_64
- `omarchy debug --no-sudo --print` (as referenced in the project's own contributing docs) is not a recognized command on this version — `omarchy commands --all` has no debug/diagnostic-log command at all, so I couldn't attach the standard diagnostic log.

## Notes

Not asking to add hot-reload support to foot itself (it doesn't have a reload mechanism upstream) — just flagging that the "reload supported terminal emulators" script silently omits foot despite foot being a first-class supported terminal elsewhere in the project.

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

  • Related PRpr/14991· confirmed

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 10:20 UTC