Summary
Assistant responses never render in the browser. The page shows nothing for the response until I manually reload, after which the full response appears. This happens for every response, not just long ones.
Reproduces consistently across two devices and three browser/OS combinations, so it does not look device-specific.
Steps to reproduce
- Open a Claude Code session in the browser (Remote Control).
- Send any message.
- Wait.
Expected
The response streams in and appears incrementally.
Actual
Nothing from the response is displayed. The area stays empty no matter how long I wait. Manually refreshing the page (Cmd-R / pull-to-refresh) makes the complete response appear immediately.
Because a refresh always surfaces the response, the server side appears to be generating and persisting it correctly — only the live delivery/render path to the browser fails. This looks like the streaming (SSE) connection either never delivers events or the client never renders them, with no visible error or timeout.
Environment
- iPad — Safari: reproduces
- iPad — Chrome: reproduces
- iMac (macOS) — Safari: reproduces
Exact OS and browser versions not captured; happy to add them on request.
Impact
Every response requires a manual page refresh to read, which makes the browser client effectively unusable for normal back-and-forth.
Additional notes
Both a mobile Safari/Chrome (which on iOS share WebKit) and a desktop Safari are affected. I have not yet tested desktop Chrome or Firefox — can do so if that would help narrow it down.
Summary
Assistant responses never render in the browser. The page shows nothing for the response until I manually reload, after which the full response appears. This happens for every response, not just long ones.
Reproduces consistently across two devices and three browser/OS combinations, so it does not look device-specific.
Steps to reproduce
Expected
The response streams in and appears incrementally.
Actual
Nothing from the response is displayed. The area stays empty no matter how long I wait. Manually refreshing the page (Cmd-R / pull-to-refresh) makes the complete response appear immediately.
Because a refresh always surfaces the response, the server side appears to be generating and persisting it correctly — only the live delivery/render path to the browser fails. This looks like the streaming (SSE) connection either never delivers events or the client never renders them, with no visible error or timeout.
Environment
Exact OS and browser versions not captured; happy to add them on request.
Impact
Every response requires a manual page refresh to read, which makes the browser client effectively unusable for normal back-and-forth.
Additional notes
Both a mobile Safari/Chrome (which on iOS share WebKit) and a desktop Safari are affected. I have not yet tested desktop Chrome or Firefox — can do so if that would help narrow it down.