Session resume falls back to scanning transcripts by id

Resuming a session by its id now works even when the usual lookup misses it.

You'll noticeTier: how much it should matter to you

3Useful: my rating, 1 to 5

0Signal: worth watching, 1 to 5

SessionsArea: what it touches

Bug FixesKind: in v2.1.223, 05 Aug 26

Bug FixesSection of the release

What

Resuming a session by string id no longer fails when the usual lookup misses it.

Details

An additional lookup path scans transcripts for the id.
When the scan is what found the session, tengu_transcript_id_scan_fallback is recorded.

Evidence

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

The build it came inv2.1.223

5 Aug 2026 · 201 entries, this one is #126.

Either side of it

Open the release →

Names in this entry

flagtengu_transcript_id_scan_fallback
Resuming a session by its id now works even when the usual lookup misses it.

Is this right?

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