{"version":"2.1.247","anchor":"cached-prompt-parameters-no-longer-leak-between-sessions","canonical_anchor":"cached-prompt-parameters-no-longer-leak-between-sessions","heading":"Cached prompt parameters no longer leak between sessions","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/cached-prompt-parameters-no-longer-leak-between-sessions","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Cached prompt parameters no longer leak between sessions\n\nCached prompt settings no longer leak from one session into another.\n\n**What**\n\nThe saved last-prompt parameters record now stores the root session id, and the resume path, the reuse path and the freshness check all reject the cache when that id does not match the current session. Previously only the model was compared, so parameters could carry across sessions in the same process.\n\n**Details**\n\n- The record also gained a flag marking parameters prompted for the session model.\n\n**Evidence**\n\n`promptForSessionModel`\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}