{"version":"2.1.271","anchor":"session-engine-store-gains-a-dedicated-enginestore-slot","canonical_anchor":"session-engine-store-gains-a-dedicated-enginestore-slot","heading":"Session engine store gains a dedicated 'engineStore' slot","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/session-engine-store-gains-a-dedicated-enginestore-slot","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Session engine store gains a dedicated 'engineStore' slot\n\nEach session now has its own dedicated 'engineStore' slot alongside existing per-session data stores\n\n**Unclear.** What data or feature `engineStore` actually holds is not stated.\n\n**What**\n\nClaude Code's per-session state container now allocates a new `engineStore`, sitting alongside existing per-conversation stores like the cost ledger, hook registry, and model selection. When a session is forked, the new store is inherited from the root session.\n\n**Why**\n\nThis is internal session-state plumbing; the finding doesn't say what the new store is used for.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}