Skip to content

Antigravity engine: CI fails with API key; need documented non-interactive auth path #35818

@dneimke

Description

@dneimke

Problem

On gh-aw v0.76.1, workflows compiled with engine: antigravity fail in GitHub Actions even when ANTIGRAVITY_API_KEY is set to a valid Google AI Studio key (models list works via direct curl to generativelanguage.googleapis.com).

Migrating from deprecated engine: gemini pushes users toward Antigravity, but headless CI cannot complete OAuth/browser login.

Environment

  • gh-aw v0.76.1, ubuntu-latest

Symptoms

Daily Code Improver — agent job exits 1:

  • AWF + Gemini api-proxy start (Gemini=true); 2 allowed requests to generativelanguage.googleapis.com
  • MCP Gateway and safeoutputs OK
  • agy --dangerously-skip-permissions --prompt "..." produces no parseable output
  • Step summary: "Log format not recognized as Antigravity stream-json"
  • No safe outputs / no PR

A Gemini API key validates against the REST API but does not appear sufficient for headless agy in Actions.

Happy to attach run logs and agent artifacts if helpful.

Metadata

Metadata

Assignees

No one assigned

    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