[chris7iu]

Summary

• Propagate mid-stream upstream aborts on Path B (upRes.pipe(clientRes)) in request-worker.js:
  • On non-Codex passthrough responses (e.g. claude-sonnet-4-6, claude-opus-4-7), request-worker.js attaches upRes.once('error', () => routeTelemetry?.finish(upRes.statusCode, 'upstream_error')) before piping upRes.pipe(clientRes). Because upRes already has an 'error' listener, Node's http client does not re-emit mid-body chunked framing/socket errors (HPE_INVALID_CHUNK_SIZE, premature socket close) on upReq, and Readable.prototype.pipe() forwards neither 'error' nor 'aborted' to clientRes. When an upstream aborts mid-stream after flushing HTTP 200 headers, clientRes previously hung open indefinitely instead of propagating UND_ERR_SOCKET to serve-shim / Claude Code's withRetry.
  • Attaches terminateDownstream on upRes 'error', 'aborted', and non-complete 'close' (!upRes.complete) so clientRes is destroyed immediately when headers are already sent (or answered with 502 Bad Gateway if headers were not yet sent).
• Propagate mid-stream upstream aborts in forwardGrok:
  • Attaches terminateGrokDownstream on Grok upRes 'error', 'aborted', and non-complete 'close' so truncated Grok SSE responses after 200 headers also destroy clientRes rather than stalling or finalizing cleanly.
• Pairs with fix(stream): retry pre-output TLS close_notify EOF and abort thinking-only streams on transient drops raine/claude-code-proxy#210 so mid-thinking transient upstream drops cleanly trigger Claude Code's native withRetry across the two-hop serve-shim -> serve-worker -> upstream path.

Test Plan

• node --require ./plugins/model-gateway/test/isolate-home.js --test plugins/model-gateway/test/relay-stream-abort.test.js plugins/model-gateway/test/request-worker.test.js plugins/model-gateway/test/grok-backend.test.js
  • Added tests in relay-stream-abort.test.js covering both serve-worker and two-hop serve-shim propagation when a passthrough Anthropic SSE upstream (claude-sonnet-4-6) or a Grok SSE upstream (grok-4.20) closes mid-chunk after flushing 200 headers.
• node scripts/release/guard.mjs --mode dev --publish-ref origin/main --default-branch main --integration-branch develop ...

[Eigenwise]

Merged, thanks. The fix reads right: with an error listener already on the upstream response, nothing told the client side that the body was cut short, so the stream just hung. Destroying the downstream response on error, abort or an incomplete close covers the passthrough and Grok paths, and the two-hop test proves it through the shim too. It goes out with the next model-gateway release.

The red Windows check on the first run was ours, not yours: a gateway lock test that times out on a slow runner. It's filed and the rerun passed.