As I continued Vibe Coding in the Google AI Studio build environment, I noticed several issues. First, after a certain amount of development, the model (AI) stops responding normally. This can be resolved by clearing the chat. However, as development continued, bugs appeared that could not be resolved no matter how many times I gave instructions. This is the story of how I managed to solve that. The model tries various methods, but even after repeating five or six times, it simply cannot fix some of the bugs. For example, I would add a function to delete elements on the screen, but pressing the button would not delete them. The model understands what the problem is, but it feels like its ability to solve it hasn’t caught up.

I decided to move to Google Jules to have it check for bugs. Jules is very slow, but it investigates the cause of bugs. However, even when I have Google AI Studio try the solution based on that, it still cannot solve it.

So I tried Antigravity. Well, it’s becoming something more than a simple vibe coding, isn’t it? However, I learned something important from that. The problem that absolutely could not be solved in Google AI Studio was resolved in Antigravity.

It seems that the Google AI Studio build environment stops working correctly when the app tries to display popup messages such as window.confirm() or window.alert(). The message is not displayed, and the action immediately preceding it fails. Nevertheless, Google AI Studio does not recognize that using window.confirm() causes issues. As a result, it writes code that displays popup messages itself. The Google AI Studio build environment basically outputs almost no error messages. Because of this, I didn’t know the cause, which was frustrating. This can be confirmed by explicitly asking Google AI Studio to create an app that displays popup messages using window.confirm() or window.alert() (naturally, this will not work).

In the Antigravity test environment, popup messages are displayed normally and work. In other words, if you instruct it not to use window.confirm() or window.alert(), the problem shouldn’t occur even in Google AI Studio.

This issue has already been reported via Google AI Studio feedback, but it is likely frustrating Vibe Coders all over the world.