{"version":"2.1.228","anchor":"forking-a-conversation-seeds-the-message-cache","canonical_anchor":"forking-a-conversation-seeds-the-message-cache","heading":"Forking a conversation seeds the message cache","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/forking-a-conversation-seeds-the-message-cache","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### Forking a conversation seeds the message cache\n\nForking a conversation preloads its message index, so the first lookups skip re-reading the file.\n\n**What**\n\nAfter 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.\n\n**Evidence**\n\n`primeSessionMessagesCache`\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}