Follow Discord
Sweep 25 Sep 2026 · 19:33Z Build v2.1.283 504 read Stable v2.1.274 Latest v2.1.283 Next v2.1.283 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.281 ·

Headless/SDK message loop: separate queue for the client's own first-turn message

When Claude Code is driven by a program, the client's own first-turn message now waits in its own queue

Under the hood Internal Changes
JSON All of v2.1.281
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
SDKArea: what it touches
Internal ChangesKind: in v2.1.281,
Internal ChangesSection of the release
What

In headless mode (Claude Code driven by another program, for example through the SDK, instead of by a person at a terminal), incoming user messages can be held back until Claude Code is ready. A message flagged as the client's own first-turn message now waits in a separate queue. Other messages now also wait on a new first-turn gate, and closing input waits for both. The cli_user_frame_parked telemetry gains own_first_turn_message and first_turn_gate.

Why

The program's own first message is kept apart from other incoming messages, so the first turn is handled before anything that arrives alongside it.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtThe finding does not say what ordering problem, if any, this change fixes for SDK users.

See this entry in the whole of v2.1.281 →

Feedback