Jagadish K.

I believe that was done because the socket is not available when the UI is initially loaded. We could queue up the messages so that they can be fired once...

This could work... ``` // frontend/src/socket/socket.ts const socket = new WebSocket(WS_URL); // Define a queue to hold messages that are to be sent when the WebSocket connects const messageQueue: SocketMessage[]...

I am having this issue too. I created a new next.js project. I have ollama running locally with Phi-4. When I asked it to boot strap it with `bootstrap this...