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-3573GitHub issuePublicReceived

10th workspace is no longer accessible

Reported by pelephant2 · filed Oct 29, 2025Closed upstream on 2025-10-29 by its own reporter pelephant2. GitHub close reason: completed. Closed by its own reporter — not by itself evidence of a fix.

Received and recorded verbatim. Nothing has been checked yet.

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

10th workspace is no longer accessiblerevision 1 · captured 2026-10-04 11:42 UTC via poll

System details

Nvidia 4080, Omarchy 3.1.4

What's wrong?

My 10th workspace is no longer accessible with Super + 0. The tenth workspace used to be accessible in this manner but no more since the last Omarchy update. The 10th workpace does show up on my Waybar however, I just can't navigate to it with Super + 0.

I looked in Learn > Keyboard Shortcuts and noticed Super + 0 is no longer listed (was it ever?). Is this intentional? Can I get the tenth workspace back? I use a lot of programs, virtual machines, etc. and need all 10 workspaces if possible.

Here's my ~/.config/waybar/config.jsonc:

...
    "hyprland/workspaces": {
    "on-click": "activate",
    "format": "{icon}",
    "format-icons": {
      "default": "",
      "1": "1",
      "2": "2",
      "3": "3",
      "4": "4",
      "5": "5",
      "6": "6",
      "7": "7",
      "8": "8",
      "9": "9",
      "10": "0",
      "active": ""
    },
    "persistent-workspaces": {
      "1": [],
      "2": [],
      "3": [],
      "4": [],
      "5": [],
      "6": [],
      "7": [],
      "8": [],
      "9": [],
      "10": []
    }
  },
...
View raw text
### System details

Nvidia 4080, Omarchy 3.1.4

### What's wrong?

My 10th workspace is no longer accessible with `Super + 0`. The tenth workspace used to be accessible in this manner but no more since the last Omarchy update. The 10th workpace does show up on my Waybar however, I just can't navigate to it with `Super + 0`.

I looked in `Learn > Keyboard Shortcuts` and noticed `Super + 0` is no longer listed (was it ever?). Is this intentional? Can I get the tenth workspace back? I use a lot of programs, virtual machines, etc. and need all 10 workspaces if possible.

Here's my `~/.config/waybar/config.jsonc`:

````
...
    "hyprland/workspaces": {
    "on-click": "activate",
    "format": "{icon}",
    "format-icons": {
      "default": "",
      "1": "1",
      "2": "2",
      "3": "3",
      "4": "4",
      "5": "5",
      "6": "6",
      "7": "7",
      "8": "8",
      "9": "9",
      "10": "0",
      "active": ""
    },
    "persistent-workspaces": {
      "1": [],
      "2": [],
      "3": [],
      "4": [],
      "5": [],
      "6": [],
      "7": [],
      "8": [],
      "9": [],
      "10": []
    }
  },
...
````

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.