Keyboard shortcuts

Most user-facing actions in Rumus have a keyboard shortcut. They’re all customizable from a single page: Settings → Keyboard Shortcuts.

​

How the page is organized

Shortcuts are grouped into sensible categories: There are roughly two dozen actions in total — every common terminal interaction has a binding you can change.

​

Rebind a shortcut

​

Conflict detection

If you bind a key combo that’s already in use by another action, Rumus tells you:

“This shortcut is already used by ''.”

You then choose to override (the previous binding loses the key) or cancel the change. There’s no silent collision — the page makes you decide.

​

Reset

Two reset paths:

• Reset this action — restore a single binding to its shipping default.
• Reset all to defaults — wipe every customization on the page. This one prompts for confirmation; there’s no undo.

​

What about chord shortcuts (Ctrl+K Ctrl+X style)?

Rumus’s keyboard system today supports single key combinations only — one modifier set + one key per binding. Multi-step chord bindings (the VS Code “Ctrl+K Ctrl+X” pattern) aren’t supported. If you need a complex combo that doesn’t fit a single chord, look for an existing single-chord binding nearby that you can repurpose.

​

Platform conventions

Rumus’s defaults follow each platform’s conventions:

• macOS — ⌘ for the primary modifier (e.g. ⌘C for copy).
• Windows / Linux — Ctrl for the primary modifier (e.g. Ctrl+C for copy).

Sync carries your bindings across devices, but the modifier semantics stay native — so ⌘C on your Mac becomes Ctrl+C on your Windows machine if you’ve kept the default.

​

Common rebindings

Some bindings people often want to change:

• Find in terminal — many users prefer Ctrl+F / Cmd+F even though some platforms default to a different key.
• Switch tab — Ctrl+1 … Ctrl+9 for direct tab access is a popular addition.
• Close tab vs Close window — be careful these don’t share modifiers; closing the wrong one is a fast way to lose work.

​

What ISN’T configurable here

A few things live elsewhere:

• AI sidebar toggle — currently the panel-right icon at the far right of the title bar (no key binding today).
• Workspace switching — managed from the workspace switcher.
• Smart autocomplete accept — bound on the same page (look under “Editing” or “Tabs & Windows” depending on the action label).

If a key in the app today does something but isn’t on this page, it’s a system / OS-level binding, not a Rumus one.

​

Settings sync

Custom keyboard bindings are part of config sync — set them once, propagate everywhere.

​

Next steps