[Feature Request] Command palette + config-file syntax for Custom Commands

[bitoneeight]

Problem

Two related asks for Custom Commands parity with Ghostty:

1. Command palette UI cmd+shirt+p
   Ghostty has a searchable command palette triggered by cmd+shirt+p — type to filter, Enter to run. Very efficient: no need to memorise a keybind for every command, just remember the command name.
   Muxy currently only triggers Custom Commands via assigned keybinds, which doesn't scale past ~5 commands before you forget the bindings.
   Proposal: cmd+shirt+p opens a fuzzy-search palette listing all Custom Commands by name. Optional description field shown as subtitle.

2. Config-file syntax
   Currently Custom Commands are GUI-only via Settings → Keyboard Shortcuts → Custom Commands. Would be great to define them as text in a config file for portability across machines and version control.
   Ghostty already has this pattern with command-palette-entry:
   command-palette-entry = title:Tree Full Folder Structure,description:List full folder structure including all sub folders,action:text:tree > folder_structure.txt

Thank you.

Proposed Solution

Proposed muxy equivalent (could live in ~/.config/muxy/config or similar):
custom-command = name:Tree Full Folder Structure,command:tree > folder_structure.txt,icon:folder,key:super+shift+t

Additional Context

Palette makes a large command set actually usable
Config-as-text makes it portable across machines via dotfiles
Matches the config-as-text philosophy already used for Ghostty integration

[saeedvaziry]

We have these shortcuts at the moment. have you tried them?

file quick open: Cmd+p
Search file contents: Cmd + shift + f
Comand pallet : Cmd + shift + O

[bitoneeight]

Hi Saeed Thanks for the reply. I knew about `Cmd+Shift+O`. That palette lists Muxy's built-in actions (new tab, split pane, etc.) — same as Ghostty's stock command palette. It doesn't list my *own custom commands*, and it doesn't read ` *command-palette-entry*` lines from `~/.config/ghostty/config`. I just tested: those entries are parsed by Ghostty's GUI app, not by libghostty, so Muxy never sees them. What I'm asking for is the same palette UX, but populated by *user-defined* shell commands — the equivalent of Ghostty's `command-palette-entry` setting. Right now Muxy's Custom Commands live in Settings → Keyboard Shortcuts → Custom Commands and can only be triggered by keybind. Two specific asks: 1. Surface those existing Custom Commands inside the `Cmd+Shift+O` palette (or a dedicated palette) so they're searchable by name *without needing a keybind*. 2. Allow defining them in a config file rather than the GUI, so they're portable via dotfiles. Ghostty's pattern example: ``` custom-command = name:Local IP,command:ipconfig getifaddr en0,icon:network custom-command = name:Tree Folder Structure,command:tree > folder_structure.txt,icon:folder,key:super+shift+t ``` The `key` field would be optional — that's the whole point: a palette means you don't need a keybind for every command. Happy to test a build if you ever want to prototype this. Thank you.

…

On Sat, 9 May 2026 at 23:52, Saeed Vaziry ***@***.***> wrote: *saeedvaziry* left a comment (muxy-app/muxy#394) <#394 (comment)> We have these shortcuts at the moment. have you tried them? file quick open: Cmd+p Search file contents: Cmd + shift + f Comand pallet : Cmd + shift + O — Reply to this email directly, view it on GitHub <#394 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AK7WIOMELNFSJ6XBEWPO45T4Z4LZNAVCNFSM6AAAAACYWX7VMOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DIMJSGQ2TIMRVHA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you authored the thread.Message ID: ***@***.***>

-- Regards Borden Li

[saeedvaziry]

Oh thats a cool idea