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

Ideas for first class support for Windows applications

Reported by michaelshmitty · filed Sep 13, 2025Closed upstream on 2026-02-01 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.

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

Ideas for first class support for Windows applicationsrevision 1 · captured 2026-10-04 11:35 UTC via poll

What do you need?

(Some) Windows applications work quite well once you install Wine (menu -> install -> package -> wine).
.exe files are automatically associated with Wine and execute when you double click them in the file browser. I did have to fiddle with winecfg and scale the DPI under the Graphics tab way up to make applications readable, but this may be display hardware dependent.

User swork1 over on X asked about Sierra Chart (https://www.sierrachart.com/) and if the experience of running Windows apps in Omarchy can be improved.

<img width="2880" height="1920" alt="Image" src="https://github.com/user-attachments/assets/3e1aad55-9b03-488b-9e69-0cc549cff4c5" />

I don't know if there is enough demand for having a better out of the box Windows applications experience, but I promised to look into it and here are some ideas:

  • Have Wine installed with a default Omarchy installation
  • If possible, pre-generate configuration in ~/.wine
  • Have a simple (Gum?) TUI that allows you to add installed windows applications (in ~/.wine/drive_c/...) to the app launcher, similar to how web apps are added.

If enough demand, I or someone else may look into this.

View raw text
### What do you need?

(Some) Windows applications work quite well once you install [Wine](https://www.winehq.org/) (menu -> install -> package -> wine).
`.exe` files are automatically associated with Wine and execute when you double click them in the file browser. I did have to fiddle with `winecfg` and scale the DPI under the _Graphics_ tab way up to make applications readable, but this may be display hardware dependent.

User [swork1](https://x.com/swork_/status/1965132353950642685) over on X asked about Sierra Chart (https://www.sierrachart.com/) and if the experience of running Windows apps in Omarchy can be improved.

<img width="2880" height="1920" alt="Image" src="https://github.com/user-attachments/assets/3e1aad55-9b03-488b-9e69-0cc549cff4c5" />

I don't know if there is enough demand for having a better out of the box Windows applications experience, but I promised to look into it and here are some ideas:

* Have Wine installed with a default Omarchy installation
* If possible, pre-generate configuration in `~/.wine`
* Have a simple (Gum?) TUI that allows you to add installed windows applications (in `~/.wine/drive_c/...`) to the app launcher, similar to how web apps are added.

If enough demand, I or someone else may look into this.
  • 3e1aad55-9b03-488b-9e69-0cc549cff4c5

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.