feat: implement ACP for Gemini and migrate to new logic #445
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.
Enable ACP (Agent Communication Protocol) support for Gemini by leveraging the native
--experimental-acpflag in the Gemini CLI. This continues the ACP migration by adding Gemini alongside Claude as an ACP-enabled tool.Related: #405
Changes
runcommandgetACPSpawnCommand()case for Gemini using the native--experimental-acpflagrecoverFromError()method fromGeminiAgentas ACP handles error recovery differentlycontainsGeminiYoloWarning()utility and its associated tests (no longer needed with ACP mode)--passWithNoTestsflag since agent tests were removedNotes
The Gemini CLI natively supports ACP via the
--experimental-acpflag, unlike Claude which requires the@zed-industries/claude-code-acppackage. This simplifies the Gemini integration significantly.