{"version":"2.1.281","anchor":"laptop-memory-context-reports-a-new-local-memory-off-state","canonical_anchor":"laptop-memory-context-reports-a-new-local-memory-off-state","heading":"Laptop memory context reports a new \"local_memory_off\" state","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/laptop-memory-context-reports-a-new-local-memory-off-state","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Laptop memory context reports a new \"local_memory_off\" state\n\nLaptop memory status events now report a `local_memory_off` state for any gate state besides open, closed, pending and denied\n\n**Unclear.** The finding does not say whether this event is shown to the user or only recorded internally.\n\n**What**\n\nClaude Code sends a `laptop_memory_context` event describing whether memory on your computer is available. Before, it was only sent for the pending and denied states. Now:\n\n- It clears when the state is open or closed.\n\n- It reports every other state.\n\n- Pending and denied are still reported as themselves; all other states are reported as `local_memory_off`.\n\n**Why**\n\nCases where local memory is unavailable for other reasons are now reported instead of being skipped."}