Follow Discord
Sweep 10 Nov 2026 · 02:18Z Build v2.1.322 539 read Stable v2.1.311 Latest v2.1.322 Next v2.1.322 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.281 ·

Headless/SDK startup work held back until the host initializes (startupWorkGate)

Headless and SDK runs now hold some startup work until the host is ready; CLAUDE_CODE_DISABLE_STARTUP_WORK_GATE turns this off

Use it now Notable No documentation found Improvements
JSON All of v2.1.281
Use it nowTier: how much it should matter to you
4Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
SDKArea: what it touches
ImprovementsKind: in v2.1.281,
What probably matters to youSection of the release
What

In headless runs (Claude Code running without its interactive screen, driven by another program), some startup tasks are now held back. One example is sending the tengu_init telemetry event, a usage report. The held tasks are released at the first of these:

  • The host program finishes initializing.
  • The first turn starts.
  • Input closes.
  • A fallback timeout fires.

When they are released at host initialization, the held tasks run one at a time and step aside if a turn starts. Setting the environment variable CLAUDE_CODE_DISABLE_STARTUP_WORK_GATE turns the holding off.

Why

Background startup work no longer competes with the program starting up the session or with its first turn. You can restore the old behavior with the environment variable if you need to.

Read from
How sure we are
One source agreesOne thing we can check says the same as this entry.
The name it cites is new in this buildNew in this build: CLAUDE_CODE_DISABLE_STARTUP_WORK_GATE

See this entry in the whole of v2.1.281 →

Feedback