{"version":"2.1.293","anchor":"keybinding-parser-rejects-spaces-next-to","canonical_anchor":"keybinding-parser-rejects-spaces-next-to","heading":"Keybindings written with spaces around '+' now get a clear error","tier":"notice","area":"Terminal UI","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/keybinding-parser-rejects-spaces-next-to","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Keybindings written with spaces around '+' now get a clear error\n\nA keybinding such as 'ctrl + x' now produces an error telling you to remove the spaces next to '+', instead of being misread\n\n**What**\n\nWhen Claude Code reads your custom keybindings (the key combinations you assign to actions), it now splits each binding on spaces first. A binding written as `ctrl + x`, with spaces around the plus sign, now gives its own error message. The message explains that the spaces turn the binding into separate key presses, one of which has no key, and tells you to remove the spaces next to `+`.\n\nBefore, the only error of this kind was raised for an empty part between two plus signs, so a spaced binding could be read wrongly instead of being flagged.\n\n**Why**\n\nIf a keybinding of yours did not work and you had written it with spaces, you now get a message saying exactly what to fix. Write it as `ctrl+x`.\n\n- Area: Terminal UI\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}