Screener AI Rewrite - Technical Details

We originally created Screener AI using WebSockets. While Django’s WebSockets worked pretty well, they had a few issues:
- The sessions were linked to the browser connection.
- If the user’s browser disconnected, the answer generation also stopped in the backend.
- This was especially problematic on mobile, where browsers are stopped after 5 seconds if the user switches apps or turns off the screen.
The above caused multiple cases where users didn’t receive the answer when they returned to the query they had asked.
That’s when we realised that we needed to decouple the user’s browser connection and the agent fetching the …







