[codex] Preserve MCP proxy trace on writer failure#98
Merged
Conversation
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
1 participant
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
--trace-outwrites verifiable evidence after a mediated event even when the client output pipe breaks.Why
The local subprocess stdio proxy is the v0.1 operator path. Its trace output should behave like a flight recorder: if the operator/client stream fails after AgentK has mediated a boundary crossing, the evidence should still be available for review.
Verification
cargo fmt --checkcargo test mcp_proxy_stdio_trace_out_survives_writer_failure_after_event -- --nocapturecargo testcargo clippy --all-targets --all-features -- -D warningscargo run --locked -- release-audit