{"version":"2.1.234","anchor":"schema-now-describes-cloud-sessions-and-cross-session-notice","canonical_anchor":"schema-now-describes-cloud-sessions-and-cross-session-notice","heading":"Schema now describes cloud sessions and cross-session notices","tier":"internal","area":"JSON Output","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/schema-now-describes-cloud-sessions-and-cross-session-notice","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Schema now describes cloud sessions and cross-session notices\n\nThe JSON output description now covers what a cloud-hosted session reports at startup and server-composed notices from other sessions.\n\n**What**\n\nThe machine-readable description of Claude Code's JSON output gained two blocks. One describes what a cloud-hosted session reports when it starts up; the other describes a notice composed by the server on behalf of another session.\n\n**Details**\n\n- The cloud session block is optional and only appears on start-up frames from the cloud client. It carries the cloud session id, a URL to view it, whether a device is bound and why not with a one-line message, and a directory sync state of off, seeding, armed or stopped with a file mode of container_sync, device_tools or unspecified.\n- It also carries a client version, with instructions that a consumer seeing a higher one should warn and carry on rather than refuse.\n- The notice block describes delivery over the polling event channel with server-asserted origin stamps that are stripped on the way in and re-applied by whatever composes the notice, the same discipline used for synthetic messages.\n\n**Evidence**\n\n`Server-asserted ingest-path marker, same strip-and-restamp discipline as isSynthetic.`\n\n- Area: JSON Output\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 4\/5"}