Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.242 Home All releases ←olderv2.1.241 v2.1.243newer→
Claude Code v2.1.242

Bridge sessions snapshot the state of the git working tree

Under the hood
Useful2 Signal3
Cloud Sessions

Sessions bridged from another environment record the git working tree state when they start.

What

Sessions bridged from another environment now record a picture of the repository at startup, which explains how those sessions decide what state they resumed into.

Details
  • Records branch, head commit, count of commits not pushed to refs/remotes/origin/<branch>, whether the tree is dirty, whether an upstream exists, whether a rebase, merge, cherry-pick, revert or bisect is in progress, whether submodules exist, and whether Git LFS is in use.
  • LFS is detected by scanning the first 64 KiB of .gitattributes for filter=lfs.
  • The whole probe runs under a timeout; timing out reports "worktree probe timed out" and counts as a collection failure.
Evidence

bridge_worktree_state

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.242 →