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

### What do you need?

There are a few options available to us to provide a better experience for users to configure their monitors. 

I think something like nwg-display is a little to heavy and doesn't fit the vibe of Omarchy but some candidates I do think could be fit are:
- [hyprdynamicmonitors](https://github.com/fiffeek/hyprdynamicmonitors)
- [display-tui](https://github.com/otto-bus-dev/display-tui)
- [hyprmon](https://github.com/erans/hyprmon)

It'd be great if people could explore these options and propose a solution for this that keeps things simple, still allows use of config files, and fits the overall Omarchy theme. It should also be able to accomplish this without needing a whole lot of rigging to support.

I don't utilize multiple displays, and I know @dhh doesn't either so it will likely require someone to pick up the torch on this one who does so we can ensure it's properly tested but also just have the motivation to tackle it.

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/7493· 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.

No decision has been recorded yet.