Refactor the Chatbot Message Render UI to make it reusable
We have a few different variant of Chatbot client implementation for connecting to different agent implementation. The core open-source codebase is only one of variant that consumes WebLLM based agent messages.
This ticket is about refactoring the chatbot message rendering UI to make is reusable across different agent implementation no matter it's backend or frontend LLM. This will make it possible to make all different chatbot UI implementation share the same message rendering codebase and reduce the maintenance work.
It will also make it easier to have different chatting UI design for different purpose. e.g. embedded as part of other workflow.
Refactor the Chatbot Message Render UI to make it reusable
We have a few different variant of Chatbot client implementation for connecting to different agent implementation. The core open-source codebase is only one of variant that consumes WebLLM based agent messages.
This ticket is about refactoring the chatbot message rendering UI to make is reusable across different agent implementation no matter it's backend or frontend LLM. This will make it possible to make all different chatbot UI implementation share the same message rendering codebase and reduce the maintenance work.
It will also make it easier to have different chatting UI design for different purpose. e.g. embedded as part of other workflow.