The web UI talks to the agent over a streaming connection, and a streaming connection drops: a phone
locks, a laptop sleeps, a network handoff. Until this release a drop in the wrong place lost the
final_response, and the chat sat showing "Thinking…" forever with the answer already produced and
thrown away.
The fix is to treat the event stream as a log. Events are stored append-only with monotonic IDs, and
the browser reconnects saying "I have everything up to event N" (Last-Event-ID), and the server
replays from there. A dropped connection is now a delay, not a loss. This is the standard SSE
pattern, applied to the case that made it necessary, and it is the fix that makes the web UI
dependable on a phone on a mobile network.
The mobile fixes in the same release are exactly the kind you only find on a phone. A safe-area padding was counted twice, leaving a gap under the input bar. Body scroll was blocked, so Firefox Android could not push the focused input above the keyboard. A focus handler now forces the prompt into view when the keyboard appears.
That last one is the argument for the whole mobile thread in this log. On a phone, the keyboard is part of the layout, and a web page that assumes a static viewport has a text box you cannot see while you type in it.