You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, chat profiles in Chainlit can serve multiple purposes:
• Acting as “tabs” to differentiate between chats/flows.
• Providing customized system prompts/agents.
• Allowing users to switch between models.
While flexibility is advantageous, there are several downsides with this approach. The current dropdown-based implementation doesn’t effectively support any of these use cases. Dropdowns are not ideal for tabbed navigation, and the chat profile buttons feel too large and intrusive for the other use cases, especially on mobile devices.
All of these features are becoming common use cases, so I think it would be good to think about what should be the default way to support these use cases.
We propose splitting these functionalities:
Tabs instead of chat profiles – Replace the dropdown with a tab-based UI, similar to Streamlit, for better chat/flow differentiation.
Custom system prompts/agents – Introduce a sidebar section with a list of named entries (with icons), similar to Gemini’s Gems, ChatGPT’s Custom GPTs, or LibreChat’s agents (see mockup).
Add examples for model choice using the Chainlit settings.
This approach would improve usability, remove clutter, and give developers using Chainlit better guidance on what functionality to use.
Mockup:
Let me know what you think!
The text was updated successfully, but these errors were encountered:
Just to be clear here, this is not about allowing users to create personas, it's about guidance in the UI for general functionality that users of Chainlit might want to use. Making chat profiles a bit less of a "catch all" type functionality.
Chat Profiles are useful if you want to let your users choose from a list of predefined configured assistants. For example, you can define a chat profile for a support chat, a sales chat, or a chat for a specific product.
The image shows using chat profiles as a way to change models.
Currently, chat profiles in Chainlit can serve multiple purposes:
• Acting as “tabs” to differentiate between chats/flows.
• Providing customized system prompts/agents.
• Allowing users to switch between models.
While flexibility is advantageous, there are several downsides with this approach. The current dropdown-based implementation doesn’t effectively support any of these use cases. Dropdowns are not ideal for tabbed navigation, and the chat profile buttons feel too large and intrusive for the other use cases, especially on mobile devices.
All of these features are becoming common use cases, so I think it would be good to think about what should be the default way to support these use cases.
We propose splitting these functionalities:
This approach would improve usability, remove clutter, and give developers using Chainlit better guidance on what functionality to use.
Mockup:
Let me know what you think!
The text was updated successfully, but these errors were encountered: