{"version":"2.1.248","anchor":"failed-session-startup-no-longer-leaves-parts-of-the-session","canonical_anchor":"failed-session-startup-no-longer-leaves-parts-of-the-session","heading":"Failed session startup no longer leaves parts of the session running","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/failed-session-startup-no-longer-leaves-parts-of-the-session","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Failed session startup no longer leaves parts of the session running\n\nA failed startup now shuts down everything it already started instead of leaving parts running.\n\n**What**\n\nSession startup was split into separate steps that each register a teardown, so if any step throws, everything already started is shut down before the error propagates. Previously a failure partway through could leave data feeds running.\n\n**Details**\n\n- New during startup: a watch that mirrors the standalone agent name into app state, a wake dispatch for task notifications, a watch that discloses activity when unattended mode turns on, and spinner subscriptions.\n- SessionStart hook output is now awaited and prepended to the transcript once it resolves.\n- If the sandbox declines to start, the remaining startup steps are skipped.\n\n**Evidence**\n\n`SessionController.start: rearmArtifactLiveOnMount threw`\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}