docs(research): record Windows descendant-process containment (#258) - #260
Merged
Merged
Conversation
…indows and what a Job Object contains (#258)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Records the research for Establish how Secant can contain a Harness's descendant processes on Windows in
docs/research/windows-process-containment.md. It covers which Git Bash commands escapetaskkill /T /F, the fact that a kill-on-close Job Object with no breakaway contains them (created throughbun:ffi), the finding that Codex'sturn/interruptleaves a running command alive, and what Claude Code, Codex, OpenCode, and T3 Code do on Windows.Facts only. The choice belongs to Decide how Secant contains a Harness's descendant processes on Windows.
Merge with a merge commit (not squash or rebase) so the pinned links in the resolution comment survive.
🤖 Generated with Claude Code