Follow Discord
Sweep 28 Sep 2026 · 18:16Z Build v2.1.284 505 read Stable v2.1.277 Latest v2.1.284 Next v2.1.284 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.284 ·

Keys that arrive together are always handled one at a time, with no way to turn it off

CLAUDE_CODE_COMMIT_BETWEEN_KEYS no longer does anything; handling a burst of keys one by one is always on

You'll notice Removed
JSON All of v2.1.284
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
Terminal UIArea: what it touches
RemovedKind: in v2.1.284,
RemovedSection of the release
What

When 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.

The default is unchanged, since the remote setting fell back to on.

Why

If you set CLAUDE_CODE_COMMIT_BETWEEN_KEYS to turn this off, that no longer works and you can remove it.

Read from
Feature flag
tengu_pewter_lintel Not enough to say

Nothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.

This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.284: 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.

Read once, for one account on one subscription tier, against v2.1.284. It isn't a statement about your account. What a flag value here can and cannot tell you

See this entry in the whole of v2.1.284 →

Feedback