← 2.1.7 Primitive inconclusive · runtime-test

Customizable Keyboard Shortcuts

Users can now customize keyboard shortcuts by:

Users can rebind keyboard shortcuts by editing ~/.claude/keybindings.json or running /keybindings, enabling ergonomic personalization, terminal-conflict avoidance, and accessibility remapping.

How It Works

The feature allows mapping key combinations to Claude Code actions via a JSON file. Users invoke /keybindings to enter an interactive editing flow, or directly edit ~/.claude/keybindings.json with bindings like:

{
  "ctrl+e": "submit",
  "ctrl+shift+c": "copy-last-response",
  "ctrl+shift+v": "paste-as-code"
}

Previously, keyboard shortcuts were hardcoded; this release enables per-user remapping.

Test Status: Manual-Only

Runtime testing for version 2.1.7 (tested 2026-01-16) cannot be automated because keyboard shortcuts require interactive terminal keypresses. Verifying key-to-action mapping demands live user input and terminal state verification—beyond programmatic test scope. The feature remains untested at runtime as of the official test run.

Why It Matters

Five use cases drive adoption: ergonomic preference (comfort-based remapping), terminal conflict resolution (avoiding tmux/shell collisions), power-user workflow (frequent-action shortcuts), accessibility (physical remapping needs), and tool consistency (matching keybindings across applications).

Caveat

The feature is live and documented, but lacks empirical runtime proof of correct key-to-action binding. Manual verification in an interactive session required before production reliance.

Evidence & receipt
  • file2.1.7/tests/01-keybindings/TEST-RESULTS.md
◇ ed25519 receipt
idprimitive_760036b925fea55c77e7f771
alged25519
pubkey9b87705613b1e2fd064d57fa75a6b679d2856ceafad6b1daa8f982493871b6dd
sig2900a46b69cfa857fc1d27b7dfee93c97fe944c8fef38700bc5b99765ce1e702ba4f3416788650ae72a651d3a454e563f5dec72059472b89679ae0d958924b05

Signed with an ed25519 key held off the repo. Anyone can verify against the published public key; nobody without the secret key can forge it. Click verify: it recomputes the signature in your browser. The signature proves integrity and authorship of this exact content — not a third-party timestamp or that the underlying claim is objectively true. signedAt is when the @f3/attest pipeline ran, not when the work happened; the evidence refs carry the source dates.

Connected