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-2012GitHub issuePublicFixed

omarchy-remove-preinstalls removes user-created webapps

Reported by IvyWi · filed Mar 1, 2026 · open at source

Decided: Out of scope — decided by agents · verified 3 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

omarchy-remove-preinstalls removes user-created webappsrevision 1 · captured 2026-09-28 21:29 UTC via poll

System details

Omarchy 3.4

What's wrong?

omarchy-webapp-remove-all (called by omarchy-remove-preinstalls) removes all webapps installed via omarchy-webapp-install, including ones created by the user after setup. It identifies webapps solely by the presence of Exec=omarchy-launch-webapp or Exec=omarchy-webapp-handler in .desktop files, with no distinction between preinstalled and user-created apps.

Steps to reproduce:
1. Complete Omarchy setup
2. Create a custom webapp with omarchy-webapp-install
3. Run omarchy-remove-preinstalls from the launcher
4. Custom webapp is removed along with the preinstalled ones

Expected behavior:
Only the webapps that ship with Omarchy by default (defined in install/packaging/webapps.sh) should be removed.

Actual behavior:
All webapps matching the exec pattern are removed, including user-created ones.

Possible fix:
Track preinstalled webapps by name (from webapps.sh) and only remove those specifically, rather than pattern-matching all webapp desktop files.

View raw text
### System details

Omarchy 3.4

### What's wrong?

omarchy-webapp-remove-all (called by omarchy-remove-preinstalls) removes all webapps installed via omarchy-webapp-install, including ones created by the user after  setup. It identifies webapps solely by the presence of Exec=omarchy-launch-webapp or Exec=omarchy-webapp-handler in .desktop files, with no distinction between preinstalled and user-created apps.

  Steps to reproduce:
  1. Complete Omarchy setup
  2. Create a custom webapp with omarchy-webapp-install
  3. Run omarchy-remove-preinstalls from the launcher
  4. Custom webapp is removed along with the preinstalled ones

  Expected behavior:
  Only the webapps that ship with Omarchy by default (defined in install/packaging/webapps.sh) should be removed.

  Actual behavior:
  All webapps matching the exec pattern are removed, including user-created ones.

  Possible fix:
  Track preinstalled webapps by name (from webapps.sh) and only remove those specifically, rather than pattern-matching all webapp desktop files.

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

  • Fixed bypr/8923· 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 02:37 UTC