You'll noticeTier: 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.228,
Internal ChangesSection of the release
What
After a fork writes the new transcript, the set of message ids for the new session is inserted straight into the transcript store's in-memory cache, so later lookups do not re-read the file just written. Insert is skipped if an entry is already there.
Evidence
primeSessionMessagesCache
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
