[Feature]: Migrate Bundled Google Code CLI From Gemini CLI to Antigravity CLI

[kennyzheng-builds]

Background

Cherry Studio bundles the Gemini CLI so users can drive Google models through a built-in code agent. Google is retiring Gemini CLI access for Google One and unpaid tiers and is steering users to the new Antigravity CLI. Users on free/Google One tiers will find the bundled Gemini CLI stops serving requests, breaking that workflow inside Cherry Studio.

Goal

Users can continue using Google's code CLI from within Cherry Studio after the Gemini CLI deprecation, by migrating the integration to Antigravity CLI.

Spec

• The built-in Google code CLI integration uses Antigravity CLI as its backing tool instead of (or in addition to) the deprecated Gemini CLI.
• Authentication and account selection work with Antigravity CLI, including free/Google One tier accounts that Gemini CLI no longer serves.
• Existing users whose configuration referenced the Gemini CLI are transitioned without manual reinstallation or a broken state.
• If both CLIs remain available for a transition period, the user can see which backend is active and the default points to the supported one.

Verification

• A user on a free/Google One Google account can authenticate and run a code task through the Google CLI integration and receive a successful response (where Gemini CLI would now refuse).
• After upgrading from a version that used Gemini CLI, the Google CLI integration is functional on first launch without the user reinstalling or reconfiguring it.
• Launching a code task shows the request being served by Antigravity CLI, not the deprecated Gemini CLI.
• A user with no Google account configured is prompted to authenticate rather than hitting a silent failure.

Related

#16136