Developer Feedback on Antigravity Extension Runtime & Ecosystem

As a developer team from Vietnam building AI-first extensions on top of Antigravity and Antigravity IDE, we would like to share some feedback regarding the current extension ecosystem and runtime experience.

After deploying and testing our extensions in production environments, we have noticed several platform limitations that are affecting developer experience and integration stability.

Some key concerns from our side:

• MCP tooling is still limiting flexibility for advanced agent workflows.
For more complex orchestration scenarios, agents still lack the level of adaptive interaction and dynamic execution needed for modern AI-first extensions.

• Antigravity Desktop App behaves differently from Antigravity IDE when handling extensions.
Some extensions work correctly inside the IDE but are not triggered consistently in the Desktop App runtime. This has already created inconsistent user experiences and customer complaints.

• The ecosystem still lacks a clear runtime communication protocol for extensions.
Developers currently do not have a stable interface for interacting with runtime events, orchestration layers, execution contexts, or agent lifecycle systems.

• Documentation for extension lifecycle and runtime behavior is still limited for production-level development.
Many runtime behaviors currently require manual testing and reverse engineering to fully understand how the platform works internally.

• A compatibility and migration strategy is urgently needed.
Many AI-first extensions were built before the Antigravity ecosystem existed. Without a proper compatibility layer or migration path, developers may be forced to redesign large parts of their architecture.

This feedback is shared with respect for the engineering effort behind Antigravity.
We believe the platform represents a strong step toward the future of AI-native environments and the Internet of Agents ecosystem.

However, the long-term success of the platform will depend heavily on the strength, openness, and stability of its developer ecosystem.

Areas that could significantly improve developer adoption:

  • Stable runtime APIs

  • Better extension communication protocols

  • Consistent behavior between Desktop App and IDE

  • More detailed runtime documentation

  • Compatibility and migration tooling

  • Stronger communication channels with developers

We remain highly interested in building long-term on top of the Antigravity ecosystem and hope to see continued improvements in the extension developer experience.