Feature/chat on demand

[zhangdjr]

Implemented two features actually:

1. Implemented chat on demand for certain UI components, where users confused about how to use the app can click on a circluar question mark to receive info while being able to ask follow up questions.
2. Implemented a chat saving feature where users can save past chats sorta like in chatgpt.

[samcraftt]

Sweet additions.

Since the first chat on demand message is always delivered to the user with no input from them, should we just hardcode the first message, so as to not have to wait for the chatbot to respond if it's essentially going to say the same thing every time? Then on subsequent queries we can generate more info via chatbot to answer follow up questions.

If it's too tedious then nvm, just a thought

[zhangdjr]

Sweet additions.

Since the first chat on demand message is always delivered to the user with no input from them, should we just hardcode the first message, so as to not have to wait for the chatbot to respond if it's essentially going to say the same thing every time? Then on subsequent queries we can generate more info via chatbot to answer follow up questions.

If it's too tedious then nvm, just a thought

I just didn't want to write an entire info blurb for every single ui component, I thought it would be easier to just have the LLM retreive the info needed using RAG from the docs we gave it. And after some time, users will probably be familair enough to stop asking questions about UI. Just my two cents. But if you really want, I can just hard code the info blurbs. What do you guys think? @akgohain @samcraftt

[samcraftt]

True, if we were to save a default info blurb for every component we provide this for that'd be clutter. So looks good to me!