Consider clarifying Gemini/Antigravity routing in agent guidance

[cbusillo]

Objective

Tentative request: when revisiting agent routing, model-role defaults, and multi-agent diversity, consider making the Gemini/Google path more explicit in Every Code's model-selector guidance and agent prose.

This came up during a memory-cleanup session: the user asked to "ask agents" for multiple viewpoints, and the controller selected OpenAI and Claude agents but skipped antigravity. The likely cause was not a capability decision; it was naming/prose friction. The selector does not expose a model literally named gemini, and antigravity only reads as the Google/Gemini-family path if the agent remembers the mapping.

Current Status

State: Waiting
Next action: Revisit together with adjacent agent/model-routing issues rather than implementing in isolation.
Blocked by: No native issue blocker.
Waiting for: Broader routing/defaults pass across model selector guidance, agent batch diversity, and Antigravity support.
Last verified: 2026-05-30 during local agent delegation; nearby issues found: #48, #134, #212.

Related Work

• Audit hard-coded model roles and agent routing defaults #48 Audit hard-coded model roles and agent routing defaults
• Track Antigravity SDK support for model-specific agents #134 Track Antigravity SDK support for model-specific agents
• Define natural agent delegation policy #212 Idea: improve agent batch diversity and dissent prompts

Tentative Direction

Consider updating Every Code's instructions/model-selector prose along these lines:

• Make clear that antigravity is the current Google/Gemini-family agent path.
• If a user asks for Gemini or a Google perspective, route that request to antigravity unless unavailable.
• When a user asks for multiple viewpoints, cross-model review, or to "ask agents," prefer a diverse set that includes OpenAI, Claude, and Google/Antigravity when task fit and latency permit.
• If the controller intentionally skips a major model family during a diversity request, briefly state why.

This may belong in the agent/model selector guide, examples, or future automatic agent-pool defaults rather than only in prompt prose.

Acceptance Criteria

• The documented model selector guide makes the Gemini/Google -> antigravity mapping obvious.
• Multi-agent examples or defaults make it natural to include antigravity for diverse viewpoint requests.
• Guidance avoids forcing Antigravity into every task; it should be a default consideration for diversity, not a hard rule.
• Any implementation aligns with Audit hard-coded model roles and agent routing defaults #48, Track Antigravity SDK support for model-specific agents #134, and Define natural agent delegation policy #212 so model-routing behavior is coherent rather than patched in one place.

Notes

This is intentionally tentative. The point is to preserve the observed friction and user expectation while leaving room for the broader agent-routing design to choose the right product shape.

[shiny-code-bot]

Completed by PR #265: Gemini/Google intent selectors now resolve to antigravity, the model-visible agent guide names Antigravity as the Google/Gemini-family lane for diverse multi-agent requests, and docs clarify that AGY uses its configured model rather than per-run Gemini Pro/Flash flags. The broader natural-agent selection policy remains tracked in #212.