Skip to content

Plugin clone silently rejected when username collapses id back into omarchy. namespace #12678

Closed as duplicate

Description

@csmithnaill

Title: Plugin clone silently rejected when username collapses id back into omarchy. namespace

Body:

What happened: Running omarchy plugin clone omarchy.menu (or any built-in plugin) reports success, but the cloned plugin never loads — it's silently rejected by the live shell.

Cause: omarchy-plugin-clone names clones ${USER}.${source_id#omarchy.}. When the login user is omarchy (the name Omarchy's own installer suggests by default), this collapses back to omarchy.<id> — the same id as the original. PluginRegistry.qml (~line 630) unconditionally rejects any third-party plugin id in the omarchy. namespace, reserved for first-party plugins. The CLI's own success check only greps plugin manifests on disk, not the live accepted registry, so it never catches this.

Where the rejection actually shows: only in the quickshell log at /run/user/1000/quickshell/by-id/<instance>/log.log — nowhere in any omarchy CLI output.

Steps to reproduce:

  1. Fresh Omarchy install, keep the suggested default username omarchy.
  2. omarchy plugin clone omarchy.menu
  3. omarchy plugin list shows the clone as present, but it never becomes the active menu / never loads.

Expected: Either the clone command should reject/rename ids that would collide with the first-party namespace, or it should warn clearly instead of reporting silent success.

Workaround: manually edit the clone's manifest.json, change "id" to something outside omarchy. (e.g. local.<plugin>), keep clonedFrom pointing at the original id, then omarchy-shell shell rescanPlugins and omarchy plugin enable <new-id>.

System details:

  • Omarchy version: 4.0.3-3 (try-omarchy-runtime package — running via TryOmarchy on Windows/QEMU)
  • Likely affects any fresh install that keeps the installer's suggested default username omarchy

Activity

  1. omarchybot commented on Oct 12, 2026

    @omarchybot
    Collaborator

    Confirmed and reproduced on quattro, on a worker whose login user is omarchy: omarchy plugin clone omarchy.weather printed "switched to omarchy.weather" while the shell kept only the built-in and logged PluginRegistry: plugin omarchy.weather rejected: id is reserved for first-party Omarchy plugins.

    The cause is as you describe, with one correction. The clone command's success check doesn't read manifests on disk. It asks the running shell (omarchy-shell shell listPlugins) whether a plugin with the new id exists, and the built-in omarchy.menu answers to that id. So the check passes, and omarchy-plugin-enable omarchy.menu re-enables the built-in.

    The fix is up as #15142. When the derived id would land in omarchy., the clone is named local.<id> instead, and clonedFrom still points at the built-in. On the same worker, omarchy.menu then cloned to local.menu, the shell loaded and enabled it, and omarchy plugin remove local.menu restored the built-in. A regression test in plugin-clone-test.sh fails against the old script and passes with the fix. The CLI suite passes; the shell suite's failures are the same with or without the change, and none of them involves plugins.

    Opus 5.5 diagnosed and fixed this; Codex Medium reviewed it as a second opinion. It confirmed the mechanism independently from source, pointed out that a username like omarchy.dev would hit the same thing (now covered), and caught a wording problem and a weak test assertion, both fixed. Its last round found nothing open. Next is the maintainer's review of #15142; until it merges, your workaround of renaming the clone's id outside omarchy. is the way around it.

  2. jandrusk commented on Oct 12, 2026

    @jandrusk

    Still seeing this on the plugin clone path when the clone id collapses back into the reserved omarchy.* namespace (same failure mode as #7118).

    Live quattro still rejects omarchy.* clones in PluginRegistry / omarchy-plugin-validate. Open fixes in flight:

    Happy to treat this as a duplicate of #7118 and track the fix on #15142 unless there’s a distinct repro beyond the username-collapse case.

  3. omarchybot commented on Oct 13, 2026

    @omarchybot
    Collaborator

    Closing this as a duplicate of #7118, as @jandrusk suggested. Both report the same bug with the same cause: for a user named omarchy, bin/omarchy-plugin-clone derives the clone id omarchy.<id>, PluginRegistry.qml rejects it as reserved for first-party plugins, and the CLI still reports success. Both ask for the same fix: keep the derived id out of the omarchy. namespace. #7118 was filed first, on 2026-08-16, so the fix is tracked there. This report adds no separate reproduction beyond the username collapse.

    Two open pull requests fix it, and the maintainer picks between them: #7366 (linked to #7118), which prefixes user., and #15142 (linked here), which renames the clone to local.<id>. Until one merges, your workaround of renaming the clone's id outside omarchy. still works.

    Opus 5.5 compared the two issues. Codex Medium gave the second opinion on whether they are the same. If this turns out to be a different bug, reopen it.

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 workingduplicateThis issue or pull request already exists

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions