News
GitHub Agentic Workflows is generally available
GitHub Next’s Agentic Workflows is generally available, turning Markdown agent instructions into GitHub Actions with read-only defaults and threat checks.
Searcher → Analyst → Writer → Editor · subagentic-20261029-0800
GitHub Agentic Workflows is generally available. In its October 28, 2026 changelog, GitHub says the open-source GitHub Next project can now run coding agents inside GitHub Actions for issue triage, CI failure analysis, documentation updates, and test writing.
The same changelog page lists separate October 28 posts for Copilot Fusion and Copilot Automations. This announcement is the agentic-workflows project, not those releases.
Workflows are natural-language Markdown files that compile into standard Actions YAML, so they reuse existing runner groups and policy constraints. Each one can use GitHub Copilot or a coding agent you bring. The project docs name Copilot, Claude Code, Codex, and Antigravity, and they describe importing another engine definition. It is available on github.com for GitHub Free, Team, and Enterprise. The default GitHub Copilot CLI engine requires a Copilot license.
Safeguards are the operational core. Agents read GitHub content under integrity-filter rules, run read-only by default, and execute in a sandboxed container behind the Agent Workflow Firewall. Outputs go through safe outputs, and a threat-detection job scans proposed changes before they are applied. The docs describe six layers: compile-time validation, the sandbox, credential isolation through an API proxy that holds tokens, integrity filtering, threat detection as its own job, and safe outputs that apply only declared writes from a separate job. Generated changes are meant to be reviewed before merging.
Since public preview, GitHub lists Actions Runner Controller and Docker-in-Docker support for self-hosted runners, a non-experimental gh aw forecast that includes threat-detection credits and monthly ranges, a refreshed model inventory, per-workflow model providers, gh aw add-wizard templates, and a model router that optimizes for task type and difficulty. Agents can run in a Cloud Hypervisor or NVX micro-VM, with enclaves meant to prevent data leaks in cross-repository workflows. The docs still mark Cloud Hypervisor and NVX as preview runtimes whose eligibility varies by host; ARC with Docker-in-Docker uses Docker.
The changelog quotes Ben Alton, senior manager on Accenture’s Strategy, Architecture & Innovation team: one lead saved an estimated 29 hours a week, team velocity more than doubled on average, AI authors 91% of that team’s commits, and production errors fell from about 11,000 a day to under 1,000. That is a customer quote in GitHub’s post, not an independent measurement.
The docs also state default cost caps of 1,000 AI credits per run and 5,000 per workflow per day, and that one AI credit is $0.01.
Read the October 28 changelog for the GA scope, then the project docs for engines, the six security layers, and the preview label on micro-VM isolation, before you put a workflow on a production runner.