Peter Shiller

Every command ends on time, and nothing it started is left behind. Artificial intelligence (AI) coding agents, scripts and Continuous Integration (CI) jobs start processes all day. Some of those processes never end. A test run waits on a socket. A dev server stays in the background. A build tool leaves a compiler worker behind. A plain timeout kills the process it started, and the children of that process keep running. The result is a hung agent session, a stuck CI runner, a locked file or a port that stays busy. process-tree-guard closes that gap. The command is born inside a Windows job object. Every process the command starts is born inside the same job. At the deadline, the guard closes the job and Windows ends every process in it.