{"version":"2.1.246","anchor":"a-second-linux-process-group-is-created-for-bash-tools-but-n","canonical_anchor":"a-second-linux-process-group-is-created-for-bash-tools-but-n","heading":"A second Linux process group is created for Bash tools but never used","tier":"internal","area":"Sandbox","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/a-second-linux-process-group-is-created-for-bash-tools-but-n","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### A second Linux process group is created for Bash tools but never used\n\nA second Linux process group for Bash tools exists with helpers that nothing calls.\n\n**What**\n\nOn Linux and WSL, alongside the existing `claude-code-bash` process group used to contain tool processes, there is now a sibling `claude-code-keeper` group with helpers to create it, move a process into it and offer it when spawning. Nothing outside the process-group code itself calls any of them.\n\n**Details**\n\n- Moving a process logs a line of the form `tool cgroup: keeper pid <pid> moved to <path>`.\n- There is no flag or setting involved; the functions are simply uncalled, and the name appears nowhere else in the build.\n\n**Evidence**\n\n`claude-code-keeper`\n\n- Area: Sandbox\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5\n- Present in the build but not switched on"}