Context
With the recent release of google-antigravity/antigravity-sdk-python and the broader Antigravity ecosystem (including the Antigravity Runtime binary, CLI, and Agent Harness), I noticed a significant functional overlap between the Google Agent Development Kit (ADK) and this new SDK.
Questions for the Maintainers
What is the long-term relationship between Google ADK and Antigravity SDK?
Will ADK be deprecated/merged into the Antigravity ecosystem, or will it evolve into a lightweight, high-level abstraction wrapper on top of the Antigravity Runtime?
For developers currently building local or personal agents using ADK, is it recommended to migrate our architecture to google-antigravity/antigravity-sdk-python to align with Google's future technical direction?
Context
With the recent release of google-antigravity/antigravity-sdk-python and the broader Antigravity ecosystem (including the Antigravity Runtime binary, CLI, and Agent Harness), I noticed a significant functional overlap between the Google Agent Development Kit (ADK) and this new SDK.
Questions for the Maintainers
What is the long-term relationship between Google ADK and Antigravity SDK?
Will ADK be deprecated/merged into the Antigravity ecosystem, or will it evolve into a lightweight, high-level abstraction wrapper on top of the Antigravity Runtime?
For developers currently building local or personal agents using ADK, is it recommended to migrate our architecture to google-antigravity/antigravity-sdk-python to align with Google's future technical direction?