{"version":"2.1.283","anchor":"keystrokes-in-one-input-chunk-are-now-committed-one-by-one","canonical_anchor":"keystrokes-in-one-input-chunk-are-now-committed-one-by-one","heading":"Keys that arrive together can now be handled one at a time by default","tier":"use","area":"Terminal Input","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/keystrokes-in-one-input-chunk-are-now-committed-one-by-one","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Keys that arrive together can now be handled one at a time by default\n\nSeveral keypresses arriving at once can now be drawn one by one without setting `CLAUDE_CODE_COMMIT_BETWEEN_KEYS`\n\n**What**\n\nWhen several keypresses reach Claude Code in a single read from the terminal, it can finish and draw the effect of each key before handling the next. Before, this only happened if you set the `CLAUDE_CODE_COMMIT_BETWEEN_KEYS` environment variable. Now, with that variable unset, a remotely controlled setting decides, and it falls back to on when the server sends nothing. Setting the variable still overrides that setting either way.\n\n**Why**\n\nFast typing, held-down keys and bursts of pasted keys should update the prompt one key at a time instead of being dropped or merged.\n\n- Flag `tengu_pewter_lintel`: Not enough to say (read for one account on one subscription tier against v2.1.283; this account: no value returned, anonymous baseline: no value returned, compiled default: on) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Terminal Input\n- Names: `CLAUDE_CODE_COMMIT_BETWEEN_KEYS`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5"}