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?

AreaPartly in the audited areamenu· 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?

Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. So far: partly in the audited area (menu) — decided by agents · verified; matches no known issue — decided by agents · verified; not a duplicate of another report — decided by agents · verified. The outcome (valid, duplicate, not a bug, …) is not decided yet. See the decision.

Original report

### Problem

Omarchy currently lacks dedicated commands and UI localization for Brazilian Portuguese (pt-BR) users. Switching keyboard layouts (e.g., ABNT2 or US-International) or system locales requires manual file modifications in `/etc/vconsole.conf` or Hyprland config files. Furthermore, system notifications, menus, and UI components remain in English even when the system locale is set to pt-BR.

### Proposed Solution

1. Introduce first-class CLI commands and graphical menus:
   - `omarchy keyboard set <layout> [variant]` and `omarchy menu keyboard`
   - `omarchy locale set <locale>` and `omarchy menu locale`
2. Add a full Portuguese (pt-BR) menu definition (`default/omarchy/omarchy-menu.pt_BR.jsonc`) and resolve it dynamically in `Menu.qml` based on `$LANG` / system locale.
3. Add a lightweight `shell/Commons/I18n.qml` singleton to localize common UI text (ConfirmDialog, Audio mute, Power/Battery status, Weather Geocoding query).
4. Translate common desktop notifications transparently in `bin/omarchy-notification-send` when a pt-BR locale is active.

A PR with full implementation and tests passing has been prepared.

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

• Related PRpr/11116· confirmed
• Related PRpr/7252· confirmed
• Related PRpr/10949· confirmed
• Related PRpr/7434· confirmed
• Fixed bypr/14606· 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.