Proof Portal

Sign in
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-1182GitHub issuePublicFixed

OS keyring error on Cursor

Reported by ChihweiLHBird · filed Aug 31, 2026 · open at source

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

OS keyring error on Cursorrevision 1 · captured 2026-09-28 21:24 UTC via poll

System details

Omarchy 4.0.2

What's wrong?

Error message:
> An OS keyring couldn't be identified for storing the encryption related data in your current desktop environment.

Similar to https://github.com/omacom/omarchy/issues/1015 but for Cursor.
https://github.com/omacom/omarchy/pull/8441 seems to be the solution but I didn't check the details of the git diff.

View raw text
### System details

Omarchy 4.0.2

### What's wrong?

Error message:
> An OS keyring couldn't be identified for storing the encryption related data in your current desktop environment.

Similar to https://github.com/omacom/omarchy/issues/1015 but for Cursor.
https://github.com/omacom/omarchy/pull/8441 seems to be the solution but I didn't check the details of the git diff.

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/8441· 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 10:13 UTC