Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.246 Home All releases ←olderv2.1.245 v2.1.247newer→
Claude Code v2.1.246

The SDK transport can ask the main loop whether it is still working

Under the hood
Useful3 Signal3
SDK

The SDK transport can now ask the main loop whether it's truly idle before saying so.

What

The transport used by the SDK and bridge gained a way to register a liveness probe, so when the last pending permission or dialog request resolves it announces idle rather than running if the main loop reports it has nothing to do.

Details
  • Print/headless mode registers the probe from its idle gate.
  • If the probe throws, the failure is recorded under the existing per_task_stop_sparing event with reason liveness_probe_throw and the session is reported as not idle.
  • Present on this build wherever the SDK or bridge transport is used, with no flag.
Evidence

setMainLoopLiveness

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

See this entry in the whole of v2.1.246 →