windows: add kill-on-close job process primitives#29979
Draft
anp-oai wants to merge 2 commits into
Draft
Conversation
This was referenced Jun 25, 2026
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.
Intent
Windows unified-exec launchers need a compatibility-safe primitive that guarantees a child cannot run user code before it belongs to a configured kill-on-close Job Object. This deliberately avoids the Windows 10-only
PROC_THREAD_ATTRIBUTE_JOB_LISTpath.Implementation
KillOnCloseJob,SuspendedProcess, andJobProcesstypes incodex-utils-pty.Manual validation
codex-utils-ptyWindows test target withcargo +1.95.0 check --target x86_64-pc-windows-msvc -p codex-utils-pty --tests.Stack
1. job primitives → 2. local ConPTY → 3. restricted sessions → 4. elevated runner → 5. command preparation → 6. raw pipe launcher → 7. command parity