Websockets are great for this. Initialize the completion with an id, and store the token stream while emitting as a websocket event. Keep the id in state some

Websockets are great for this. Initialize the completion with an id, and store the token stream while emitting as a websocket event. Keep the id in state somewhere on the client (url works great with pushstate). If the client disconnects then just replay the event stream for the id.