Skip to content

docs: clarify default stderr capture behavior - #1200

Merged
zackees merged 1 commit into
zackees:mainfrom
Etherist:docs/clarify-stderr-capture-default
Sep 29, 2026
Merged

zackees merged 1 commit into
zackees:mainfrom
Etherist:docs/clarify-stderr-capture-default

Conversation

@Etherist

@Etherist Etherist commented Sep 9, 2026 •

Copy link
Copy Markdown

Summary

Updates the README to match the current stderr capture behaviour.

RunningProcess(...) merges stderr into stdout by default, while passing stderr=PIPE enables separate stdout/stderr capture.

The pipe-backed example now demonstrates the split-capture form explicitly, and the Notes section has been corrected accordingly.

Background

The README currently states that stdout and stderr are no longer merged by default, but the implementation and regression tests use merged capture as the default.

The documented behaviour had drifted from the runtime contract, so this PR updates the documentation rather than changing runtime behaviour.

Scope

Documentation only. No runtime or API behaviour is changed.

This PR documents the current default stderr capture behaviour described in #1195.

Resolves #1195

Update the pipe-backed example and notes to document the current stderr capture contract: stderr is merged into stdout by default, while stderr=PIPE enables separate capture.
@zackees
zackees merged commit 8d188a7 into zackees:main Sep 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Review default output stream handling in RunningProcess(...)

2 participants