Description
2025-06-05 14:49:20.940 [info] Starting server from LocalProcess extension host
2025-06-05 14:49:20.948 [info] Connection state: Running
2025-06-05 14:49:21.139 [info] 405 status sending message to https://xxx/sse, will attempt to fall back to legacy SSE
2025-06-05 14:49:22.037 [warning] Failed to parse message: "{"jsonrpc":"2.0","id":2,"result":{"tools":...{"additio\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u00
When we use the SSE transport, the client receives a flood of stray NUL (\u0000) bytes that eventually break the stream. Switching to the Streamable-HTTP transport eliminates the problem entirely, indicating the defect is isolated to the SSE path.