Hello, i have Antigravity installed form AUR and im trying to reopen old projects and chats, after i give the prompt it stuck on ‘waiting for user input’ but there’s no way to give an input. It’s so annoying can’t use it and i have a Pro Plan.
Same problem here.I have pro plan also
I solved it by starting a new chat.
Same here. but, starting a new chat does not solve the problem, it always waits for user input when the model is searching a file.
same how to fix it? pls tell us, I’ve noticed that there’s a bug when using different workspaces or importing plans from elsewhere.
It’s time to migrate to Cursor and GPT. Google has never cared about user experience.
Same issue, super frustrating… I had to manually downgrade to version 1.21.9, then it worked (see Google Antigravity)
Hey Guys, is there any solution for that yet?
Same problem, I was using a version from february till it forced me to update 10 mins ago. I updated and it does not work. The older version was doing fine for me. I want a stable IDE not the super newest one. Last time it was autoupdated and there was a very annoying bug: when left&right arrow keys are pressed, it was changing the IDE theme. I wasted 1 hour to stop autoupdate and to downgrade to previous version. Now I need to do the same.
If there are versions that must be updated, then classify some versions as stable and give us an option to UPDATE TO LATEST STABLE VERSION.
PLEASE RELEASE IT AFTER YOU TEST IT. AND PLEASE DON’T FORCE USERS TO UPDATE UNLESS IT’S A TESTED AND STABLE VERSION.
Edit: Downgrading does not work, all previous versions are forcing update to use chat. I’m moving to Codex.
It’s doing my head in. why on earth would it force us to upgrade. old version was fine. Surely there’s somewhere we can get feedback from this??
[Solved] It took for a while, but here’s how you can solve this issue:
1- If you are using GIT, go to your .git/config file. Check if there is a line:
worktreeConfig = true
Make it false (worktreeConfig = false), or delete the line.
2-Force clear the cache of Antigravity
First, quit Antigravity.
Open a terminal.
Run commands(the path might be different in Linux):
rm -rf ~/Library/Saved\ Application\ State/com.google.antigravity.savedState
rm -rf ~/.config/antigravity
3-Add some lines to User Settings (JSON)
Open Antigravity.
pres cmd + shift + P
Type:
Preferences: Open User Settings (JSON)
Add the lines below to json file:
“antigravity.agent.autoApprove”: true,
“antigravity.agent.allowedCommands”: [“*”],
“antigravity.mcp.autoApprove”: true
======*The line below is OPTIONAL to define agent’s allowed folders=====
“antigravity.agent.allowedPaths”: [ “PATH OF YOUR PROJECT FOLDER”, “PATH OF YOUR OTHER PROJECT FOLDER” ],
It will ensure agents are auto approved for every command it runs. You can manipulate these lines based on your needs.
Save the JSON file, then restart Antigravity.
These steps should solve the problem. If not, go to Gemini and work with it.
OPTIONAL:
I had been getting errors with grep_search command all the time, even before this bug.
Below is the solution of Gemini, not tested yet if it works but it makes sense. It simply tells grep_search command (Actually the entire Antigravity, to ignore those files) to skip following files since there is no chance that the model is looking for those files. It’s like .gitignore for grep_search:
“Even with permissions fixed, grep_search often hangs if it hits a massive directory. In a Laravel project the vendor and node_modules folders contain tens of thousands of files.
Do this immediately in your terminal:
cd YOUR PROJECT FOLDER
touch .antigravityignore
echo "node_modules/" >> .antigravityignore
echo "vendor/" >> .antigravityignore
echo ".git/" >> .antigravityignore
I have applied all the steps and now Antigravity works fine on my side.
I hope it helps you, if not try using Gemini (How ironic, using Gemini to fix Antigravity 
)
None of these options seems to work for me. Also, are you sure you want to give the editor autoapproval to run any command? 
Looks like this version (v1.23.2) of arch build for antigravity is bugged. I’ve been facing this issue almost daily & it’s so frustrating. Through some research & experimentation, it seems the issue is caused by the grep_search tool. Whenever this tool is invoked, the permissions interface never seem to show. Though, this isn’t the case always. If by any change this tool is able to run once somehow, subsequent runs for that session aren’t affected.
Now as of the temporary workaround until this gets fixed, provide the agent explicit instructions not to use grep_searchtool. Instead, ask it to use some alternatives like running the grep command in terminal manually or use read_file tool. For me, adding these below instructions at the end seem to work.
Do not use the `grep_search` tool as it seems to be having some permission issues (not being able to show the allow/deny buttons). Use alternatives instead.
You don’t need to change any user setting, no need to allow all commands to run without review either. Again, this bug is seriously frustrating, hope google’s dev team fixes it soon. Again, this seem to work for me. Not sure if it’d work for all. Worth a try, though.
We want FIX … makes usage almost impossible… 
Please fix this bug. Its super annoying.