After the recent Google AI Studio Update, the code assistant started saving the chat history, due to which any new prompt to the AI just confuses the AI and it responses to a prompt I made 2-3 Steps back. Additionally, even if it gives a response it only gives a preview/ “Updated files” but doesn’t update it on the code. This issue needs to be addressed urgently as many users are not able to continue to code on it and build new applications.
same issue here, my chat is broken
Hi @toxnaliz ,
Hi, @Mrinal_Ghosh
After going through your response I downloaded Google Chrome as I was earlier using Opera. After logging in my credentials it look exactly the same. I have attached a screenshot to show you the issue. Looking forward to hearing from you.
Hi @toxnaliz ,
Thank you for bringing this to our attention. We truly appreciate you flagging this issue. A bug has been filed internally!
Hi @Mirko_A,
Thank you for keeping me posted and raising an issue internally. Just to keep you posted even on safari on my phone its the same, i am guessing its a issue based on the region. Anyways, I am looking forward to seeing a update come up as soon as possible as it the moment without resetting the Code Assistant, its impossible to to add a prompt to the AI as the AI keep on getting confused and answers to a prompt made by me 2-3 prompts back. I have attached a screenshot to show the mobile version too.
Hi @Mrinal_Ghosh ,
Just to bring to your notice. My older project shows the same (i.e No reset button). However When i went to create a new Project it shows the reset button. I have attached 2 screenshots so that you could address the bug accordingly.
Hi @Mrinal_Ghosh,
Sorry to bother you, but I just wanted to know if the issue will be patched any time soon. If not, then I have to download the ZIP file and then add each text file to the new project that had the reset button. Hope the two screenshots clarified the bug much better.
The issue has been solved, and now even older projects have the reset conversation button. Thank you, @Mrinal_Ghosh, for raising the issue internally.
