Follow Discord
Sweep 06 Nov 2026 · 01:32Z Build v2.1.319 537 read Stable v2.1.311 Latest v2.1.318 Next v2.1.319 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.275 ·

Session-fork sanitization clears bridge and artifact-monitor state

Forking or resuming a session now clears bridge and artifact-monitor state

Under the hood Internal Changes
JSON All of v2.1.275
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
SessionsArea: what it touches
Internal ChangesKind: in v2.1.275,
Internal ChangesSection of the release
What

When 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.

Why

This 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.

See this entry in the whole of v2.1.275 →

Feedback