{"version":"2.1.317","anchor":"sdk-control-channel-prompt-hold-and-next-page-token","canonical_anchor":"sdk-control-channel-prompt-hold-and-next-page-token","heading":"Programs driving Claude Code get a hold on control messages and a page token","tier":"internal","area":"SDK","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/sdk-control-channel-prompt-hold-and-next-page-token","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Programs driving Claude Code get a hold on control messages and a page token\n\nFor programs that drive Claude Code, some control messages can now be held back and later processed, and a list result gains next_page_token\n\n**Unclear.** It is unclear what triggers the hold and which list returns `next_page_token`.\n\n**What**\n\nControl messages are how a program that drives Claude Code, for example through the SDK (software development kit), and Claude Code tell each other what to do. That exchange changed in two ways:\n\n- Hold: some control messages can now be delayed, and replies Claude Code does not recognise can be held and then processed again.\n\n- `next_page_token`: a list result can now include this value, used to fetch the next page of results.\n\n**Why**\n\nIf you build on the SDK, this affects the order in which control messages are handled and how some lists are split into pages.\n\n- Area: SDK\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}