{"version":"2.1.307","anchor":"sdk-supporteddialogkinds-check-moved-into-a-helper-new-ses","canonical_anchor":"sdk-supporteddialogkinds-check-moved-into-a-helper-new-ses","heading":"SDK gains new control requests and session flags","tier":"use","area":"Agents","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/sdk-supporteddialogkinds-check-moved-into-a-helper-new-ses","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### SDK gains new control requests and session flags\n\nThe SDK protocol gains three control request types, three new session flags and a new `unsupported_runtime` reason\n\n**Unclear.** What the new control requests and flags do is not stated.\n\n**What**\n\nThe SDK is the kit for running Claude Code from another program. Its protocol, the set of messages passed between that program and Claude Code, gains:\n\n- Three more kinds of control request.\n\n- New flags named `lifecycle_wakeup_source_v1`, `interrupt_requeue_taken_v1` and `read_file_as_written_v1`.\n\n- A new reason, `unsupported_runtime`.\n\nThe existing check that rejects `supportedDialogKinds` when no `onUserDialog` handler is given still applies; it has only been reorganised.\n\n**Why**\n\nPrograms built on the SDK may start seeing these new messages and values.\n\n- Area: Agents\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}