Tool memory cgroups are reworked and gated on CLAUDE_CODE_TOOL_MEMORY_LIMIT or a remote flag that falls back to false.
The Linux and WSL feature that caps the memory of processes Claude Code spawns was rebuilt. It stays off unless CLAUDE_CODE_TOOL_MEMORY_LIMIT names a limit or the remote flag tengu_tool_memory_cgroup reads true; the in-source fallback is false, so with no server value nothing is capped. Setting the env var to none disables it outright.
- If the enclosing cgroup already caps the process it is reused rather than nested, reported as
nested. - If the machine is too small for the default cap the feature disables itself, logging
tool cgroup: disabled (host too small for the default cap). - A cgroup directory that disappears is re-created (
recreated) or the feature is switched off (vanished). - Every outcome reports to
tengu_tool_cgroup.
if (o === void 0 && C.read("tengu_tool_memory_cgroup", !1) !== !0) return;
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
tengu_tool_memory_cgroup Off in both readingsThe flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.
This account: off · anonymous baseline: off · compiled default in v2.1.246: not a boolean we can read
Read once, for one account on one subscription tier, against v2.1.246. It isn't a statement about your account. What a flag value here can and cannot tell you
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.