{"version":"2.1.248","anchor":"auto-memory-is-off-in-restricted-sessions","canonical_anchor":"auto-memory-is-off-in-restricted-sessions","heading":"Auto-memory is off in restricted sessions","tier":"notice","area":"Memory","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/auto-memory-is-off-in-restricted-sessions","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Auto-memory is off in restricted sessions\n\nRestricted sessions never write auto-memory, regardless of your settings.\n\n**What**\n\nRestricted sessions no longer write auto-memory. The eligibility check bails out before it even looks at `CLAUDE_CODE_DISABLE_AUTO_MEMORY`.\n\n**Details**\n\n- Triggered by the same option behind the `--restricted` argument that Claude Code passes to its own child sessions, along with the `CLAUDE_CODE_RESTRICTED: \"1\"` environment variable it forwards.\n- Defaults to false, so ordinary sessions are unaffected.\n\n**Evidence**\n\n`CLAUDE_CODE_DISABLE_AUTO_MEMORY`\n\n- Area: Memory\n- Names: `CLAUDE_CODE_DISABLE_AUTO_MEMORY`, `--restricted`, `CLAUDE_CODE_RESTRICTED`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}