`Antigravity 2.0` Installer Overwrites Dual-Version Setups

// related

• #0001

  #0001Agents & toolsGoogle AI Forum21 minutes ago

  `Antigravity IDE` 2.0.1 Dev Container Attach Fails on Missing Linux Server Tarball

  50radar

  AntigravityAI coding IDE — supports remote Dev Container servers

  The container install reaches Google’s CDN, then gets 404 for every linux-x64 server URL. Pin or delay upgrades if Dev Containers are part of daily work.

  • —Antigravity IDE 2.0.1 commit bf9a033f... requests Antigravity-reh.tar.gz, but all 4 CDN candidates return 404.
  • —DNS, TCP/TLS, curl, and wget all work inside the container, so this is a release publishing gap, not local networking.
  • —Affected path is remote server install under ~/.antigravity-ide-server/bin/...; local editing may work, container attach is the broken flow.

  Source: discuss.ai.google.dev/t/bug-report-dev-container-attach-Read original →
• #0002

  #0002Agents & toolsGoogle AI Forum1 hour ago

  `Antigravity 2.0` upgrade can duplicate repo projects; consolidation scripts exist

  40radar

  AntigravityAI coding IDE — Gemini-powered agent workspace

  The workaround maps duplicate project UUIDs, rewrites agyhub_summaries_proto.pb, and deletes redundant ~/.gemini/config/projects files. Useful only if the upgrade broke your workspace history.

  • —Run find_uuids.py first to generate consolidate_mapping.json; then run consolidate.py after checking the mappings.
  • —Project definitions live in ~/.gemini/antigravity/agyhub_summaries_proto.pb, while redundant project files sit under ~/.gemini/config/projects.
  • —Tested on one small project before bulk use. Sandbox restrictions may block deletes, so manual rm cleanup can still be required.

  Source: discuss.ai.google.dev/t/if-you-need-help-consolidating-pRead original →
• #0003

  #0003Agents & toolsGeekNews2 hours ago

  `Mirage`, a unified virtual filesystem for AI agents

  70radar

  MirageVirtual filesystem for AI agents — mounts SaaS as one tree

  Different SaaS backends become one filesystem tree. Agents can use Unix tools instead of learning every SDK or MCP, so cross-service automation gets simpler.

  • —Mounts S3, Google Drive, Slack, Gmail, and Redis into one filesystem tree — fewer integration surfaces for agents.
  • —Agents can work through Unix-style bash tools, reducing the need to teach each agent service-specific SDKs or MCP interfaces.
  • —Cross-service pipelines become file operations. Moving data between storage, chat, mail, and cache can be scripted more cheaply.

  Source: news.hada.io/topic?id=29681Read original →