Kieran Klukas's June 17 commit d3af321b is a small maintenance story with a concrete human target: anyone running an agent command inside Crush should not lose the parent TUI because zsh job control or a child signal grabbed the terminal.
The Public Trail
The patch adds internal/shell/exec_unix.go, creates a process-group exec handler, sets SysProcAttr.Setsid, and sends cancellation signals to the negative child PID so a whole child process group is interrupted or killed.
The change also rewires run.go away from the default shell exec handler because the default appends an execution path without the process isolation Crush needed.
Why This Contribution Matters
The tests explain the user pain better than a feature label. One test checks that a child sending SIGINT to its own process group does not reach the parent. Another simulates interactive zsh job control and fails if it hangs or loses the expected output.
Klukas also landed nearby Crush work on scroll filtering and model discovery, but this patch is the clearest maintenance arc: a terminal agent is only useful if its helper process cannot damage the interface that is supervising it.
The Conversation To Open
The fair question for the Crush maintainers is what other shell surfaces still need this kind of isolation contract: sudo prompts, long-running grandchildren, Windows parity, or plugin-spawned commands.