On Linux you can cap memory for shell commands so a runaway process cannot eat your machine.
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.233: on
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.
Read once, for one account on one subscription tier, against v2.1.233. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
On Linux and WSL, shells spawned by the Bash and PowerShell tools can now be placed in a claude-code-bash memory cgroup so a runaway command hits a cap instead of your machine. Set CLAUDE_CODE_TOOL_MEMORY_LIMIT to a size such as 2g to pick the cap, or to none to switch it off. With no explicit size it only engages when the remote flag tengu_tool_memory_cgroup is on, which is off by default in this build.
- Writes
memory.maxon cgroup v2 andmemory.limit_in_byteson v1. - With no override the limit is derived from total system RAM.
- Other platforms return early and spawn normally.
- Reports the outcome as
tengu_tool_cgroupwith status enabled or disabled, and logs atool cgroup: disabled (line with the reason.
CLAUDE_CODE_TOOL_MEMORY_LIMIT=2g claudetengu_tool_cgroup, tool cgroup: disabled (
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Every session now gets the
cdpermission warning in the Bash toolBoth mention tool bash
-
v2.1.234
Command lessons are recorded with the command that produced them
Both mention tool bash
-
v2.1.238
Directory tracking for backgrounded commands no longer breaks early
Both mention tool bash