{"version":"2.1.281","anchor":"system-status-frame-attach-serve-helpers-emit-from-the-st","canonical_anchor":"system-status-frame-attach-serve-helpers-emit-from-the-st","heading":"system status frame: --attach-serve helpers emit from the start","tier":"internal","area":"SDK","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/system-status-frame-attach-serve-helpers-emit-from-the-st","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### system status frame: --attach-serve helpers emit from the start\n\nInternal docs for the stream-json status frame now say --attach-serve helpers have no init and list every key in their first frame\n\n**Unclear.** The description is marked internal, and the finding does not say how `--attach-serve` is used or reached.\n\n**What**\n\nStream-json is a machine-readable output format that sends a series of messages, called frames. The internal description of the frame that reports status changes now covers helpers started with `--attach-serve`. These helpers do not send an init message, so their first frame (sequence number 1) lists every key and acts as the first full snapshot.\n\n**Why**\n\nA program reading this output from such a helper should treat the first status frame as the complete starting state, because no init message comes before it.\n\n- Area: SDK\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}