{"version":"2.1.284","anchor":"tengu-pewter-lintel-kill-switch-and-claude-code-commit-betwe","canonical_anchor":"tengu-pewter-lintel-kill-switch-and-claude-code-commit-betwe","heading":"Keys that arrive together are always handled one at a time, with no way to turn it off","tier":"notice","area":"Terminal UI","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/tengu-pewter-lintel-kill-switch-and-claude-code-commit-betwe","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### Keys that arrive together are always handled one at a time, with no way to turn it off\n\n`CLAUDE_CODE_COMMIT_BETWEEN_KEYS` no longer does anything; handling a burst of keys one by one is always on\n\n**What**\n\nWhen several keypresses reach Claude Code in a single read from the terminal, it draws the effect of each key before handling the next. This used to be controlled by the `CLAUDE_CODE_COMMIT_BETWEEN_KEYS` environment variable and, when that was unset, by a remotely controlled setting. Both are gone: the behaviour now applies whenever a batch holds more than one key.\n\nThe default is unchanged, since the remote setting fell back to on.\n\n**Why**\n\nIf you set `CLAUDE_CODE_COMMIT_BETWEEN_KEYS` to turn this off, that no longer works and you can remove it.\n\n- Flag `tengu_pewter_lintel`: Not enough to say (read for one account on one subscription tier against v2.1.284; this account: no value returned, anonymous baseline: no value returned, compiled default: not a boolean we can read) 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 UI\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}