THe agent tries to use unix commands - REAL unix commands. i’ve been fighting with this since i installed antigravity, thinking that it was just a few of the editing tools. turns out, it’s the terminal. the fix is to go into the terminal settings and set the profile to be Powershell, not windows powershell. then the agent can use tail -n 100 without getting an error. it doesn’t have to use the get children nonsense, it can just use ls -al, etc - suddenly, my agent isn’t making all sorts of edit errors because it can actually use grep and sed and awk and cat correctly.
Same here. Thanks for the tip.
I suspect that Antigravity’s development team primarily works on macOS and doesn’t test their product as thoroughly on Windows systems as they do on Macs, and therefore does not include this kind of tips in the documentation. Could that be a root cause of this issue?
Yes, there’s definitely a room for improvement in the Windows/Powershell implementation of Antigravity. It consistently tries to run Bash commands on Powershell, fails, fixes the error, then tries again soon after. There should be away to ‘remind’ / ‘force’ the Agent to recognize the shell/operating system and act accordingly. Perhaps a rule or skill could do the trick but this should be built in…