Until Google either removes the ‘auto-save’ feature or allows users to disable it, it’s a good idea to manually andregularly create copies of your app whenever you have a stable version you don’t want to lose, IMHO. Click the ‘Copy app’ button.
Since the recently introduced ‘auto-save’ feature can’t be turned off via Settings at the moment, the Assistant saves your app code almost every time a change is made.
While this is often convenient, as it eliminates the need for manual saving, there are times when the Assistant messes up your code or made changes you regret. Although it is possible to retrieve previous code versions through the History feature, the process can be cumbersome and confusing.
Therefore, I believe it’s a smart practice to save a copy of your app whenever you reach a significant development milestone that you want to preserve.
Oh, yeah, sorry I did not read it fully. I dont think so that version history is canfusing, just think how it is work for 2 minutes in verison history panel, you have every prompt written that you have wrote and it is clear that it means this verison is with the changes made in this one prompt. Besides it there is (load app) version that means you start version of app in this chat ( this is very helpfull if assistant made new errors and problems, you can just go back to loaded version at start).
As well as the history feature, if the change was in the recent chat, you can scroll back through the chat window and use the ‘restore checkpoint’ button to restore to that point.
Checkpoints and history are lifesavers, no doubt, but sometimes “auto-save” swoops in like an overzealous superhero, making the last checkpoint vanish into thin air. Sure, we could argue about the pros and cons of auto-save until the end of time, but let’s face it: some folks love it, and others just don’t.
The perfect solution? A Google AI Studio setting that lets users decide what they prefer. Problem solved, everyone wins!
I agree making thing optional is good. But, if checkpoints are disappearing, that would seem like the issue which needs addressing. I’ve not noticed that myself. When the AI goes nuts and introduces a regression bug, I prefer to berate it and bully it into fixing the mistake, much like I would with a real person! It changed my settings icon from a cog to an indescribable squiggle a few versions ago, and I’m getting a lot of pleasure out of yelling at it to fix it over and over and over and…
It’s always funny when it replies super confident ‘As a world leading front end developer … I’ve triple checked the changes…’
Me: yeah, still doesn’t work.
I am preety sure that “auto save” was added because assistant code was not always respecting not saved code. No saved code was cocrrectly working like 2 month ago but like 2 weeks ago that was mess and I think they added auto save to make it sure that user will save the file.
