My chat box text keeps regenerating

Google AI Studio
,
1

I have an AI chatbox in my AI Studio app that animates the text as if somebody were typing. It has been working, but suddenly the first speech bubble types line one, then speech bubble two starts, but triggers speech bubble one to start again at the same time. As line one finishes, speech bubble three starts, and bubbles one and two start again. Only after speech bubble three has finished, does speech bubble two start to generate line two and three etc…. I have tried so many times within AI Studio to get AI to fix it, but it keeps acting the same no matter what fix the AI makes. I am only Vibe coding and cannot code myself. I do not know how to make it work.

3

It sounds like your chat bubbles are all listening to the same “start typing” event, so every time a new bubble begins its animation, the previous ones get triggered again. This usually isn’t a model issue — it’s a UI state problem inside the Vibe flow.

A few things you can try inside AI Studio:

  1. Make each bubble depend only on its own state
    If all bubbles are sharing the same variable (like a single “isTyping” or “currentMessage” signal), they will all restart whenever that value changes.
    Create a separate state variable for each bubble, or use a list/array where each message has its own typing flag.

  2. Turn off “Auto-trigger on update”
    If you used an animation block or “When input changes → animate”, disable auto-triggering. Otherwise any small UI update triggers the animation again.

  3. Wrap each message generation in a separate flow block
    Have each bubble’s typing animation triggered only when its own message is created, not when the next one starts.

  4. Reset animation state after each bubble finishes
    Some users have fixed this by adding a tiny delay + a state reset so the previous bubble can’t re-fire.

Since you’re using Vibe coding, you don’t need custom code — just make sure each bubble animation is isolated and has its own trigger. Once each bubble listens only to its own signal, the restarting loop should stop.

5

Thank you so much, Emma. I actually solved it with the change to Gemini 3.0. Sooo much better. I just did what I tried to do the day before; this time it worked. I really appreciate your thoughts though. :grinning_face: