Configure keybinds for keyboard-first workflows
Keyboard control accelerates repeatable workflows. When your hands stay on the keyboard, you maintain flow state longer and complete tasks faster. Keybinds in QuantenRam are designed to be intuitive and consistent with common development tools.
The best keybinds are the ones you actually use. It's better to have a few well-chosen shortcuts that you remember and use daily than a comprehensive set that you constantly have to look up. Start with the actions you perform most frequently and bind those first.
Map frequent actions to short bindings
The most common actions deserve the shortest key combinations. Single-modifier shortcuts (like Ctrl+S) are better than multi-modifier ones (like Ctrl+Shift+Alt+S). Reserve complex chords for rarely-used actions.
Avoid browser/OS conflicts
Some key combinations are reserved by the browser or operating system. Ctrl+T opens a new tab in most browsers. Ctrl+W closes the current tab. Avoid these or provide alternatives for different platforms.
Document shortcuts centrally
Keybinds only work if people know about them. Maintain a central reference, either in-app (like a help modal) or in documentation. Update it when you add or change shortcuts.
Default keybinds in QuantenRam
QuantenRam comes with a set of default keybinds designed for common workflows. These are optimized for the most frequent actions without conflicting with browser defaults.
// Default keybind configuration
{
"keybinds": {
"global": {
"?": "Show keyboard shortcuts help",
"/": "Focus search",
"esc": "Close modal / Cancel operation"
},
"chat": {
"ctrl+enter": "Send message",
"ctrl+shift+enter": "Send with reasoning",
"ctrl+k": "Clear conversation",
"ctrl+up": "Previous message",
"ctrl+down": "Next message"
},
"navigation": {
"g then d": "Go to dashboard",
"g then a": "Go to activity",
"g then k": "Go to API keys",
"g then s": "Go to settings"
}
}
}The navigation keybinds use the "g then" pattern popularized by Gmail and GitHub. This creates a namespace for navigation shortcuts without conflicting with single-key actions.
Custom keybinds
You can override default keybinds or add custom ones in your configuration. This is useful if you have muscle memory from other tools or specific workflows that aren't covered by defaults.
// Custom keybind overrides
{
"keybinds": {
"custom": {
"ctrl+shift+t": "Toggle theme",
"ctrl+shift+m": "Toggle model selector",
"alt+c": "Copy last response",
"alt+r": "Regenerate last response"
}
}
}When adding custom keybinds, test them across different browsers and operating systems. Mac uses Cmd where Windows/Linux use Ctrl, so multi-platform shortcuts should account for this.
Keybinds are about efficiency. The goal is to reduce friction for actions you perform repeatedly. Start small, build muscle memory, then add more shortcuts as needed.