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

omarchy plugin clone omarchy.bar produces a plugin that can never load (required properties)

Reported by tinterian · filed Sep 5, 2026Closed upstream on 2026-09-20 by bjarneo via an automated message, as a duplicate of #6915 (R-1851). GitHub close reason: completed.

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

omarchy plugin clone omarchy.bar produces a plugin that can never load (required properties)revision 1 · captured 2026-10-04 12:10 UTC via poll

What happened

omarchy plugin clone omarchy.bar is documented as the supported way to customize the status bar. But the clone it produces cannot actually load as a third-party plugin, with zero edits, because the shipped Bar.qml declares its host-injected properties as required:

// shell/plugins/bar/Bar.qml
required property string omarchyPath
required property var barWidgetRegistry
required property var barConfig

This works for the built-in bar because it's instantiated inline in shell.qml as a Component with all three bound directly at construction time:

Component {
  id: defaultBarComponent
  Bar {
    omarchyPath: shell.omarchyPath
    barWidgetRegistry: shell.barWidgetRegistry
    barConfig: shell.barConfig
    shell: shell
    manifest: shell.barManifestFor(shell.defaultBarId)
  }
}

A cloned bar, however, is loaded by pluginBarLoader, a plain Loader { source: url }. Quickshell can only assign properties to that item after it's constructed (via shell.configureBar(item, ...) in onLoaded), and QML's required contract demands they be set atomically at construction. Any bar cloned this way — even completely unedited — fails to load.

Steps to reproduce

  1. omarchy plugin clone omarchy.bar
  2. omarchy restart shell
  3. The bar disappears (see basecamp/omarchy#10324 for why the fallback-to-stock-bar path also silently fails here, compounding this).
  4. Quickshell's log shows:
   WARN scene: file:///home/<user>/.config/omarchy/plugins/<user>.bar/Bar.qml[15:3]: Required property omarchyPath was not initialized
   WARN scene: file:///home/<user>/.config/omarchy/plugins/<user>.bar/Bar.qml[17:3]: Required property barWidgetRegistry was not initialized
   WARN scene: file:///home/<user>/.config/omarchy/plugins/<user>.bar/Bar.qml[22:3]: Required property barConfig was not initialized

Expected

omarchy plugin clone omarchy.bar produces a bar that loads and renders identically to the stock bar, ready for further customization — this is the whole point of the clone workflow (see the plugin docs: "Clone a built-in Omarchy shell plugin into your own config").

Actual

The freshly cloned, unedited bar fails to load at all.

System

  • Omarchy: 4.0.0-1 (stable channel)
  • Hyprland: 0.56.2
  • Quickshell: 0.3.0 (quickshell-git AUR)
  • uname -a: Linux 7.1.8-arch1-3 x86_64

Suggested fix

Either:
- Change the shipped Bar.qml's three host-injected properties from required property to plain property with safe defaults (e.g. property string omarchyPath: "", property var barWidgetRegistry: ({ widgets: ({}) }), property var barConfig: null), matching how manifest and shell are already declared as plain (non-required) properties right below them; or
- Have pluginBarLoader construct the item with initial properties supplied atomically (e.g. Loader.setSource(url, {omarchyPath: ..., barWidgetRegistry: ..., barConfig: ...}) or Component.createObject(parent, {...})) instead of relying on post-construction assignment in onLoaded.

The first option is the smaller, more contained fix and is what I applied locally to unblock a custom-bar clone.

View raw text
### What happened

`omarchy plugin clone omarchy.bar` is documented as the supported way to customize the status bar. But the clone it produces cannot actually load as a third-party plugin, with zero edits, because the shipped `Bar.qml` declares its host-injected properties as `required`:

```qml
// shell/plugins/bar/Bar.qml
required property string omarchyPath
required property var barWidgetRegistry
required property var barConfig
```

This works for the built-in bar because it's instantiated inline in `shell.qml` as a `Component` with all three bound directly at construction time:

```qml
Component {
  id: defaultBarComponent
  Bar {
    omarchyPath: shell.omarchyPath
    barWidgetRegistry: shell.barWidgetRegistry
    barConfig: shell.barConfig
    shell: shell
    manifest: shell.barManifestFor(shell.defaultBarId)
  }
}
```

A cloned bar, however, is loaded by `pluginBarLoader`, a plain `Loader { source: url }`. Quickshell can only assign properties to that item *after* it's constructed (via `shell.configureBar(item, ...)` in `onLoaded`), and QML's `required` contract demands they be set atomically at construction. Any bar cloned this way — even completely unedited — fails to load.

### Steps to reproduce

1. `omarchy plugin clone omarchy.bar`
2. `omarchy restart shell`
3. The bar disappears (see basecamp/omarchy#10324 for why the fallback-to-stock-bar path also silently fails here, compounding this).
4. Quickshell's log shows:
   ```
   WARN scene: file:///home/<user>/.config/omarchy/plugins/<user>.bar/Bar.qml[15:3]: Required property omarchyPath was not initialized
   WARN scene: file:///home/<user>/.config/omarchy/plugins/<user>.bar/Bar.qml[17:3]: Required property barWidgetRegistry was not initialized
   WARN scene: file:///home/<user>/.config/omarchy/plugins/<user>.bar/Bar.qml[22:3]: Required property barConfig was not initialized
   ```

### Expected

`omarchy plugin clone omarchy.bar` produces a bar that loads and renders identically to the stock bar, ready for further customization — this is the whole point of the clone workflow (see the plugin docs: "Clone a built-in Omarchy shell plugin into your own config").

### Actual

The freshly cloned, unedited bar fails to load at all.

### System

- Omarchy: 4.0.0-1 (stable channel)
- Hyprland: 0.56.2
- Quickshell: 0.3.0 (quickshell-git AUR)
- `uname -a`: Linux 7.1.8-arch1-3 x86_64

### Suggested fix

Either:
- Change the shipped `Bar.qml`'s three host-injected properties from `required property` to plain `property` with safe defaults (e.g. `property string omarchyPath: ""`, `property var barWidgetRegistry: ({ widgets: ({}) })`, `property var barConfig: null`), matching how `manifest` and `shell` are already declared as plain (non-required) properties right below them; or
- Have `pluginBarLoader` construct the item with initial properties supplied atomically (e.g. `Loader.setSource(url, {omarchyPath: ..., barWidgetRegistry: ..., barConfig: ...})` or `Component.createObject(parent, {...})`) instead of relying on post-construction assignment in `onLoaded`.

The first option is the smaller, more contained fix and is what I applied locally to unblock a custom-bar clone.

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.