The Antigravity changes shipping between late April and early May 2026 look quiet on the surface, but several of them touch the developer workflow directly. Here are the three updates I tested on real projects and concluded "this actually changes my daily routine."
Rather than walking through the release notes, I focus only on what you notice once you start using the new behavior. Marketing copy and on-device experience always diverge a bit; this article aims to fill that gap.
Update 1: Direct Unreal Engine 5 Integration
Since early May, Antigravity behaves differently when you point it at a UE5 project. Specifically, opening a directory containing .uproject now lets Antigravity read the relationship between Blueprints and code as a structured graph.
Before, handing a UE5 project to Antigravity was risky: the tool couldn't see how Blueprints referenced C++ source, and editing one side would silently misalign with the other. After this update, Antigravity holds the .uasset reference graph, so questions like "what breaks if I delete this C++ function that's referenced by a Blueprint?" come back with sensible answers.
I tested it by adding a custom AI behavior tree to a Third Person template. The full loop — add a BTService, verify Blueprint references, run the editor test — took about 30 minutes through Antigravity. That used to easily take 1–2 hours, so for UE5 developers, this is a long-awaited change.
Update 2: A2A Protocol Support
Agent-to-Agent (A2A) protocol support cut the failure rate when wiring external agents into Antigravity. Calling unsupported agents used to spin in retry loops because tool-call argument formats didn't match. With A2A in the path, first-call success is the norm.
Concretely, calling external MCP servers or third-party AI agents from Antigravity is dramatically more stable. A small Slack notification agent I run locally used to need a retry on roughly one in five calls. Now it lands first try almost every time.
To verify A2A is on, open Antigravity Settings → Integrations and confirm A2A Protocol Support is Enabled. Capable agents will use this transport automatically.
# Minimal example of starting an A2A-capable agent on the other side
# (illustrative — small custom agent layout)
node ./agents/notify-agent.js \
--protocol a2a \
--port 7878 \
--name slack-notifyUpdate 3: Smarter Sub-Agent Splitting in AgentKit 2.0
AgentKit 2.0 itself shipped in April, but the sub-agent splitting logic landed an upgrade in May. Splitting used to trigger off raw file count. Now it accounts for change independence.
Before, anything past 30 touched files would parallelize mechanically. Now, when Antigravity recognizes a workload as "consecutive edits to the same file" (no real parallelism gain), it stays single-agent. The practical win is fewer wasted agent startups.
On my mid-size projects (80–120 files), I'm seeing 15–20% shorter end-to-end time for AgentKit-driven runs between April and May. The smarter split judgment plus fewer redundant integration phases stack together.
Known Issues and Workarounds
The May rollouts come with a handful of small snags I want to flag.
First, the initial UE5 indexing pass can look frozen for 5–10 minutes on projects over 10 GB. Antigravity is building the asset reference graph in the background; it's normal as long as Task Manager shows CPU activity.
Second, the first call to an A2A-capable agent can fail handshake under some TLS configurations. Restarting the agent with --protocol a2a-insecure works around it for local development — never in production.
Third, after the AgentKit 2.0 split-logic update, I once saw .gitignore-listed paths (node_modules, .next) get pulled into the agent's working set. An explicit .aignore file resolves it.
# Example .aignore
node_modules/
.next/
dist/
build/
Where to Start
If you touch UE5 at all, jump straight to the integration work. Otherwise, the AgentKit 2.0 refinement is the highest-impact change for normal projects. A2A only matters if you're already wiring external agents in — it's safe to circle back later.
A Concrete Next Step
Tomorrow, drop a .aignore into the Antigravity project you use most. Five minutes of work, and AgentKit 2.0's smarter splitting becomes noticeably lighter to run. Smallest investment for the largest immediate payoff this month.