test(mcp): add stdout regression test for devkit mcp - #101
Merged
Conversation
Spawns the real binary, sends an initialize JSON-RPC request, and asserts stdout carries only valid JSON-RPC frames. Guards against stray Println / banner output on stdout, which breaks the MCP handshake (the bug Codex hit with "connection closed: initialize response").
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
src/cmd/mcp_test.go— spawns the realdevkitbinary, sends aninitializeJSON-RPC request over stdin, and asserts stdout carries only valid JSON-RPC frames.connection closed: initialize response): any strayPrintlnor banner on stdout breaks the MCP handshake.Test plan
go test ./cmd/ -run TestMCPStdoutIsCleanJSONRPC -vpasses locally