[Feature]: Support Gemini Integration via Antigravity

[uguraka]

Problem or Use Case

Currently Hermes Agent works flawlessly via Claude Code and Codex. For Gemini, only solution is to use the Google API. I would love to be able to use Gemini Pro subscription via Antigravity

Proposed Solution

Add a new antigravity value to the Supported Providers list. This extension would wrap the google-antigravity Python SDK instead of making direct REST calls.

Key integration requirements:

Credential Reuse: Automatically detect and authenticate using the local Google Antigravity CLI/IDE session tokens (similar to how Hermes handles Claude Code credentials or xai-oauth).

Stateful Session Routing: Map the Hermes agent loop directly to the Antigravity SDK's Conversation and Agent classes. This would allow Hermes to utilize Antigravity's highly optimized context management for Gemini 3.5 Flash/Pro.

Execution Sandbox: Optionally allow Hermes to offload system/shell tool execution into Antigravity's isolated Linux sandbox and leverage its built-in Inspect/Decide/Transform safety hooks.

The antigravity-sdk-python library provides clean programmatic access (from google.antigravity import Agent). Because Hermes is already built to handle complex, non-standard providers like copilot-acp and qwen-oauth, adding an antigravity adapter is the most native way to unlock state-of-the-art Gemini capabilities without forcing users to manage separate API billing quotas.

Alternatives Considered

Continuing to rely solely on the gemini provider. While functional for standard inference, this approach treats Gemini as a generic API endpoint rather than utilizing the robust LocalConnectionStrategy and agent-optimized runtime that Google built specifically for Gemini 3.5.

Feature Type

Configuration option

Scope

Medium (few files, < 300 lines)

Contribution

• I'd like to implement this myself and submit a PR

Debug Report (optional)

[Grut-star]

I actually saw that this is supposedly already done in #50454.
But I also don't understand where it's supposed to be configured.
I'm in the same situation as noobplayer480 in that PR.
There’s nothing suitable when selecting a provider, and it’s completely unclear where else this is supposed to be set up.
Is it definitely done?

Update: Ok. I saw #50492 and the reason it was opened. Now the reason for the absence of antigravity is clear.

[TheToto]

#50492

[CreonHan]

Agree, I don't understand why just cancel the original google-gemini-cli route but still not establish a new route through antigravity-cli for gemini pro subscriber.

[alt-glitch]

This was generated by AI during triage.

Keeping this open as the live feature request. To clarify the current state: #50454 briefly added a native google-antigravity OAuth provider, but #50492 then removed both google-gemini-cli and google-antigravity, so there is currently no Antigravity route on main (verified — only a passing doc reference remains). This is not resolved by those merged PRs; it tracks re-adding an Antigravity provider/route for Gemini Pro subscribers. Related: #50492 (the removal), #44943 / #50338 (earlier requests), #29294 (Gemini CLI sunset).

[alt-glitch]

This was generated by AI during triage.

Verified on main: the native google-antigravity OAuth provider added by #50454 (merged) was then removed by #50492 (merged ~3h later, which dropped both google-gemini-cli and google-antigravity OAuth). main currently has no antigravity provider, so the 'already done in #50454' reading isn't accurate — this ask is still unimplemented. Keeping this open as the feature spec. Related: #50454, #50492, #44943.

[teknium1]

Thanks for documenting the desired Antigravity workflow. This automated hermes-sweeper review is closing this as not planned for the core tree.

• The request is for an in-tree Antigravity LLM-provider integration, which falls under the standing in-tree-provider-integration policy: niche/vendor provider integrations must be standalone plugins rather than bundled core providers.
• Current main intentionally supports Gemini through the API-key gemini provider (plugins/model-providers/gemini/__init__.py:51-59).
• The prior Google Antigravity OAuth implementation was deliberately removed in 7130d60861a9243301514bff611a9381830d59d8 (feat(providers): remove google-gemini-cli + google-antigravity OAuth providers #50492) because reusing those OAuth credentials could expose Google accounts to enforcement and ban risk.
• The retained antigravity-cli optional skill supports invoking the external agy CLI as a worker/reviewer without making it a Hermes inference provider.

A separate plugin implementation is the appropriate integration boundary for third-party provider work, subject to the upstream authentication terms and account-safety constraints.

---

Closed as not-planned per standing maintainer policy (in-tree-provider-integration). This is a design-direction decision, not a code-quality judgment — see the Contribution Rubric in AGENTS.md for what the project is looking for. If you believe this policy was misapplied to your change, comment here and a maintainer will take a look.