Proof Portal

Sign in
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-1911GitHub issuePublicDecided· Out of scope

Add support for footclient

Reported by YouKnow-sys · filed Jun 23, 2026 · open at source

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

Add support for footclientrevision 1 · captured 2026-09-28 21:29 UTC via poll

System details

Omarchy 3.8.2

What's wrong?

right now when we select foot as the default terminal omarchy always run the standalone foot. A good thing about foot is it supports running a server so new terminal instances can be opened instantly using footclient with a near-zero memory footprint.

Currently, there is no official support for footclient in the configuration. Even if a user manually adds it to xdg-terminals.list, it breaks the floating layouts for all Omarchy TUI apps (like btop, bluetui, impala) because the window class defaults back to footclient instead of matching the expected custom app IDs.

Could we add native support for footclient in xdg-terminals.list and update the master Hyprland window rules to properly catch the footclient class so it floats correctly?

View raw text
### System details

Omarchy 3.8.2

### What's wrong?

right now when we select foot as the default terminal omarchy always run the standalone `foot`. A good thing about foot is it supports running a server so new terminal instances can be opened instantly using `footclient` with a near-zero memory footprint.

Currently, there is no official support for `footclient` in the configuration. Even if a user manually adds it to `xdg-terminals.list`, it breaks the floating layouts for all Omarchy TUI apps (like btop, bluetui, impala) because the window class defaults back to `footclient` instead of matching the expected custom app IDs.

Could we add native support for footclient in xdg-terminals.list and update the master Hyprland window rules to properly catch the `footclient` class so it floats correctly?

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/14543· 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 03:55 UTC