Source Intelligence

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.238 Home All releases olderv2.1.237 v2.1.239newer
Claude Code v2.1.238

Turns in cloud sessions now wait for a pre-turn check, which cannot yet refuse

Not switched on
Useful2 Signal4
Cloud Sessions

Headless and SDK turns now wait on a pre-turn check that currently always says go ahead.

A veto point before every turn exists with only one participant registered, the directory-sync pull, which always answers ready, so nothing can refuse a turn.

What

Headless and SDK sessions gained a check that runs before every turn: registered participants are asked whether the turn may start, and a refusal ends the session with "This session cannot continue: a required step before the turn did not complete." Only one participant is ever registered, the directory-sync pull, and it always answers ready, so no code in this build can actually refuse a turn.

Details
  • The participant is registered only when the directory-sync worker starts, which needs an SDK URL and CLAUDE_CODE_REMOTE_SESSION_ID, with neither CLAUDE_CODE_DISABLE_DIR_SYNC nor CLAUDE_CODE_DISABLE_WORKING_SYNC set. In that case turns genuinely wait for the sync pull to finish before starting.
  • The refusal machinery is complete but unreachable: nothing in the bundle returns a failure answer, so the failure-collection branch, the after-abort logging and the fallback wording for a refusal with no reason all sit unused.
Evidence

This session cannot continue: a required step before the turn did not complete.

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.238 →