{"version":"2.1.274","anchor":"new-x-memory-context-stop-response-header-controls-memory","canonical_anchor":"new-x-memory-context-stop-response-header-controls-memory","heading":"New 'x-memory-context-stop' response header controls memory-context shutdown","tier":"internal","area":"Team Memory","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/new-x-memory-context-stop-response-header-controls-memory","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### New 'x-memory-context-stop' response header controls memory-context shutdown\n\nServer can now tell Claude Code to stop using shared memory context via a new response header\n\n**What**\n\nClaude Code now reads a new `x-memory-context-stop` response header, which can carry the value \"org\" or \"credential\". When the server sends this header on certain responses, Claude Code treats it as an instruction to stop using team or shared memory context for the current session, surfaced internally as a `stopped_org` or `stopped_credential` state.\n\n**Why**\n\nThis lets the server centrally shut off shared memory context for an organization or a specific credential, for example if access should no longer be granted, without requiring a client update.\n\n- Area: Team Memory\n- Names: `x-memory-context-stop`\n- Tier: Under the hood\n- Useful: 3\/5\n- Signal: 3\/5"}