You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
MemoryArea: what it touches
ImprovementsKind: in v2.1.248,
ImprovementsSection of the release
What
Restricted sessions no longer write auto-memory. The eligibility check bails out before it even looks at CLAUDE_CODE_DISABLE_AUTO_MEMORY.
Details
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.
Defaults to false, so ordinary sessions are unaffected.
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed sinceAnthropic's documentation has since written up --restricted, on Tools reference.* A permissions [deny rule](/docs/en/permissions#match-all-uses-of-a-tool), the `--disallowedTools` flag, or [`--restricted`](/docs/en/cli-reference#cli-flags) removes `Bash` from the session.tools-referencesee the edit
How sure we are
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up --restricted, on Tools reference.
Anthropic's release notes agreeAdded --restricted (or CLAUDE_CODE_RESTRICTED=1): removes the built-in tools that run commands or code and WebFetch (unless named in…
The name it cites is new in this buildNew in this build: --restricted
