{"version":"2.1.275","anchor":"session-fork-sanitization-clears-bridge-and-artifact-monitor","canonical_anchor":"session-fork-sanitization-clears-bridge-and-artifact-monitor","heading":"Session-fork sanitization clears bridge and artifact-monitor state","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/session-fork-sanitization-clears-bridge-and-artifact-monitor","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### Session-fork sanitization clears bridge and artifact-monitor state\n\nForking or resuming a session now clears bridge and artifact-monitor state\n\n**What**\n\nWhen session state is carried forward into a fork or resume, a new helper now strips it of certain state so it doesn't leak into the new session. It clears artifactCommentMonitor and artifactAutoReactLedger unconditionally, along with a full set of bridge-related fields: bridgeSessionId, bridgeLastSeq, bridgeDialogKinds, bridgeSessionGroupingId, bridgeNoHistoryBackfill, bridgeOwnerAccountUuid, and bridgeOwnerOrganizationUuid. It can also optionally strip worktreeSession and relocatedCwd.\n\n**Why**\n\nThis prevents a forked or resumed session from inheriting artifact-monitoring or bridge-connection identifiers that belonged to the original session, avoiding cross-session state confusion.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 1\/5"}