Daily · · Copilot · 🌶️🌶️🌶️Act nowSpicy: act now (security, deadline, breaking, big launch) Why: Automate triage and CI with agents
GitHub Agentic Workflows generally available
Your next GitHub Action can start as a Markdown file.
Agentic Workflows went generally available on Oct 28, 2026. Describe issue triage, CI failure analysis, docs updates or test writing in natural-language Markdown, and they compile into standard Actions YAML.
What changed
Agentic Workflows let you describe a CI job in Markdown and run it as GitHub Actions. You don’t have to wire the YAML by hand.
They are available on github.com for every GitHub plan (including the no-cost tier), Team, and Enterprise.
Agents run with read-only permissions by default, inside a sandboxed container behind the Agent Workflow Firewall. Outputs go through a safe-outputs check, and a threat-detection job scans proposed changes before they apply. You can power each workflow with GitHub Copilot or bring your own coding agent.
Using the default GitHub Copilot CLI engine needs a Copilot license.
Concrete start: follow the quickstart to install the CLI extension, or add a prebuilt workflow from GitHub Next’s agentics repository for triage, dependency management, code review or reporting.
Also new for general availability
- Actions Runner Controller and Docker-in-Docker on self-hosted runners
gh aw forecastfor budget ranges (no longer experimental)- Per-workflow model providers, model routing and micro-VM isolation
What to do
Install the CLI extension from the quickstart, then trigger a first workflow. Prefer a ready template from the agentics repository if you want triage or CI analysis today.
Source: GitHub Changelog: GitHub Agentic Workflows generally available, Oct 28, 2026