Implement native non-PTY processes - #285
Merged
Merged
Conversation
|
Coverage
|
pcarrier
force-pushed
the
pc/native-non-pty-processes
branch
from
August 14, 2026 03:10
db261ad to
dbf69bc
Compare
pcarrier
force-pushed
the
pc/native-non-pty-processes
branch
4 times, most recently
from
August 14, 2026 04:38
1710767 to
7c01339
Compare
pcarrier
force-pushed
the
pc/native-non-pty-processes
branch
from
August 14, 2026 06:00
7c01339 to
cc80a80
Compare
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.
Summary
process_ref; any process-capable client can list live children and TTL-retained detachable final records, attach concurrent watches for future output, and issue lifecycle controls through a watch without a bearer/adoption tokenCLEAR_ENVmodeBLIT_PROCESS=0/--no-processes, startup policy settings, and operator/RFC documentationThere is intentionally no cross-client process confidentiality or control boundary: process-capable clients can discover, watch, and control one another's native children. The low-level packet/accounting API is included; integrated native-client and extension convenience SDKs remain follow-up work.
Validation
cargo test -p blit-server --lib— 484 passedcargo test -p blit-remote --lib— 240 passedcargo test -p blit-cli --bin blit— 93 passed./bin/lint --check— Rust formatting, Prettier, and the full clippy matrix passed