{"version":"2.1.290","anchor":"cloud-session-init-docs-worker-result-may-precede-init","canonical_anchor":"cloud-session-init-docs-worker-result-may-precede-init","heading":"A worker's result can now arrive before a cloud session's first start message","tier":"notice","area":"SDK","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/cloud-session-init-docs-worker-result-may-precede-init","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### A worker's result can now arrive before a cloud session's first start message\n\nPrograms driving Claude Code may now receive a worker's result before the first start message of a cloud session\n\n**What**\n\nPrograms that drive Claude Code through its SDK (its programming interface) receive a stream of messages, which usually begins with a start message called init. The documentation for cloud sessions now says a worker's result may arrive with no init before it. Claude Code holds such early results and lets them through once the session is created and the result comes from a worker. Before, only informational system messages could come before the first init.\n\n**Why**\n\nIf you write a program around the SDK, it should not assume that init always comes first.\n\n- Area: SDK\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}