docs: add gemini-cli deprecation notice (June 18, 2026 cutoff) + migration link - #21
Open
MarcosNahuel wants to merge 1 commit into
Open
docs: add gemini-cli deprecation notice (June 18, 2026 cutoff) + migration link#21MarcosNahuel wants to merge 1 commit into
MarcosNahuel wants to merge 1 commit into
Conversation
…ation link Google announced at I/O 2026 (May 19) that gemini-cli is being replaced by Antigravity CLI (agy). Free-tier and AI Pro/Ultra users stop receiving requests on June 18, 2026 — about 3 weeks from now. Users hitting that cutoff will find their installs silently breaking, with no signal currently in this README that the underlying CLI is being deprecated. This adds a short factual notice with: - The June 18, 2026 date and which user tiers are affected - Which tiers are NOT affected (Gemini Code Assist Enterprise, Vertex AI) - A link to antigravity-plugin-cc as an upstream-compatible migration target No existing docs are removed or weakened. The notice is purely informational so users who Google "gemini-cli deprecated" find guidance instead of being silently broken later. Sources: - https://developers.googleblog.com/an-important-update-transitioning-gemini-cli-to-antigravity-cli/ - https://www.theregister.com/ai-ml/2026/05/20/bye-bye-gemini-cli-google-nudges-devs-toward-antigravity/
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why this PR
Google announced at I/O 2026 (May 19) that
gemini-cliis being replaced by Antigravity CLI (agy), and stops serving requests for AI Pro/Ultra and free-tier users on June 18, 2026 — about 3 weeks from now.Users hitting that cutoff will find their
gemini-plugin-ccinstalls silently breaking. Right now this README has no signal that the underlying CLI is being deprecated, so users will only discover the issue when their workflows stop working.This PR adds:
antigravity-plugin-cc) for users who want to keep their/<provider>:research-style workflow without breakage.The plugin you maintain is excellent and was the direct inspiration for the migration.
antigravity-plugin-ccmirrors its shape (slash-command-per-task, thin forwarder, no companion runtime) on top ofagyinstead ofgemini-cli, with four extras for browser walkthrough recording, structured scraping, multimodal document conversion, and UX design review.What this PR does NOT do
gemini-plugin-ccfor existing users — Gemini Code Assist for Enterprise and Vertex AI authenticated users keep working post-cutoff and this plugin remains useful for them.The notice is purely informational so users who Google "gemini-cli deprecated" land somewhere with guidance instead of being silently broken later.
Diff
One file changed:
README.md— adds a> [!IMPORTANT]callout block right after the H1 title, before the existing intro paragraph. 12 lines added, 0 removed.Sources
Happy to adjust wording, scope, or position of the notice — your call as the maintainer. If you'd prefer a different framing (eg. only call out the cutoff date without naming a specific migration target, or putting the notice at the bottom under a "Future" section), let me know and I'll update.
Thanks for maintaining this plugin — it's been a clean reference implementation.