{"version":"2.1.246","anchor":"server-can-now-push-a-your-memory-context-was-withheld-notic","canonical_anchor":"server-can-now-push-a-your-memory-context-was-withheld-notic","heading":"Server can now push a \"your memory context was withheld\" notice","tier":"soon","area":"Memory","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/server-can-now-push-a-your-memory-context-was-withheld-notic","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Server can now push a \"your memory context was withheld\" notice\n\nThe server can tell Claude your memory context is being withheld, though memory context itself is off.\n\n**What**\n\nThe cloud connection gained a new live event type that tells Claude Code whether the server is withholding your memory context. The handling is wired end to end: a withheld notice drops the cached context, anything else triggers a re-fetch. The store it feeds is behind the same `tengu_misty_anchor` and entrypoint switch as the rest of memory context, so on a build without that turned on, nothing is fetched even when the event arrives.\n\n**Details**\n\n- The transport gained a field and a `setOnMemoryContextStatus` setter next to its existing heartbeat probe, and the event dispatcher routes the new frame to it carrying whether the payload marked the context withheld.\n- With the gate off, the receiving handler returns early after clearing the cache.\n\n**Evidence**\n\n`memory_context_status`\n\n- Flag `tengu_misty_anchor`: Not enough to say (read for one account on one subscription tier against v2.1.246; this account: no value returned, anonymous baseline: no value returned, compiled default: off)\n- Area: Memory\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 0\/5\n- Present in the build but not switched on"}