From 360bcb4c6cffc2e4d7f855b200927f508df17163 Mon Sep 17 00:00:00 2001 From: CyberSprout Date: Sun, 22 Nov 2026 04:01:14 +0800 Subject: [PATCH] docs(process): record the capture PTY hangup of same-group children (#10282) When the target exits, the terminal sends SIGHUP to its foreground process group. The capture guide now says that, and that this signal is not REA cleanup. Co-authored-by: Cursor --- docs/guides/runtime/process-capture.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/guides/runtime/process-capture.md b/docs/guides/runtime/process-capture.md index 2eae6781ad..56e57d4e69 100644 --- a/docs/guides/runtime/process-capture.md +++ b/docs/guides/runtime/process-capture.md @@ -456,6 +456,8 @@ run the same owned-process cleanup path. Settlement reports whether the sampled process group quiesced or whether cleanup was needed or unverifiable; sampling cannot prove that every short-lived or detached descendant was seen. +The target is the session leader of the capture PTY. When that leader exits, the terminal delivers SIGHUP to processes that are still in its foreground process group, as `script -c` and `ssh -t` do. A child that should outlive the target has to leave the group, for example with `setsid`, or ignore SIGHUP. This hangup comes from the terminal, not from REA's owned-process cleanup, and the capture result does not record it. + ### Finalization interval By default a deadline sends `SIGKILL` at once. Set `finalization_ms` to give the