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

TUI shortcuts created incorrectly when default terminal set to Ghostty

Reported by prepin · filed Sep 22, 2025Closed upstream on 2025-09-26 by ryanrhughes, as a duplicate of #1820 (R-2954). GitHub close reason: duplicate.

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

TUI shortcuts created incorrectly when default terminal set to Ghosttyrevision 1 · captured 2026-10-04 11:35 UTC via poll

System details

Omarchy v3.0.1

What's wrong?

What happens:
When the default terminal is set to Ghostty, TUI app shortcuts are generated with Alacritty-style parameters. This results in an error window when launching the shortcut.

Steps to reproduce:
1. Install Ghostty and check if it is set as default terminal in ~/.config/uwsm/default.
2. Install some TUI app, for example yay -S lazysql-bin
3. Create TUI shortcut using Omarchy Menu => Install TUI

Observed result:
Launching the TUI produces an error:

<img width="1340" height="814" alt="Image" src="https://github.com/user-attachments/assets/121de5a6-3dc6-4218-9ea5-0ea54acfce53" />

Why this happens:

The generated .desktop file in ~/.local/share/applications contains:

Exec=ghostty --class TUI.tile -e lazysql

The options --class and -e are common between Alacritty and Ghostty, but Ghostty requires class=TUI.tile style and the installer uses the Alacritty style class TUI.tile (note the = sign).

Possible solutions:
TUIs are always created with Alacritty, regardless of current default terminal or*
* TUI shortcuts are adapted to current default terminal (for example via wrapper script).

View raw text
### System details

Omarchy v3.0.1

### What's wrong?

**What happens:**
When the default terminal is set to Ghostty, TUI app shortcuts are generated with Alacritty-style parameters. This results in an error window when launching the shortcut.

**Steps to reproduce:**
1. Install Ghostty and check if it is set as default terminal in `~/.config/uwsm/default`.
2. Install some TUI app, for example  `yay -S lazysql-bin`
3. Create TUI shortcut using Omarchy Menu => Install TUI

**Observed result:**
Launching the TUI produces an error:

<img width="1340" height="814" alt="Image" src="https://github.com/user-attachments/assets/121de5a6-3dc6-4218-9ea5-0ea54acfce53" />

**Why this happens:**

The generated `.desktop` file in `~/.local/share/applications` contains:
```
Exec=ghostty --class TUI.tile -e lazysql
```
The options `--class` and `-e` are common between Alacritty and Ghostty, but Ghostty requires `class=TUI.tile` style and the installer uses the Alacritty style `class TUI.tile` (note the `=` sign).

**Possible solutions:**
* TUIs are always created with Alacritty, regardless of current default terminal **or**
* TUI shortcuts are adapted to current default terminal (for example via wrapper script).
  • 121de5a6-3dc6-4218-9ea5-0ea54acfce53

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.