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
I'm currently unable to use the gemini-1.5-pro-exp-0801 model with this repository.
Additionally, the "Clear Chat Content" button at the bottom of the chat interface is easily accidentally pressed, especially on mobile devices. This can lead to unintentional loss of the entire chat history, which is frustrating and disruptive.
Solution Description
I would like the repository author to add support for the gemini-1.5-pro-exp-0801 model.
Furthermore, I propose adding a confirmation prompt before clearing the chat content. This could be a simple pop-up dialog asking the user to confirm their action. This would prevent accidental clearing of the chat history and improve the overall user experience, particularly on mobile devices.
Alternatives Considered
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered:
If you are deploying the version on vercel, you need to redeploy after modifying the environment variables to make them effective. If you are deploying using docker, you need to restart the docker image to make it effective.
Problem Description
I'm currently unable to use the gemini-1.5-pro-exp-0801 model with this repository.
Additionally, the "Clear Chat Content" button at the bottom of the chat interface is easily accidentally pressed, especially on mobile devices. This can lead to unintentional loss of the entire chat history, which is frustrating and disruptive.
Solution Description
I would like the repository author to add support for the gemini-1.5-pro-exp-0801 model.
Furthermore, I propose adding a confirmation prompt before clearing the chat content. This could be a simple pop-up dialog asking the user to confirm their action. This would prevent accidental clearing of the chat history and improve the overall user experience, particularly on mobile devices.
Alternatives Considered
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: