Today while using Firebase Studio’s prototyper mode, I noticed that my Gemini history was completely wiped — all my previous builds were gone. Luckily, I didn’t need them anymore, so it wasn’t a big deal this time. Honestly, starting fresh even felt kind of nice.
That said, I’m concerned about what happens if this issue comes up again while I’m working on active changes or mid-build. Is there a way to recover or restore our last saved or deployed build if the prototyper history resets again? Or is everything permanently lost once that happens?
Would really appreciate some clarity on how persistence is handled here.
Yep - and if that file is missing or empty or such, then indeed it looks like the history was dropped, and we’ll definitely want to investigate why/how that happened.
Unfortunately I already started reusing the gemini and the past history was already unavailable. I’ll try to look for the file first if this thing happens again.
I can see the file but it only shows the history starting today. Everything else (past week-1/2) is gone. Now it thinks I am working on a new app and wants to prototype something new. Hard to get it to understand it needs to work on the app that is in the codebase/project I am in.
I have had the same exact problem. Yesterday i got to a good stopping point (I just got back to that commit) and then I resumed working on more functionality. It started getting really slow at around 9pm PST and I simply left because it was hanging my prototyper in the black screen.
This morning it was still not working so I tried all of this : Firebase Studio troubleshooting & FAQ
That got it back working but when I went to my Prototyper I had the same issue. All history was gone and it does not recognize my project. Unfortunately the context was major (and I was getting the hang of it) for it to keep on going. Yep, you are correct, big problem if you hare half-way (my case) through a project.
If this is a problem, then my question is: how do I get prototyper up to speed on the project so it does not think I am just beginning a new project.
Ideally there would be a way for it (Gemini on prototyper) to go over the codebase and allow me to resume working on an existing app. This case is an app I am working on, but this could be for any project (meaning, if I use another app/codebase) so I can keep using the prototyper as a tool for the app dev.
Right now it seems my only option is to keep using the IDE side of things and forget the prototyper. Needless to say this sucks. I was getting the hang of it and really gaining speed. Now I am kind of stuck with a half-baked app…
PS_ I can see the file ls -al ~/.idx/ai/capra-thread.json but when I do a less on it, it only shows the chat since this morning after it went blank on me. Unless there is a backup (maybe this would be a good idea to commit the chat history to the source control) I can’t seem to find any other chat history file via terminal.
I’ve had this issue a couple of times now. All I did was just keep instructing the AI to fix what was needed, and that seemed to work. The only downside is that I’m missing the history to restore from if I ever need it, and I’ve had to rebuild some pages again because of that—no way to go back and fix the messed-up code without a restore point.
Please note that the article I posted is not the “how to get your missing chat history back” discussed in this thread.
However, applying what is described in my post may solve the problem of agents starting with Blueprint creation in an existing environment where the chat history has disappeared.
I have an idea of a possible solution and will let you know in this thread when I have completed the verification on my end.
Temporary solution for the issue where agents restart Blueprint creation in existing workspaces (unofficial)
Verification has been completed, and I am pleased to report the following.
The following steps appear to allow you to continue editing without executing Blueprint creation in existing environments.
However, please note that if any conversation history has been saved in JSON files, it will be cleared.
To ensure you can revert to the previous state after executing the steps, please do not skip step 5.
Caution
This procedure is not an official guide, so please proceed at your own risk.
Enter the following command in the terminal and press the [Enter] key to execute it, creating backups of the current capra-context-state.json and capra-thread.json files in the context_backup folder:
Note: This prevents the context_backup folder and the backup files within it from being used as input for the App prototyper agent context.
Enter the following command in the terminal, press the [Enter] key to execute, replacing specific string in capra-context-state.json to switch from proposal creation mode to app editing mode:
sed -i 's/create-proposal/edit-app/g' /home/user/.idx/ai/capra-context-state.json
