Applied AI
A hidden Location header can make an agent stream look finished
Test LangGraph JS run-stream reconnection through proxies and CORS before trusting a clean close.
November 11, 2026
An agent answer may stop midway and appear complete when a proxy cuts its stream. A LangGraph JS fix merged on November 10 describes run streams that could not reconnect when the server omitted Location or browser CORS rules hid it. If Content-Location was hidden too, the client could miss the run ID needed to cancel or rejoin it.
Reproduce the real network path
Test through the same proxy, browser and CORS configuration customers use. Start a resumable run, record its ID, interrupt the stream transport, and observe whether the UI reconnects or declares completion. Repeat when Location is readable, missing and not exposed to browser JavaScript. These are different conditions; a successful local test can hide a production proxy problem.
The merged fix reconstructs a join path from Content-Location or metadata when possible. It also notes that a non-resumable run still cannot recover events after a drop. Verify the installed package contains the fix before relying on it. LangGraph’s JavaScript architecture guidance treats streaming as a progress surface over durable execution, not as the only record of the result.
Define completion independently
Only mark the interaction complete when the authoritative run reaches a terminal state. On transport failure, show a reconnecting state and preserve the run ID; do not silently create a second run. Test cancel while waiting to reconnect, because the same PR addresses an abort delay in that window.
Adovo’s view
The wire can close while the work is still alive. A trustworthy agent experience keeps run identity across that gap. Completion must come from the run, never from the socket.
