you asked me to built my app on your platform, so I did. now, what? what kind of user experience is this? what in the world is going on? how is this even remotely acceptable? why are we allowed in just to get booted as soon as the Prototyper even musters a hint of coding language, even with it’s only to annoying blabber on about what it’s going do (instead of just doing it, you know?). the second it opens up a ’ character to mention a file, all hell breaks loose, the loading icon loads and the PROTOTYPER BLACK SCREEN OF DEATH (ALREADY WITH A SCREEN OF DEATH???) comes on, and the only thing left to do is reset the VM. this is pitiful and I am at my wits end. I am going clinically insane, for real. I am SO close to the finish line, I can’t move on, I need to wrap this up. this is NOT cool. why are you letting me in just to crash the second a request is made? this has been going on for 72 hours straight on my end. I cannot comprehend the lack of any sort indication of what is going.
recently, it started going back to the useless preamble on occasion and actually starting to write some lines, but it’s not long before the loading icon shows up and the session is doomed because of the PROTOTYPER BLACK SCREEN OF DEATH. I’ve reset so many VMs, I should have a title. this is screwed up. please tell us something useful. please. cuz you’re online Statuses are straight up lies, and have not shown a single indication of what in the world is going on. again, NOT cool.
even the Prototyper chat history is just pilling on, it so lengthy now, it’s ridiculous, why isn’t it resetting anymore NOW, when it was CONSTANTLY resetting for the past couple of weeks, even when it was not appropriate to do so?
I already realized from time to time the VMs gets slow… but I think it’s just their server too busy, this morning the prototyper wasn’t being able to complete anything, not even resetting was solving… I then reseted the vm and waited a couples of minutes to open the project again (thus receive a new VM, maybe a different one ?), then the prototyper was able to get back to work normally.
It’s also a good idea to ask the prototyper to refactor your code in case you have files that are getting excessively big 800… 1000… 1500 lines… it’ll work much more smoother and faster.
note that when the chat apparently clears the messages, it’s a bug, not a feature, and your chat history context is still all in the prototyper memory, the chat only really resets when the prototyper loses it completely, you’ll know that when after a reset he’ll ask you to prototype your app again, so you know he went completely blank of previous context
I personally would love to have a way to clear the prototyper context (without him wanting to prototype the thing again).
the way I see it, it’s a free product, that we can deploy for free on some fast servers. Myself I’m good with it, or else I’d be paying loads of api costs, to use some api based coding interface which I won’t.
I appreciate your response, I do. however, I disagree. we are both clients, paying or not. and I for one have been paying to use a Gemini API key and even though I’m rolling on 500$ of sign-up credit, they expire in June and I will start coughing up cash. there are standards. the situation is untenable. it’s inappropriate and shameful. where is the transparency?
one question for you t_rec. Are you always using the Prototyper view rather than the code view? I think if you are serious then I would switch to code view and use Gemini in there with Gemnin 2.5 Pro rather than the built in model the Prototyper uses. Also I would connect your project to GitHub for proper source control and that will protect you when things in the environment go wrong.
I’m just a user like you are but I’m finding the code view plus Gemini 2.5 Pro is much better and avoids crashes with the Prototyper.
