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

bin scripts: user-visible OSD strings are hardcoded English, no i18n path

Reported by WokoFlipper · filed Sep 28, 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

bin scripts: user-visible OSD strings are hardcoded English, no i18n pathrevision 1 · captured 2026-09-28 21:23 UTC via poll

Problem

bin/omarchy-audio-input-mute sends user-visible OSD messages as literals:

omarchy-osd -i microphone-muted -m "Microphone muted"
omarchy-osd -i microphone -m "Microphone on"

On a non-English setup (e.g. Russian keyboard toggling mic mute), the OSD pops up in English while everything around it (binds, panel, notifications) is translated. There is currently no mechanism for locales to translate strings emitted by bin/ scripts — QML has i18n.t(), shell has nothing.

Proposal

Give scripts a lookup path for user-visible strings, for example:

  • a per-locale message catalog (e.g. under config/ or $OMARCHY_PATH/locale/) that scripts source, falling back to English when a key is missing;
  • or an omarchy-osd message-key mode (-k microphone-muted) resolved against the same catalogs QML uses.

Fail-closed to English keeps this safe: missing key = current behaviour.

Happy to pilot it on omarchy-audio-input-mute (two strings) if the approach sounds right.

View raw text
## Problem

`bin/omarchy-audio-input-mute` sends user-visible OSD messages as literals:

```bash
omarchy-osd -i microphone-muted -m "Microphone muted"
omarchy-osd -i microphone -m "Microphone on"
```

On a non-English setup (e.g. Russian keyboard toggling mic mute), the OSD pops up in English while everything around it (binds, panel, notifications) is translated. There is currently no mechanism for locales to translate strings emitted by `bin/` scripts — QML has `i18n.t()`, shell has nothing.

## Proposal

Give scripts a lookup path for user-visible strings, for example:

- a per-locale message catalog (e.g. under `config/` or `$OMARCHY_PATH/locale/`) that scripts source, falling back to English when a key is missing;
- or an `omarchy-osd` message-key mode (`-k microphone-muted`) resolved against the same catalogs QML uses.

Fail-closed to English keeps this safe: missing key = current behaviour.

Happy to pilot it on `omarchy-audio-input-mute` (two strings) if the approach sounds right.

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/7434· confirmed
  • Fixed bypr/11010· confirmed
  • Related PRpr/15117· 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 20:00 UTC