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-306GitHub issuePublicDecided· Out of scope

Omarchy 3 Updating Broken (no such ref was fetched)

Reported by pelephant2 · filed Sep 19, 2026Closed upstream on 2026-10-12 by the bot omarchybot, as a duplicate (target not recorded).

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 3 Updating Broken (no such ref was fetched)revision 1 · captured 2026-09-28 21:23 UTC via poll

System details

Omarchy 3.8.5

What's wrong?

I'm on Omarchy 3.8.5 and when I update through the menus, or with omarchy update, I get the following error:

your configuration specifies to merge with the ref 'refs/heads/master' from the remote,
but no such ref was fetched

and then I'm dropped back into the terminal without any updates.

View raw text
### System details

Omarchy 3.8.5

### What's wrong?

I'm on Omarchy 3.8.5 and when I update through the menus, or with `omarchy update`, I get the following error:
```
your configuration specifies to merge with the ref 'refs/heads/master' from the remote,
but no such ref was fetched
```
and then I'm dropped back into the terminal without any updates.

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.

  • Out of scopeDecided by agents · verified · 2026-10-09 16:05 UTC