Customizable Keyboard Shortcuts — runtime test

Hands-on runtime battle-test of Customizable Keyboard Shortcuts. Result: INCONCLUSIVE.

Customizable Keyboard Shortcuts (2.1.7) — a Claude Code feature enabling remappable key bindings via ~/.claude/keybindings.json.

What It Does

Users can remap terminal keyboard shortcuts by editing a JSON configuration file or running the /keybindings command. The feature ships with sensible defaults (e.g., ctrl+e to submit, ctrl+shift+c to copy) and allows ergonomic, accessibility, and workflow-specific customization. Previously keyboard shortcuts were hardcoded; this release adds personalization.

Test Design and Result

The test suite attempted automated verification on 2026-01-16 against version 2.1.7 features running on 2.1.9. However, automated testing proved infeasible: keyboard shortcuts require interactive terminal input, real key-press-to-action mapping, and the /keybindings command is itself interactive. Automated harnesses cannot inject terminal key events reliably. Result: INCONCLUSIVE. The feature was not runtime-tested.

Expected Usage

Example binding configuration:

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

Primary use cases include ergonomic remapping, avoiding terminal/tmux conflicts, accessibility accommodation, and workflow consistency across tools.

Remaining Gap

Manual interactive testing is required to verify that key presses actually map to intended actions. The test harness identified this as a blocker but did not execute hands-on verification. Epistemic status: untested runtime behavior.

Primary source

⎘ 2.1.7/tests/01-keybindings/TEST-RESULTS.mdverbatim from the corpus

Test Results: Customizable Keyboard Shortcuts

Feature: Customizable keyboard shortcuts via ~/.claude/keybindings.json

Tested: 2026-01-16 Version: 2.1.7 features on 2.1.9

Feature Description

Users can now customize keyboard shortcuts by:

Running /keybindings command
Editing ~/.claude/keybindings.json

Documentation: https://code.claude.com/docs/en/keybindings

Test Result: MANUAL REQUIRED

Cannot test programmatically because:

Keyboard shortcuts require interactive terminal
Would need to verify key press → action mapping
/keybindings is an interactive command

Expected Usage

// ~/.claude/keybindings.json
{
  "ctrl+e": "submit",
  "ctrl+shift+c": "copy-last-response",
  "ctrl+shift+v": "paste-as-code"
}

Use Cases

Ergonomic preferences - Remap to comfortable key combos
Terminal conflicts - Avoid conflicts with terminal/tmux bindings
Power user workflows - Custom bindings for frequent actions
Accessibility - Remap for physical needs
Consistency - Match keybindings across different tools

Notes

Major usability feature. Keyboard shortcuts were previously hardcoded - this enables personalization.

Status: MANUAL (run /keybindings interactively)

Evidence & receipt

file2.1.7/tests/01-keybindings/TEST-RESULTS.md ↓

◇ ed25519 receipt

idtest_041e8e9976641125145f9d64

alged25519

pubkey9b87705613b1e2fd064d57fa75a6b679d2856ceafad6b1daa8f982493871b6dd

sig

1ae18909529d793caf50c2a9b0f10a19d23a9c059c5f58c483354e93d18d05f35cd4871cfafddeaeae52bc61d02da598678886f660e644dde4007421368e3007

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

verifies Customizable Keyboard Shortcuts Primitive