{"version":"2.1.236","anchor":"repl-and-fleet-view-read-from-a-shared-snapshot-instead-of-s","canonical_anchor":"repl-and-fleet-view-read-from-a-shared-snapshot-instead-of-s","heading":"REPL and fleet view read from a shared snapshot instead of scattered state","tier":"internal","area":"REPL","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236\/e\/repl-and-fleet-view-read-from-a-shared-snapshot-instead-of-s","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236","markdown":"### REPL and fleet view read from a shared snapshot instead of scattered state\n\nStreaming state and the fleet view now read one shared snapshot instead of scattered props.\n\n**What**\n\nStreaming state, including the user's input while a turn is processing, the streaming text peek, the interruptible-tool flag, a pending preserved insert and the API metrics reset, moves onto one stream object. The message queue is now passed explicitly to spawn and notification paths rather than reached through a module-level function, and the fleet view drops eight initial-state props in favour of snapshot reads for focused index, rename state, follow origin and mode. No behaviour change is claimed, though most REPL callback signatures changed.\n\n**Evidence**\n\n`hasInterruptibleToolInProgress`\n\n- Area: REPL\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}