Antigravity slow response and low quality in making UI

Hi, I’m having some problems with Antigravity and I’m wondering if anyone has the same experience. The Antigravity is very slow, and sometimes it just lags or gets stuck for quite a long time. The output quality is also not very good.Another problem is that sometimes the agent says it understands what I want, but when it actually makes the changes, it does something completely different from what I asked for. Is there anything I can do to improve this?

Can’t say I have had the lag issue, but weeks ago I realized if I have gem 3.8 create wire/HIFI/video (many diff options) mock ups to explore before you make the plan official > the output is phenomenal. I think it does a few things. 1. allows you to explore different ideas and visualize them. 2. Allows the agent to show you what it plans to do while also keeping an artifact of what it plans so it sticks to it. 3. Helped me see how to direct AGY better. IE If I wanted a specific UI style, and it wasn’t outputting that.More than likely I just didn’t use the proper design vocabulary. Prompting for glassmorphism (frosted translucent panels, blurred backdrops) versus neo-brutalism (thick borders, high-contrast flat solids, hard drop shadows) or flat design completely changes how the model structures the CSS and layouts. Giving it an exact aesthetic keyword alongside an artifact gives the agent zero room to drift. Also pairing visual prompts with built-in skills like modern web design and a11y forces the agent to follow strict accessibility rules and structured layout patterns rather than winging the implementation. If you share controlled images to gemini in web app it helps not pollute context If you need help with how to word something. “This is what it looks like but I do not know the term for the effect I want - explain effect- what is the UI style” then you can 1. learn (there is always cool new UI) 2. go back to AGY with a screen shot and the proper terms. It helps if it can see its work too. You can cut out gemini web app if you wanted to discuss in AGY - I just do it personally to have a front end teacher with gemini web app and keep AGY orchestrating. (although now that I say this my engineer mind spins you could have a blank workspace folder you just ask AGY questions about specific topics. that allows you to even upload extended videos into the folder with audio speaking and you could take the information you learned from your - teacher conversation project - and apply it to your actual workspace). hope I didn’t overload!

Hi @LEE_WAI_LOONG,

Welcome to the Forum,

Thanks for reporting this. To help us look into it, could you share:

  • Which Antigravity platform you’re using (Antigravity app, IDE, or CLI) and its version
  • Your operating system
  • The model you had selected

Meanwhile, these steps usually improve speed and output quality for UI work:

  1. Start a fresh conversation for each new UI task. Long conversations carry a lot of earlier context. That slows responses and can make the agent lose track of your latest instructions. Click New Conversation (+) before starting a new task.

  2. Use Plan mode (/plan) and review the plan before approving it. The agent writes an Implementation Plan first, so you can catch a misunderstanding before any code changes. Break large UI requests into steps, e.g. layout → styling → state handling, instead of asking for a whole interface in one prompt.

  3. Create a Markdown file in .agents/rules/ describing your UI framework, component conventions and hard constraints, so the agent’s changes match your expectations.

  4. For complex layouts or changes across many files, pick a higher-reasoning model from the model selector (or a higher reasoning/thinking level, if your model offers one). These give better results but respond more slowly. For quick UI tweaks, a faster model will feel much more responsive.

  5. If the chat stops responding, restart Antigravity. In the IDE, you can instead run Developer: Reload Window from the Command Palette (Ctrl+Shift+P / Cmd+Shift+P).

  6. Make sure you’re on the latest release. If the problem continues, use the in-app Give feedback option with Include diagnostics while submitting.