Google Antigravity release notes: 2.0.11 fixes startup and Open IDE

Google Antigravity 2.0.11 is a small changelog entry, but it touches two things that often decide whether agent work gets reviewed at all: the app has to start, and the handoff into the IDE has to work.

Google Antigravity is Google's agentic development platform, where coding agents can work inside projects while humans set scope, permissions, and review. An agentic IDE is a coding environment where the agent's work can be reviewed in the same workspace as files, terminals, and project rules.

Source: Google Antigravity Changelog

Google Antigravity release notes: what changed in 2.0.11?

The 2.0.11 changelog entry is dated June 3, 2026, and is titled "Antivirus and Open IDE fixes". Google says new versions roll out gradually and may take a few days to reach all users.

There are two verified fixes:

• Google fixed an issue where some antivirus products could cause a dark blank screen on app startup.
• Google fixed bugs related to the Open IDE button.

Source: Google Antigravity Changelog

Why this changelog entry matters

This is not a new model or a major new agent feature. It is more ordinary than that: fewer failures at startup and fewer problems when a project needs to open in Antigravity IDE.

For Swedish and Nordic teams testing coding agents, that matters. If work from an agent gets stuck behind a blank startup screen, or cannot move cleanly into a review workspace, the result is often copy-paste, guesswork, and loose Slack threads. When the Open IDE flow works better, it is easier to inspect changed files, check assumptions, and run the right tests before anything moves forward.

Hammer's angle here is Tool Forge: build agent workflows that work in real environments, with clear permissions, scoped access, approval gates, and logs. Security does not have to mean avoiding integrations. It means connecting them in a way the team can audit.

What to test today

If 2.0.11 has reached your installation, test the handoff itself:

• Start Antigravity in a non-critical codebase where you already know how the project should behave.
• Open the current project in Antigravity IDE when the Open IDE button is available.
• Ask the agent to summarize what needs review, not to make more changes immediately.
• Check whether antivirus or endpoint security tooling still blocks app startup.

Source: Google Antigravity documentation and Antigravity IDE getting started

Short example: use the new Antigravity feature

Human step: Update to Google Antigravity 2.0.11 when the version has reached your installation. Open an existing project and use the Open IDE button if it appears. Then paste the prompt below to the agent inside the opened workspace.

Source: Google Antigravity Changelog

Review this Antigravity project after the Open IDE handoff. Summarize changed files, current assumptions, visible startup or environment blockers, and the tests a human should run before approving more agent work. Do not edit files.

Good output should:

• Separate verified file changes from agent assumptions
• Mention environment or security blockers if they are visible
• Suggest concrete tests or manual checks
• Mark what a human should approve before the agent continues

What we are watching next

This post covers only Antigravity 2.0.11: the antivirus startup fix and the Open IDE fixes. The next useful post should cover actual new functionality, a new migration rule, a new CLI or IDE change, or documentation that changes how teams should work with Antigravity.

Source: Google Antigravity Changelog