{"version":"2.1.229","anchor":"storage-and-session-handles-passed-explicitly-instead-of-rea","canonical_anchor":"storage-and-session-handles-passed-explicitly-instead-of-rea","heading":"Storage and session handles passed explicitly instead of read from globals","tier":"internal","area":"Session State","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229\/e\/storage-and-session-handles-passed-explicitly-instead-of-rea","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229","markdown":"### Storage and session handles passed explicitly instead of read from globals\n\nStorage and session handles are now passed around explicitly instead of read from process-wide state.\n\n**What**\n\nConfig writes, transcript appends (custom title, agent name, PR link, last prompt), session-start and setup hook dispatch, background housekeeping, plugin marketplace operations and many dialogs now receive the storage handle and session object as arguments rather than reaching for process-wide state. Hook dispatch in particular changed shape to take the session plus a storage field.\n\n**Evidence**\n\n`storageV5: t.storageV5`\n\n- Area: Session State\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}