Repository navigation
Possible deprecation of Gemini and Grok ACP support in upcoming NeverWrite updates #217
Closed
jsgrrchg
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hi everyone,
Maintaining support for multiple ACP implementations in NeverWrite has become increasingly difficult. Different providers support different versions of the Agent Client Protocol, which makes communication with agent runtimes harder to keep stable and consistent. The latest versions of the protocol changed many things around how agent communicate model list, tools, and others, so the migration is not something easy to do, and is the main reason why NeverWrite haven't shipped support for Claude with latest runtime that includes Claude Fable.
Because Google’s current Gemini ACP implementation appears to be stuck on ACP 0.12, with no clear progress toward supporting ACP 0.14, NeverWrite will eventually deprecate the current Gemini ACP integration in an upcoming updates. I will keep a legacy path for it in the meanwhile. Antigravity cli doesn't support ACP yet. google-antigravity/antigravity-cli#31
A similar compatibility issue currently exists with Grok, which also remains on ACP 0.12. At the moment, NeverWrite is maintaining two separate communication paths for agent runtimes, but this adds a lot of complexity and stability issues and is not ideal long term. More details about Grok support will be shared once the migration path is clearer. I'm hopeful that xAI support the newer protocol sooner rather than later.
Sadly, if providers don't update their ACP implementations, I will be forced to deprecating grok and gemini.
Kilo, OpenCode, Claude, and Codex are unaffected by this change, since they already support ACP 0.14.
Thanks for your understanding.
Related PR: #218
All reactions