`Antigravity 2.0` backlash: chat-only agent surface removed core IDE controls

// related

• #0001

  #0001Agents & toolsGoogle AI Forum2 hours ago

  `Antigravity` backlash: editor removed, agent command center takes over

  60radar

  AntigravityAI coding IDE — Google’s agent-first dev tool

  The update shifts from a full IDE into an agent hub. Losing file-first editing weakens it as a daily driver; worth watching before switching workflows.

  • —The core complaint is concrete: files, editor, terminal, and change tracking no longer feel like one controlled workspace.
  • —A CLI is framed as a poor replacement for a full IDE. For app debugging, terminal-first flow adds friction.
  • —Cursor and Windsurf were named as competitors that benefit if Antigravity drops its integrated editor.
  • —Only 5 posts from 3 participants, so this is an early friction signal, not broad market proof.

  Source: discuss.ai.google.dev/t/you-did-not-upgrade-antigravity-Read original →
• #0002

  #0002Agents & toolsGoogle AI Forum2 hours ago

  `Antigravity CLI` `agy` loses auth session in WSL 2

  40radar

  Antigravity CLICoding agent CLI — runs terminal workflows via `agy`

  WSL 2 runs trigger browser login on every agy execution. Skip WSL use for now if repeated auth breaks your coding loop.

  • —Repro path is simple: run agy in Ubuntu on WSL 2, complete Windows browser auth, exit, then run it again.
  • —Expected behavior is a persisted Linux-side session; actual behavior is fresh authentication every run.
  • —Reported environment is Windows host plus WSL 2 Ubuntu 22.04.5 LTS, so native Linux/macOS behavior is not covered.

  Source: discuss.ai.google.dev/t/bug-antigravity-cli-agy-fails-toRead original →
• #0003

  #0003Agents & toolsGoogle AI Forum2 hours ago

  `Antigravity 2.0` Forced Update Reportedly Breaks Project and Chat Mapping

  50radar

  AntigravityAgent IDE — Google-linked AI coding workspace

  A forced update allegedly mixed projects with conversations, exposed encoded names, and triggered agent crashes. Treat agent IDE auto-updates as production risk until rollback and workspace recovery paths are clear.

  • —Reported failures include swapped project/chat mapping, URL-encoded project names, missing UI elements, and repeated Agent terminated due to error crashes.
  • —No rollback path and no forced-update toggle are the real risk: one unstable release can block active client, legal, or competition work.
  • —Before relying on agent IDEs for paid work, keep workspace exports, repo-level backups, and versioned notes outside the tool’s project database.

  Source: discuss.ai.google.dev/t/antigravity-2-0-forced-update-brRead original →