Text of github.github.com › gh-aw › engines › gemini as Styx crawled it on Nov 19, 2026. The page may have changed since. Only its words are kept, without pictures or layout.

Open the live page

Using Gemini CLI with GitHub Agentic Workflows | GitHub Agentic Workflows

Skip to main content Using Gemini CLI with GitHub Agentic Workflows Run Gemini CLI workflows with a Gemini API key or Google Workload Identity Federation (WIF). Connect your account Section titled “Connect your account” Set engine: gemini and add a GEMINI_API_KEY repository secret, or configure Google WIF . The example grants Copilot access for safe-output threat detection, which uses Copilot rather than Gemini. Supply Copilot authentication or configure a different detection engine .

Run a daily report Section titled “Run a daily report” After setting up gh-aw , save this workflow: .github/workflows/daily-status.md --- on : workflow_dispatch : schedule : daily permissions : contents : read issues : read pull-requests : read copilot-requests : write engine : gemini tools : github : toolsets : [ issues , pull_requests ] safe-outputs : create-issue : title-prefix : " [status] " --- # Daily repository status Summarize open issues and recent pull request activity in one concise issue.

Compile with gh aw compile daily-status , then commit and push both the Markdown and generated lock file. Run it from the repository’s Actions tab or wait for its schedule. Capabilities and limitations Section titled “Capabilities and limitations” Gemini supports command-level shell restrictions, but not native web search; use an MCP search server . See the Gemini reference for configuration and limitations. Next steps Section titled “Next steps” Gemini CLI technical reference Create a workflow Workflow examples Compare engines