{"version":"2.1.295","anchor":"tool-memory-cgroup-skipped-when-ks-is-true","canonical_anchor":"tool-memory-cgroup-skipped-when-ks-is-true","heading":"Memory limit for tool commands is skipped in a certain mode","tier":"notice","area":"Sandbox","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/tool-memory-cgroup-skipped-when-ks-is-true","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Memory limit for tool commands is skipped in a certain mode\n\nIn a certain mode, Claude Code now skips setting up the memory limit it can place on commands run by tools\n\n**Unclear.** Which mode makes Claude Code skip the memory limit is not settled.\n\n**What**\n\nOn Linux, Claude Code can put commands run by its tools into a cgroup, a Linux feature that caps how much memory a group of programs can use. `CLAUDE_CODE_TOOL_MEMORY_LIMIT` controls that limit. In a certain mode, Claude Code now skips setting this up altogether, before checking the platform or the limit. Otherwise the setup works as before.\n\n**Why**\n\nIn that mode, commands run by tools are not memory-limited this way, even if you set `CLAUDE_CODE_TOOL_MEMORY_LIMIT`.\n\n- Flag `tengu_tool_memory_cgroup`: Off in both readings (read for one account on one subscription tier against v2.1.295; this account: off, anonymous baseline: off, compiled default: not a boolean we can read) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Sandbox\n- Names: `CLAUDE_CODE_TOOL_MEMORY_LIMIT`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}