🚀 Feature Request
Currently, in the Pipali chat interface, AI responses are displayed entirely all at once after the backend finishes generating them. For longer answers, this creates a perceived delay for the user and feels less interactive compared to standard modern AI chat interfaces.
Describe the solution you'd like
I propose adding a progressive typing or streaming effect for AI messages. The text should appear dynamically, making the app feel significantly faster, more responsive, and natural.
Technical Approach & Questions
Since I want to submit a PR for this, I'd love to align with the current architecture (React 19 + Bun + WebSockets) before writing the code. There are two ways to tackle this:
- Real-time Streaming: If the backend
Director and WebSocket routes already support emitting partial tokens for the ATIF step, I can hook the frontend up to stream the text as it arrives.
- UI-Simulated Effect: If the backend currently only sends the completed
ATIF step at the end of the thought loop, I can create a React component/hook to simulate a fast character-by-character typing effect on the frontend once the payload is received.
Additional context
I am ready to work on this and raise a PR! Could the maintainers let me know which of the two approaches above fits best with the current roadmap?
🚀 Feature Request
Currently, in the Pipali chat interface, AI responses are displayed entirely all at once after the backend finishes generating them. For longer answers, this creates a perceived delay for the user and feels less interactive compared to standard modern AI chat interfaces.
Describe the solution you'd like
I propose adding a progressive typing or streaming effect for AI messages. The text should appear dynamically, making the app feel significantly faster, more responsive, and natural.
Technical Approach & Questions
Since I want to submit a PR for this, I'd love to align with the current architecture (React 19 + Bun + WebSockets) before writing the code. There are two ways to tackle this:
Directorand WebSocket routes already support emitting partial tokens for theATIFstep, I can hook the frontend up to stream the text as it arrives.ATIFstep at the end of the thought loop, I can create a React component/hook to simulate a fast character-by-character typing effect on the frontend once the payload is received.Additional context
I am ready to work on this and raise a PR! Could the maintainers let me know which of the two approaches above fits best with the current roadmap?