Source Intelligence

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.228 Home All releases olderv2.1.227 v2.1.229newer
Claude Code v2.1.228

Reaped bridge sessions are unarchived before reattaching

You'll notice
Useful4 Signal3
Sessions

Resuming an older reaped session now unarchives it first instead of failing.

Feature flag
tengu_bridge_unarchive_on_resume Gate removed from the code

This release deleted the gate from the code while it was still reading on for the account this site reads, so the code path no longer asks a flag before running.

This account: on · anonymous baseline: on · compiled default in v2.1.228: not a boolean we can read

These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.

Read once, for one account on one subscription tier, against v2.1.228. It isn't a statement about your account. What a flag value here can and cannot tell you

What

On resume, a bridge session that was reaped is unarchived first and then reattached, so resuming an older session works instead of failing. Controlled by tengu_bridge_unarchive_on_resume, which defaults to on in this build.

Details
  • The unarchive call is retried once through the trusted-device path.
  • A 409 is read as another client having already unarchived the session, and resume continues without undoing anything.
Evidence

tengu_bridge_unarchive_on_resume

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

See this entry in the whole of v2.1.228 →