You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
SessionsArea: what it touches
Bug FixesKind: in v2.1.228,
Bug FixesSection of the release
What
If you resume a different conversation while a transcript backfill is still running, the upload now aborts and logs instead of pinning content from the old session onto the live one. The check runs both before the main upload and before the subagent pass.
Evidence
[persistence-sync] Refusing backfill: session id changed since the scan anchor was pinned
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agreeFixed Remote Control /resume while connected leaking the resumed conversation's title or history into the connected session
