process-guard

To prevent terminal commands from blocking your coding agent, you can use a process management skill that classifies commands and wraps finite executions with timeouts. This ensures commands automatically terminate if they exceed a specified duration.

Managing long-running background processes without leaving orphans involves starting them as managed background tasks with graceful shutdowns. The process monitor recursively stops managed processes and cleans up state files upon completion.

Verifying the readiness of a background process is done by checking health URLs, ports, custom probes, or log patterns. The process monitor uses these methods to confirm the process is fully operational before proceeding.

Yes, you need system access to terminate terminal processes and write state to a run directory. This level of access is required to enforce timeout wrappers and execute recursive cleanup of managed background tasks.

The best way to run a long-running command like npm test with a timeout is to execute it via a managed process script. You pass the command, port, and timeout duration as arguments to ensure it runs in the background with enforced limits.