Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA 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.
Automatic Extraction of Web Icon
Reported by MentalGear · filed Sep 15, 2025Closed upstream on 2026-02-01. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.
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?
Hey, thank you for sharing the gift of this minimalistic & efficient distro!
I noticed that omarchy-webapp-install currently requires specifying an icon path manually. However, I think the icon could also be automatically extracted from a website URL, which would greatly lower app install friction.
Here's a quick outline:
- If
manifest.jsonis available, use the path of the most high-res icon. - Otherwise fallback to scanning the HTML
<head>for<link rel="icon"> and <link rel="apple-touch-icon">. - Lastly look for
favicon.icoat default path
I could contribute this enhancement. But before putting the work into a pull request, I wanted to check (as it seems rather straightforward) if there is any reason why automatic icon extraction hasn’t been implemented yet?
Are there any edge cases, design constraints, or other considerations to keep in mind?
Looking forward to your thoughts!
View raw text
### What do you need? Hey, thank you for sharing the gift of this minimalistic & efficient distro! I noticed that [omarchy-webapp-install](https://github.com/basecamp/omarchy/blob/d09b6aa42a25e71e270ac8ac19e5ce3c17feb878/bin/omarchy-webapp-install#L4) currently requires specifying an icon path manually. However, I think the icon could also be automatically extracted from a website URL, which would greatly lower app install friction. Here's a quick outline: 1. If `manifest.json` is available, use the path of the most high-res icon. 2. Otherwise fallback to scanning the HTML `<head>` for `<link rel="icon"> and <link rel="apple-touch-icon">`. 3. Lastly look for `favicon.ico` at default path I could contribute this enhancement. But before putting the work into a pull request, I wanted to check (as it seems rather straightforward) if there is any reason why automatic icon extraction hasn’t been implemented yet? Are there any edge cases, design constraints, or other considerations to keep in mind? Looking forward to your thoughts!
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.