Configurable Shortcuts

[mohseenrm]

Hey folks!

First off, thanks for the amazing work in creating such a great TUI for interacting with AI models in the terminal! 🙌🏽 🚀

My dev workflow is mostly based in the terminal and often I configure zellij, neovim and other CLI utilities to not have any conflicting keybindings (OS or app wise).

Part of adopting this tool more widely for me and other tmux/multiplexer users is the friction with conflicting keymaps.

Ex: Ctrl + p/n/s, ... all collide with zellij and neovim controls.

Would it be possible to extend configuring keymaps via the existing crush.json? (resolving config would stay the same, but the content can help customize keybindings per project or globally applied)

./.crush.json
./crush.json
$HOME/.config/crush/crush.json

Configuration itself is stored as a JSON object:

{
    "keybindings": {
         // or however best currently used in the tool
         "NewSession": ["alt", "s"]
    }
}

This would allow a user to configure the keymaps that would make it easier for them to use crush, while also allowing other users flexibility on how they want to use the tool (different keyboard layouts might make some default combos harder to trigger).

Let me know your thoughts on this! I am fairly new to go lang, but familiar with CLI tools, would be happy to spin up a PR to support this!

Thanks.

[torarnv]

Yes please! The ctrl key is a bit out of reach for my finger memory. Would love to remap, and also to allow triggering commands with / and files with @ like in similar tools.

[uri]

Perhaps some defaults should be changed before a stable release. For example ctrl+p is up in most terminals, this is especially jarring in crush as ctrl+n does register properly as down, so if you're using to using both, it feels really off. But maybe this is argument for having modal based bindings, so if there's a list visible ctrl+p acts as up for example.

ctrl+f to move forward one character being overwritten is also not ideal.

I understand that it might be too late to change some defaults, so the ability to map your own bindings would be greatly appreciated too.