{"version":"2.1.301","anchor":"keyboard-dispatch-flushes-and-marks-on-handled-keypress","canonical_anchor":"keyboard-dispatch-flushes-and-marks-on-handled-keypress","heading":"Handled keypresses are now processed right away","tier":"internal","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/keyboard-dispatch-flushes-and-marks-on-handled-keypress","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### Handled keypresses are now processed right away\n\nWhen a keypress is handled, Claude Code now processes pending work at once and runs a follow-up step with that key, instead of ignoring the result\n\n**Unclear.** It is not stated what the follow-up step does, so any visible effect is unclear.\n\n**What**\n\nWhen you press a key, Claude Code passes it to a handler that decides whether anything should respond to it. Before this release, Claude Code did nothing with the handler's answer. Now, when the handler reports that it dealt with the keypress, Claude Code processes any pending work immediately and then runs a follow-up step with the key that was pressed.\n\n**Why**\n\nThis may make the interface respond more promptly to keypresses that trigger an action. Nothing else about how keys are typed or read is described as changing.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}