Skip to content

[deep-report] Fix Gemini API proxy handler: Smoke Gemini workflow failing with missing proxy handler #26456

@github-actions

Description

@github-actions

Description

Smoke Gemini is failing (#26351), and open community issue #25294 documents the root cause: GEMINI_API_BASE_URL points to the AWF proxy, but the proxy has no Gemini handler. Additionally, issue #25944 reports Gemini API key rejection by the proxy sidecar despite a valid key. The Gemini engine is the rarest in the ecosystem (1/191 workflows use it), making this a targeted fix with low blast radius.

Expected Impact

Restoring the Gemini engine proxy handler unblocks Gemini-based workflow testing and enables the community to use Gemini as an agent engine. The smoke test will serve as a canary for ongoing engine health.

Suggested Agent

Agentic Maintenance — review the AWF proxy configuration, add a Gemini handler that forwards requests to the Gemini API endpoint, and validate with the Smoke Gemini workflow.

Estimated Effort

Medium (1–4 hours)

Data Source

DeepReport Intelligence Briefing — 2026-04-15 (run §24461694592). Source: open issues #26351, #25294, #25944.

Generated by DeepReport - Intelligence Gathering Agent · ● 595.1K ·

  • expires on Apr 17, 2026, 3:10 PM UTC

Metadata

Metadata

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions