{"version":"2.1.227","anchor":"fleet-view-state-gathered-into-one-host-object","canonical_anchor":"fleet-view-state-gathered-into-one-host-object","heading":"Fleet view state gathered into one host object","tier":"notice","area":"Background Tasks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/fleet-view-state-gathered-into-one-host-object","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Fleet view state gathered into one host object\n\nThe fleet view keeps your selected tab and cached statuses across a remount.\n\n**What**\n\nAll of the fleet view's state now lives in a single host object built by a new factory, which callers can create once and pass back in. That lets the selected tab, cached job statuses, worktrees and the set of already-reported results survive a remount instead of being rebuilt.\n\n**Details**\n\n- The host holds jobs, earlier entries, loop kicks, statuses and their timestamps, PR statuses, the active tab (defaulting to \"local\"), remote jobs, child repos, repo worktrees, templates, skills, routines, and a block tracking which results have already been seen.\n- Both fleet view entry points now use a caller-supplied host if given, otherwise build a fresh one.\n\n**Evidence**\n\n`createFleetViewHost`\n\n- Area: Background Tasks\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}