Running Hermes Agent on a Google Antigravity subscription, and why Claude kept returning empty turns
I pay for Google Antigravity, and most of my agent work runs through Hermes Agent . I wanted Hermes on that quota without handing a Google token to a proxy or copying Google's OAuth client into someone else's code. The result is a Hermes plugin that treats Google's own agy CLI as the model: npx hermes-antigravity-oauth hermes --provider antigravity-oauth -m claude-sonnet-4-6 The first command…
Using Google Antigravity, I ran Hermes Agent to access Claude's Claude Sonnet 4.6 and Opus 4.6 models through the agy CLI. By treating Google's agy CLI as the model, I used the command npx hermes-antigravity-oauth hermes --provider antigravity-oauth -m claude-sonnet-4-6 to install agy, enable the plugin, and run the Hermes authentication process.
The key challenges I faced were why Claude returned empty turns and why the effort setting caused Hermes to switch providers unexpectedly. The first issue was resolved by modifying the plugin to translate native tool calls into Hermes tool calls instead of aborting them. The second issue was fixed by adjusting the plugin to only send the effort flag for Gemini models, rather than applying it to all models.
Finally, I ensured the persona carried over to subsequent turns by building the system prompt from the SOUL.md file. The Hermes plugin runs agy processes in a separate temp HOME directory to keep OAuth tokens and keychains secure, and it has been tested on macOS, Linux, and Windows.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
