{"version":"2.1.281","anchor":"process-tree-kill-can-restrict-to-the-same-session","canonical_anchor":"process-tree-kill-can-restrict-to-the-same-session","heading":"Process-tree kill can restrict to the same session","tier":"internal","area":"Elsewhere","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/process-tree-kill-can-restrict-to-the-same-session","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Process-tree kill can restrict to the same session\n\nFinding child processes to stop can now be limited to those in the same operating-system session\n\n**Unclear.** The finding does not say which stop actions pass `sameSession`.\n\n**What**\n\nWhen Claude Code stops a program, it can also find the other programs that program started, known as its descendant processes. That search can now take a `sameSession` option. With it, Claude Code also reads each process's operating-system session id and only follows child processes that share the same session. This is a session in the operating system's sense, a group of related processes, not a Claude Code conversation. On macOS the id is read with `sess=`, and on other systems with `sid=`.\n\nIf session ids cannot be read, or every process has the same one, the search stops and does not follow children at all.\n\n**Why**\n\nThis narrows which processes get stopped along with a program, so processes that belong to a different session are left alone.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}