{"version":"2.1.224","anchor":"plans-and-session-records-read-through-the-keyed-store","canonical_anchor":"plans-and-session-records-read-through-the-keyed-store","heading":"Plans and session records read through the keyed store","tier":"internal","area":"Internals","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/plans-and-session-records-read-through-the-keyed-store","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Plans and session records read through the keyed store\n\nPlans and session records are now addressable through the keyed storage layer, not just as files.\n\n**What**\n\nPlans and session files are now addressable through Claude Code's keyed storage layer rather than only as raw files on disk.\n\n**Details**\n\n- Two namespaces were registered, `plan` (keyed by name) and `session` (keyed by file), both classified as plain.\n- Priming plan slug collisions lists entries from the store, but only when a store handle is passed and the plans directory is the default one; otherwise it still reads the directory directly, and it also falls back to that on a store error logged as \"primePlanSlugCollisions: v5 list failed: \".\n- The old raw-file reader for plan workshop documents was deleted.\n\n**Evidence**\n\n`primePlanSlugCollisions: v5 list failed: `\n\n- Area: Internals\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}