Are they actually listening to the community?
At least from what I've seen, not a single official Google representative or moderator has responded ..
Please Google, this is the only way you're gonna win the AI race
This is NOT about AI agents.
I work on a project in Antigravity and the latest changes are already saved correctly. But when I open the same workspace in VS Code, the code suddenly gets reverted/overwritten with an older version/state.
It seems like VS Code is restoring some old workspace/editor state and writing it back to disk.
Has anyone experienced this with VS Code + Antigravity? What causes this, and how can I prevent VS Code from overwriting the newer files when opening the workspace?
This is NOT about AI agents.
I work on a project in Antigravity and the latest changes are already saved correctly. But when I open the same workspace in VS Code, the code suddenly gets reverted/overwritten with an older version/state.
It seems like VS Code is restoring some old workspace/editor state and writing it back to disk.
Has anyone experienced this with VS Code + Antigravity? What causes this, and how can I prevent VS Code from overwriting the newer files when opening the workspace?
I've been relying on AI coding tools quite a bit while working on a fairly large web app, and today I hit something that genuinely annoys me
I asked it to make a small UI change on a single page. The change looked fine, so I moved on.
A little later I started getting weird failures that seemed completely unrelated
getHomeUrl()) had somehow disappeared, causing login to throw 500 errorsAfter digging through the diff, I realized the AI hadn't just edited the file I asked for. It had silently rewritten more than a dozen unrelated files using what looked like stale context or older snapshots
If I hadn't reviewed the changes carefully, I probably would've spent hours chasing "random bugs" that were actually regressions introduced by the AI
I'm curious if anyone else has run into this (i only use Antigravity)
Please improve Copilot’s cache and workspace refresh
I use Antigravity and Copilot in the same project, both set to auto-commit after each task via markdown. When I switch to Copilot, it sometimes uses an old file state and overwrites Antigravity’s committed changes, even in a new chat
Copilot should always refresh the latest repository state before editing or committing
Has anyone experienced this?
I'm using GitHub Copilot alongside Google Antigravity. If Antigravity modifies a file and I then switch back to Copilot, Copilot sometimes overwrites the file with its stale cached version, wiping out all the changes Antigravity just made.
The root cause seems to be that Copilot's replace-in-string/file edit cache isn't staying in sync with the latest file state before applying edits.
Has anyone found a workaround, or is this a known issue?
(yes, i know i can just start a new chat. But i don't want to do that because then Copilot has to learn from the scratch)
I feel like GitHub has made the session limit and weekly limit on the legacy annual plan noticeably more restrictive recently
it feels around 25-30% stricter than it used to be. I'm hitting the limits much faster, despite my usage patterns staying pretty much the same or less.
is anyone else noticing this too? Or is it just me? 🤔
the annoying part is that GitHub controls the limits and how they're measured, so it's hard to know if anything actually changed
I've been on the Annual Legacy Plan for a while, and recently it feels like both the session limits and weekly quota are being used up much faster than before
my usage hasn't really changed, so I'm wondering if GitHub changed how usage is calculated
Anyone else noticing this?
[SOLVED for me] just a bug
I suddenly lost access to the top-tier model, has this happened to anyone else?
now I'm being asked to upgrade to Max?!
