Anyone has had this problem? After the issues yesterday my environment kept getting stuck in the prototype view.
So I did a " Rebuild Environment" command as suggested in the help. Now I cannot see any of the previous chat in prototype (or anywhere). Moreover, gemini now thinks this is a new project (it’s been almost 2 weeks of daily work) and seems to think I am trying to start a new project (even though the code view and the codebase is there and the app is working)…
Any help and suggestions would be appreciated.
How do I get it back?
How do I resume?
Or how do I take what had been done so far and proceed.
Thanks!
Hey there! We’re trying to reproduce the issue on our end - there’s a similar thread with a troubleshooting step here - would you mind trying that?
I can see the json 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.
So, after following that thread I was able to find a bunch of what looks like backed up files for
capra-thread.json. so I renamed the current one old-capra-thread.json and replaced it with the one of the backups (under /threads) that looked like it had the most history. That kind of works. It shows now in my thread on prototyper (looks like only up to a point and only up to until last night’s latest change, even though now I am running an older commit that worked).
Would love to get on a screen share before I mess this up terribly 
Meantime, let’s see what you guys come up with or how much of a mess I’ve made of this
Ah today, the threads dir is code view AI chat threads, and capra-thread is the Prototyper thread, so it’s not really a backup. But we definitely need to get to the bottom of what happened to your Prototyper thread :-/
Yes, I found out the hard way. Doing that “trick” snags the prototyper back to the black screen of hell - it would be great to figure out what happened, ideally how to recover, and ultimately how one can move forward continuing development with the prototyper cooperating.
1 Like
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.
Ya, I just created a new branch and then I created a new environment from that branch. But the prototype tool is non existent that way. I guess the way forward is to keep coding the way it works almost anywhere else. But I was really digging the whole start to finish on prototype where I barely had to go into the code. I got astonishingly far and hadn’t yesterday’s update messed my history, this was getting really far and interesting without going to the IDE view. Kind of bummed that I got the project far and now it’s going to be slow because it is clear the Gemini on the IDE side has much less context and ability to understand the app. The beauty of using the prototyper for just about all of it is that it seemed to be aware of the scope of all that had been built. The IDE does not seem (keeps asking me for paths for things that it could easily find if it understood the scope of the app, etc).
1 Like
I had the same issue, somehow got wiped. I got it to work again by creating a new blank project (told prototyper to create a blank web app) and manually added all the files from the wiped project
1 Like