Skip to content

omarchy plugin clone produces an id the registry always rejects when the user is named omarchy #7118

Open

Description

@omarchybot

System details: Omarchy quattro @ 7488ead (post-4.0.0), QEMU/KVM VM, Hyprland session. Found by an automated QA pass; reproduced on a disposable worker VM.

omarchy plugin clone builds the new plugin id from $USER, with no check that the result avoids the reserved omarchy. namespace:

new_id="${USER:-$(id -un)}.${source_id#omarchy.}"

(bin/omarchy-plugin-clone:131)

The default user on the Omarchy ISO is literally omarchy — the name Omarchy's own docs use — so for that user every clone produces an id like omarchy.clock, which PluginRegistry then rejects:

for (var tk in thirdParty) {
  if (firstParty[tk] || String(tk).indexOf("omarchy.") === 0) {
    console.warn("PluginRegistry: plugin " + tk
      + " rejected: id is reserved for first-party Omarchy plugins")
    continue
  }

(shell/services/PluginRegistry.qml:602-608)

The CLI reports success, the built-in keeps rendering, and every edit the user makes to their clone is ignored forever:

$ whoami
omarchy
$ omarchy-plugin-clone omarchy.clock
Cloned omarchy.clock to /home/omarchy/.config/omarchy/plugins/omarchy.clock and switched to omarchy.clock

$ qs log -p $OMARCHY_PATH/shell | grep reserved
WARN qml: PluginRegistry: plugin omarchy.clock rejected: id is reserved for first-party Omarchy plugins

$ omarchy-shell shell listPlugins | grep clock
{'id': 'omarchy.clock', 'name': 'Clock', 'firstParty': True, 'clonedFrom': ''}   # still the built-in

$ grep '"name"' ~/.config/omarchy/plugins/omarchy.clock/manifest.json
  "name": "My Clock",                 # the clone exists on disk and is never loaded

Rejecting or re-prefixing an id that starts with omarchy. in omarchy-plugin-clone closes it.


Correction, after an independent review of this report:

Narrower than filed. This needs the effective $USER to be exactly omarchy, which is an explicitly configured account name rather than the default population of ISO installations -- the worker this was found on had that username set by its own provisioning, not by Omarchy. Where it does apply, the clone is silently ignored forever and the CLI still reports success.

Activity

  1. 686f6c61 commented on Aug 18, 2026

    @686f6c61

    I'll take this: if the derived clone id starts with omarchy., prefix it with user. so PluginRegistry will actually load the clone.

  2. 686f6c61 commented on Aug 18, 2026

    @686f6c61

    Opened #7366 — if the derived clone id starts with omarchy., prefix it with user. so PluginRegistry will load the copy.

  3. omarchybot commented on Oct 8, 2026

    @omarchybot
    CollaboratorAuthor

    Re-checked against quattro at e1614f2: the bug is still there. bin/omarchy-plugin-clone:131 still builds omarchy.<id> for a user named omarchy, and shell/services/PluginRegistry.qml:630 still rejects it while the clone command reports success.

    #7366 fixes it and is already linked to this issue. When the derived id would start with omarchy., it prefixes user., so the clone becomes user.omarchy.clock with clonedFrom still pointing at the built-in. That id passes omarchy-plugin-validate, the catalog does not treat it as first-party, and enable swaps it in for the built-in through clonedFrom, so nothing later in the chain rejects or misroutes it. One limit: a clone that was already made under the broken id is not repaired. It has to be removed and cloned again.

    I read the source and did not run anything for this issue. The pull request gets its own test run on a worker as a separate item. Codex Medium gave the second opinion, read the same code and reached the same conclusion; it may have seen this reasoning first, so its agreement is not independent.

    Next step: the maintainer decides on #7366.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions