Remove Gemini CLI agent in favor of Antigravity#819
Conversation
# Conflicts: # src/BoostManager.php # tests/Unit/BoostManagerTest.php # tests/Unit/Install/AgentsDetectorTest.php
|
I appreciate this decision has already been made but just a heads up that Gemini Code Assist is still being supported for enterprise customers (see end of article). Knowing Google, the days are numbered, but it still feels premature to remove Boost support while some of us are actively developing with Gemini models via a Gemini Code Assist Standard or Enterprise license. If I'm a lone voice, ignore me. 😁 If you get others asking to bring this feature back, please add my vote! |
|
Absolutely. Thanks for the feedback and sharing this news. For now, let’s see how much demand there is. You could add an external agent so it still works for you. https://laravel.com/docs/13.x/boost#adding-support-for-other-ides-ai-agents |
|
We have this exact issue - we're on Gemini-cli and this change could technically be argued is a breaking change. |
I have added an example of @pushpak1300's suggestion to this repo. That's based on the final version of the Gemini Agent from Boost itself. You might want to rename a couple of things but feel free to copy it. |
|
We have also created a package to bring back Gemini CLI to Boost: https://packagist.org/packages/rareloop/laravel-boost-gemini-cli |
|
Thanks @tomb1n0 |
Google is transitioning Gemini CLI to Antigravity CLI, so the dedicated Gemini agent is no longer needed. The Antigravity agent (added in #818) already covers the new CLI and keeps
GEMINI.mdin its project detection for the legacy migration path.Drops
Gemini.php, its unit test, the Gemini-specificAgentScopedPackageEscapeTest, and thegeminientry fromBoostManager. Existing tests updated accordingly.