{"version":"2.1.238","anchor":"turns-in-cloud-sessions-now-wait-for-a-pre-turn-check-which-","canonical_anchor":"turns-in-cloud-sessions-now-wait-for-a-pre-turn-check-which-","heading":"Turns in cloud sessions now wait for a pre-turn check, which cannot yet refuse","tier":"soon","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/turns-in-cloud-sessions-now-wait-for-a-pre-turn-check-which-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### Turns in cloud sessions now wait for a pre-turn check, which cannot yet refuse\n\nHeadless and SDK turns now wait on a pre-turn check that currently always says go ahead.\n\n**What**\n\nHeadless 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.\n\n**Details**\n\n- 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.\n- 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.\n\n**Evidence**\n\n`This session cannot continue: a required step before the turn did not complete.`\n\n- Area: Cloud Sessions\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}