AI Code Generation Gone Wrong

Google Antigravity
, , , ,
1

very annoying.

how can it be when i have been building the project for several months on my own and have done in-depth debugging.when i turned to google Antigravity and hoped to get the best FRONTEND of gemini 3 pro.

but instead there are a lot of duplicate UI/UX and it’s even worse :

  1. I never gave any command to change the backend configuration because from the beginning I only needed it for UI/UX design.I never gave any command to change the backend configuration because from the beginning I only needed it for UI/UX design.but this is my hardest blow because AI is trying to configure public frontend from cloudflare to cloud run!! this is very close to the backend and very fatal.
  2. For some reason, since 2026, AI has not obeyed the commands given, they tend to work quickly but the results are beyond reason (the resulting code has no rules)and finally i need to fix this 1/1. this is so crazy because it’s not about cost but time (time is more expensive than money that can be earned)

I just hope this gets fixed, I know and understand the costs of the model used. but at least if it is a matter of cost then just give it a longer COLDDOWN.but because the cooldown is longer, make sure there is a Byok system. at least this is better than nothing

I just hope, and will decide whether I and many people will survive or remain the same with the same goal.

thanks

2

Hello @BATAL,
Thank you for sharing this feedback. It is incredibly frustrating when the agent introduces regressions or rewrites stable logic while attempting to fix a specific issue.

Here are four best practices you can use to prevent unintended code changes:

  • Just like a .gitignore file, you can create a .geminiignore file in your project root. Add paths to your stable modules, core libraries, or completed features here.
  • In the chat interface, be mindful of which files are pinned as context.
  • Avoid broad instructions like ‘Refactor the code to be cleaner.’ Instead, use specific, constrained prompts.
  • When the agent presents a plan or code block, use the Diff View (Compare) feature before clicking ‘Apply.’ If the agent attempts to modify a file you didn’t ask for, reject the plan and respond with: ‘Revert changes to [filename]. Only touch the requested file.’