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

Feature: allow locking the bar to a fixed screen edge

Reported by iamcheyan · filed Sep 20, 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

Feature: allow locking the bar to a fixed screen edgerevision 1 · captured 2026-09-28 21:23 UTC via poll

Problem\n\nThe bar can be moved between the top, bottom, left, and right screen edges by dragging an empty area of the bar (or clicking and holding). Setting bar.position to "top" in ~/.config/omarchy/shell.json only sets the initial/current position; it does not disable the gesture.\n\nFor users who always want a top bar, this makes it easy to move the bar accidentally, especially with touchpads or imprecise pointing devices. The current workaround is to clone the built-in bar and modify its QML, which is fragile and prevents the custom bar from receiving upstream fixes automatically.\n\n### Requested feature\n\nAdd a user-configurable option to disable the bar-edge move gesture, for example:\n\n{\n "bar": {\n "position": "top",\n "allowPositionDrag": false\n }\n}\n\nAlternatively, a setting such as lockPosition: true would work. This should disable only moving the whole bar between screen edges; widget drag-reordering should remain available.\n\n### Expected behavior\n\nWith the option enabled, dragging empty bar space does not change the bar edge, and the bar remains at the configured position after shell reloads and restarts. Users who want to reposition it can re-enable the gesture or use the existing command/API.\n\nRelated issues: #8834, #7276, #6881

View raw text
### Problem\n\nThe bar can be moved between the top, bottom, left, and right screen edges by dragging an empty area of the bar (or clicking and holding). Setting bar.position to "top" in ~/.config/omarchy/shell.json only sets the initial/current position; it does not disable the gesture.\n\nFor users who always want a top bar, this makes it easy to move the bar accidentally, especially with touchpads or imprecise pointing devices. The current workaround is to clone the built-in bar and modify its QML, which is fragile and prevents the custom bar from receiving upstream fixes automatically.\n\n### Requested feature\n\nAdd a user-configurable option to disable the bar-edge move gesture, for example:\n\n{\n  "bar": {\n    "position": "top",\n    "allowPositionDrag": false\n  }\n}\n\nAlternatively, a setting such as lockPosition: true would work. This should disable only moving the whole bar between screen edges; widget drag-reordering should remain available.\n\n### Expected behavior\n\nWith the option enabled, dragging empty bar space does not change the bar edge, and the bar remains at the configured position after shell reloads and restarts. Users who want to reposition it can re-enable the gesture or use the existing command/API.\n\nRelated issues: #8834, #7276, #6881

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:36 UTC