{"version":"2.1.246","anchor":"tool-memory-cgroups-reworked-still-off-unless-turned-on","canonical_anchor":"tool-memory-cgroups-reworked-still-off-unless-turned-on","heading":"Tool memory cgroups reworked, still off unless turned on","tier":"soon","area":"Sandbox","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/tool-memory-cgroups-reworked-still-off-unless-turned-on","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Tool memory cgroups reworked, still off unless turned on\n\nMemory caps on processes Claude starts were rebuilt but stay off unless you set the limit variable.\n\n**What**\n\nThe 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.\n\n**Details**\n\n- If the enclosing cgroup already caps the process it is reused rather than nested, reported as `nested`.\n- 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)`.\n- A cgroup directory that disappears is re-created (`recreated`) or the feature is switched off (`vanished`).\n- Every outcome reports to `tengu_tool_cgroup`.\n\n**Evidence**\n\n`if (o === void 0 && C.read(\"tengu_tool_memory_cgroup\", !1) !== !0) return;`\n\n- Flag `tengu_tool_memory_cgroup`: Off in both readings (read for one account on one subscription tier against v2.1.246; this account: off, anonymous baseline: off, compiled default: not a boolean we can read)\n- Area: Sandbox\n- Names: `CLAUDE_CODE_TOOL_MEMORY_LIMIT`\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}