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-4184GitHub issuePublicReceived

Use hyprmon TUI for monitor configuration instead of editor

Reported by dlsvob · filed Mar 1, 2026Closed upstream on 2026-03-01 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.

Open at source
Received and recorded verbatim. Nothing has been checked yet.

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

Use hyprmon TUI for monitor configuration instead of editorrevision 1 · captured 2026-10-04 11:49 UTC via poll

Suggestion

When selecting Setup > Monitors from the omarchy menu, it currently opens monitors.conf in the user's editor via open_in_editor. This works, but requires users to know the Hyprland monitor config syntax.

hyprmon is a TUI tool purpose-built for Hyprland monitor configuration — it shows a visual layout, lets you drag monitors around, change resolution/scale/refresh rate, and writes the results back to monitors.conf. Much more approachable for users who aren't familiar with the config format.

Proposed change

In show_setup_menu() in omarchy-menu, change:

*Monitors*) open_in_editor ~/.config/hypr/monitors.conf ;;

to:

*Monitors*) present_terminal hyprmon ;;

And add hyprmon to omarchy-base.packages.

Why not a PR

This is a one-line change plus a package addition, but it's an opinionated UX decision — wanted to get the team's take before submitting code.

🤖 Generated with Claude Code

View raw text
## Suggestion

When selecting **Setup > Monitors** from the omarchy menu, it currently opens `monitors.conf` in the user's editor via `open_in_editor`. This works, but requires users to know the Hyprland monitor config syntax.

[hyprmon](https://github.com/erans/hyprmon) is a TUI tool purpose-built for Hyprland monitor configuration — it shows a visual layout, lets you drag monitors around, change resolution/scale/refresh rate, and writes the results back to `monitors.conf`. Much more approachable for users who aren't familiar with the config format.

## Proposed change

In `show_setup_menu()` in `omarchy-menu`, change:

```bash
*Monitors*) open_in_editor ~/.config/hypr/monitors.conf ;;
```

to:

```bash
*Monitors*) present_terminal hyprmon ;;
```

And add `hyprmon` to `omarchy-base.packages`.

## Why not a PR

This is a one-line change plus a package addition, but it's an opinionated UX decision — wanted to get the team's take before submitting code.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

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.