Plugin Control

Think of Sublime Text's classic Package Control or the VS Code Command Palette, but for Omarchy Quattro plugins.

Press Ctrl+P (or click the tray icon), type a few letters to fuzzy-search, and press Enter to install or remove a plugin.

Plugin Control keeps the full @HANCORE-linux community marketplace and local plugin state in a small cache, then filters it in process on every keypress.

Install

omarchy plugin add https://github.com/ilyaZar/plugin-control.git --enable

Plugin manifests cannot add global bindings. For a keyboard-only path, add this optional binding to your repo-managed or user-owned bindings.lua:

o.bind(
  "CTRL + P",
  "Plugin Control",
  "omarchy-shell shell toggle io.github.ilyazar.plugin-control '{}'"
)

Bare Ctrl+P is quick, but it replaces the usual application shortcut while the binding is active. Change the first string if that disrupts your setup.

Use

Start typing to search plugin names, IDs, descriptions, authors, and tags. Enter opens the selected plugin's available action; Ctrl+I shows details without changing anything.

Use either command to narrow the action first:

• plug-install: shows available installable plugins
• plug-remove: shows removable local plugins

Commands are not pinned. Type install, remove, plug-in, or plg-in to bring one forward, then press Tab or Enter to complete it. Search restarts after the colon. Backspace edits a plugin name normally; at an empty completed prefix, one press removes the trailing space and the next clears the command.

Useful keys:

Install behavior

Installs run in the background by default and report their result in the palette and a notification. The confirmation's Run in Omarchy terminal switch streams native prompts instead. Both paths use the confirmed catalog snapshot.

Plugins run unsandboxed inside the shell. Marketplace validation is not a security audit.

Start and stop

The lifecycle helper lives inside the installed plugin:

~/.config/omarchy/plugins/io.github.ilyazar.plugin-control/bin/plugin-control start
~/.config/omarchy/plugins/io.github.ilyazar.plugin-control/bin/plugin-control start --tray-hidden
~/.config/omarchy/plugins/io.github.ilyazar.plugin-control/bin/plugin-control stop

start uses the configured tray default. --tray-hidden and --tray-visible override it; stop disables the plugin.

Settings

Ctrl+S opens Plugin settings, Keybindings, and Cancel / Back. Use j/k, arrows, mouse, or Enter; Escape returns to the plugin list.

~/.config/omarchy/plugin-control/channels.yaml
~/.config/hypr/bindings.lua

settings:
  tray-icon-hidden: false

Plugin Control never rewrites the user-owned Ctrl+P binding. Its other shortcuts work only while the palette is focused. Saving a valid tray setting updates the live bar; a CLI flag overrides it until the YAML is saved again.

Settings use strict schema 2. Invalid edits keep the last valid schema-2 file; version 1 is not migrated.

Dependencies

• Omarchy Quattro and its shell
• Bash, curl, Git, and jq
• Ruby with Psych
• util-linux (flock and setsid)
• GNU coreutils (timeout)
• omarchy-launch-terminal for terminal installs

Plugin Control installs no packages and requests no elevated privileges.

Remove

Select Plugin Control under plug-remove: or right-click its bar icon and choose Remove Plugin Control. Both paths open the same No/Yes warning. The native command is:

omarchy plugin remove io.github.ilyazar.plugin-control

Remove the optional Ctrl+P binding separately. Native removal keeps:

• settings: ~/.config/omarchy/plugin-control/
• cache: ~/.cache/omarchy/plugin-control/
• action history: ~/.local/state/omarchy/plugin-control/

Development

tests/all.sh
shellcheck bin/plugin-control scripts/*.sh tests/*.sh
omarchy plugin validate .

License

MIT. See LICENSE.