Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Guide and apply cmux keyboard shortcut customization. Use when the user asks to customize, rebind, unbind, reset, audit, or create shortcut templates for cmux, including tmux-style, Vim-style, terminal-first, browser-heavy, iTerm/Terminal-like, or agent-triage layouts.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-11 | ✗→✓ | ▲ Improved | 154% | 0% |
| case-12 | ✗→✓ | ▲ Improved | 88% | 0% |
| case-08 | ✗→✓ | ▲ Improved | 63% | 0% |
| case-09 | ✗→✓ | ▲ Improved | 126% | 0% |
| case-10 | ✗→✓ | ▲ Improved | 85% | 0% |
Turn a user's workflow preferences into cmux shortcut bindings in ~/.config/cmux/cmux.json: guide, propose compact templates, apply the selected changes, and confirm the config parses with recognized keys.
Every new cmux-owned keyboard shortcut must be added to Sources/KeyboardShortcutSettings.swift, visible and editable in Settings > Keyboard Shortcuts, supported as shortcuts.bindings.<actionId> in ~/.config/cmux/cmux.json, and documented in web/app/[locale]/(landing)/docs/keyboard-shortcuts/page.tsx and the configuration docs. All four, not a subset.
skills/cmux-settings/scripts/cmux-settings for every read/write. It reads JSONC, writes atomically, and validates JSON plus recognized settings keys.skills/cmux-settings/references/shortcut-actions.md. Current defaults: web/data/cmux-shortcuts.ts or Sources/KeyboardShortcutSettings.swift.bashif [[ -z "${CMUX_SETTINGS:-}" ]]; then root="$(git rev-parse --show-toplevel 2>/dev/null || pwd)" for candidate in \ "$root/skills/cmux-settings/scripts/cmux-settings" \ "${CODEX_HOME:-$HOME/.codex}/skills/cmux-settings/scripts/cmux-settings" \ "$HOME/.agents/skills/cmux-settings/scripts/cmux-settings"; do [[ -x "$candidate" ]] && CMUX_SETTINGS="$candidate" && break done [[ -n "${CMUX_SETTINGS:-}" ]] || { echo "cmux-settings helper not found; run from a cmux checkout or install cmux-settings" >&2 exit 1 } fi
shortcuts.bindings.<actionId>."cmd+b".["ctrl+b","c"]. The first stroke needs a modifier unless the key is Space. The second stroke can be bare.null for explicit unbinds. "", "none", "clear", "unbound", and "disabled" are accepted aliases, but null is the clearest JSON value and matches the templates below.selectSurfaceByNumber and selectWorkspaceByNumber must use a digit from 1 to 9. cmd+1 means the full cmd+1 through cmd+9 family.showHideAllWindows is the only system-wide shortcut. It cannot be a chord, requires modifiers, and may be rejected by macOS if reserved.globalSearch is application-scoped and only fires while cmux is active.showHideAllWindows also requires Settings > Global Hotkey > Enable System-Wide Hotkey. The binding can validate in cmux.json while the feature is disabled, so warn the user to enable that setting before reporting the shortcut as usable.unset deletes a cmux.json override. It does not clear shortcut changes saved through the Settings UI/UserDefaults. If the user asks for true built-in defaults, tell them to use Settings > Keyboard Shortcuts > Reset Default Shortcuts after clearing file-managed overrides, then verify in the app. For showHideAllWindows, use Settings > Global Hotkey to restore the shortcut to ctrl+opt+cmd+. because Keyboard Shortcuts > Reset Default Shortcuts intentionally skips the global hotkey.cmux.json live reloads. Never tell the user to restart cmux.unset rule above).bash "$CMUX_SETTINGS" path "$CMUX_SETTINGS" get shortcuts.bindings 2>/dev/null || printf '{}\n' "$CMUX_SETTINGS" validate
unset; a path with an existing custom value reverts with set <same-json-value>.bash "$CMUX_SETTINGS" get shortcuts.bindings.focusLeft 2>/dev/null || printf '<absent>\n'
"$CMUX_SETTINGS" validate.bash "$CMUX_SETTINGS" set shortcuts.bindings.newSurface '["ctrl+b","c"]' "$CMUX_SETTINGS" set shortcuts.bindings.focusLeft cmd+opt+h "$CMUX_SETTINGS" set shortcuts.bindings.sendFeedback null
"$CMUX_SETTINGS" get shortcuts.bindings.newSurface.Apply action by action, never by overwriting the whole shortcuts.bindings object.
One terminal-style namespace; ctrl+b starts a cmux chord instead of reaching the shell.
bash"$CMUX_SETTINGS" set shortcuts.bindings.newSurface '["ctrl+b","c"]' "$CMUX_SETTINGS" set shortcuts.bindings.closeTab '["ctrl+b","x"]' "$CMUX_SETTINGS" set shortcuts.bindings.nextSurface '["ctrl+b","n"]' "$CMUX_SETTINGS" set shortcuts.bindings.prevSurface '["ctrl+b","p"]' "$CMUX_SETTINGS" set shortcuts.bindings.selectSurfaceByNumber '["ctrl+b","1"]' "$CMUX_SETTINGS" set shortcuts.bindings.splitRight '["ctrl+b","v"]' "$CMUX_SETTINGS" set shortcuts.bindings.splitDown '["ctrl+b","s"]' "$CMUX_SETTINGS" set shortcuts.bindings.focusLeft '["ctrl+b","h"]' "$CMUX_SETTINGS" set shortcuts.bindings.focusDown '["ctrl+b","j"]' "$CMUX_SETTINGS" set shortcuts.bindings.focusUp '["ctrl+b","k"]' "$CMUX_SETTINGS" set shortcuts.bindings.focusRight '["ctrl+b","l"]' "$CMUX_SETTINGS" set shortcuts.bindings.toggleSplitZoom '["ctrl+b","z"]' "$CMUX_SETTINGS" set shortcuts.bindings.toggleTerminalCopyMode '["ctrl+b","["]' "$CMUX_SETTINGS" set shortcuts.bindings.equalizeSplits '["ctrl+b","="]'
These actions already match cmux built-in defaults, so clear file overrides rather than writing default values.
bashfor a in newSurface closeTab nextSurface prevSurface selectSurfaceByNumber \ splitRight splitDown toggleSplitZoom toggleTerminalCopyMode renameTab; do "$CMUX_SETTINGS" unset "shortcuts.bindings.$a" done
Prefix-free pane movement with no arrow keys.
bash"$CMUX_SETTINGS" set shortcuts.bindings.focusLeft cmd+opt+h "$CMUX_SETTINGS" set shortcuts.bindings.focusDown cmd+opt+j "$CMUX_SETTINGS" set shortcuts.bindings.focusUp cmd+opt+k "$CMUX_SETTINGS" set shortcuts.bindings.focusRight cmd+opt+l "$CMUX_SETTINGS" set shortcuts.bindings.splitRight cmd+opt+v "$CMUX_SETTINGS" set shortcuts.bindings.splitDown cmd+opt+s "$CMUX_SETTINGS" set shortcuts.bindings.toggleSplitZoom cmd+opt+z "$CMUX_SETTINGS" set shortcuts.bindings.equalizeSplits cmd+opt+=
Unread handling on one key family. toggleUnread stays on cmd+opt+u so this composes with Vim Pane Navigation without colliding with cmd+opt+j.
bash"$CMUX_SETTINGS" set shortcuts.bindings.showNotifications cmd+u "$CMUX_SETTINGS" set shortcuts.bindings.jumpToUnread cmd+j "$CMUX_SETTINGS" set shortcuts.bindings.markOldestUnreadAndJumpNext cmd+shift+j "$CMUX_SETTINGS" set shortcuts.bindings.toggleUnread cmd+opt+u "$CMUX_SETTINGS" set shortcuts.bindings.triggerFlash cmd+shift+h "$CMUX_SETTINGS" set shortcuts.bindings.focusRightSidebar cmd+shift+e
Workspaces and surfaces on distinct number and bracket lanes.
bash"$CMUX_SETTINGS" set shortcuts.bindings.selectWorkspaceByNumber cmd+1 "$CMUX_SETTINGS" set shortcuts.bindings.selectSurfaceByNumber cmd+opt+1 "$CMUX_SETTINGS" set shortcuts.bindings.nextSidebarTab 'cmd+opt+]' "$CMUX_SETTINGS" set shortcuts.bindings.prevSidebarTab 'cmd+opt+[' "$CMUX_SETTINGS" set shortcuts.bindings.nextSurface 'cmd+shift+]' "$CMUX_SETTINGS" set shortcuts.bindings.prevSurface 'cmd+shift+['
Return embedded-browser behavior to common macOS browser shortcuts. unset keeps future cmux defaults applying.
bashfor a in openBrowser focusBrowserAddressBar browserBack browserForward browserReload \ browserZoomIn browserZoomOut browserZoomReset toggleBrowserDeveloperTools \ showBrowserJavaScriptConsole find findNext findPrevious; do "$CMUX_SETTINGS" unset "shortcuts.bindings.$a" done
Fewer app-level shortcuts. Prefer unbinding only the actions the user names; this is a starting proposal.
bashfor a in renameTab renameWorkspace editWorkspaceDescription triggerFlash sendFeedback; do "$CMUX_SETTINGS" set "shortcuts.bindings.$a" null done
~/.config/cmux/settings.json unless the user explicitly asks; it is legacy fallback config.shortcuts.bindings unless the user wants a full replacement.shortcut-actions.md.cmux-settings validate. It validates JSON and supported keys, not shortcut syntax, macOS reservation, or focus-context conflicts.cmd+[ or cmd+] to application-scoped actions, warn that they collide with browser Back/Forward unless the browser actions are also changed or unbound.unset clears file-managed overrides for one action. Do not call that a built-in default reset unless Settings UI/UserDefaults values were also reset.Other measured skills in the registry, with their headline benchmark lift.