TL;DR — GitHub's Agentic Workflows is now in public preview (June 11, 2026). Write automation rules in a plain Markdown file. GitHub Copilot CLI compiles them into standard Actions YAML. AI agents then run inside GitHub Actions to triage issues, diagnose CI failures, update docs, and more — with read-only defaults and sandboxed execution.

The Core Idea: If You Can Say It, You Can Automate It

GitHub Agentic Workflows is built on a single observation: most repository automation is well-understood in plain English, but translating that understanding into YAML pipelines has always required specialized knowledge. The project removes that translation layer.

Developed by GitHub Next, GitHub, Azure Core, and Microsoft Research, Agentic Workflows lets you write automation logic in a natural language Markdown file. The GitHub Copilot CLI compiles it into standard Actions YAML. Standard GitHub Actions runners execute it. The whole stack reuses your existing runner groups and policy constraints — no new infrastructure required.

The result is that a project maintainer can describe what they want ("triage open issues daily, prioritize bugs, send stale issues to the stale queue, open a PR with the changes") and the system handles everything else.

18+ Pre-built workflow templates available
Read-only Default agent permission mode
100% Reuses existing Actions infrastructure

How It Works

Step 1: Write the Markdown

Create a .md file in your repository. The front matter specifies triggers and permissions; the body is plain natural language describing what you want the agent to do.

---
trigger: schedule(daily)
permissions: read
outputs: pull_request
---
Every day at 8am, review open issues on the main branch.
Relabel issues tagged 'bug' with priority: high.
Add a 'stale' label to any issue inactive for more than 7 days.
Submit changes as a pull request for human review.

Step 2: Compile

Run gh aw compile from the CLI. The Copilot CLI reads your Markdown and generates a standard, version-controllable Actions YAML file. You can review and edit the generated YAML before committing.

Step 3: Run

On trigger, GitHub Actions spins up the agent in a sandboxed container behind the Agent Workflow Firewall. The agent accesses GitHub content through integrity filter rules, proposes changes through the Safe Outputs process, and a dedicated threat detection job scans all proposed changes before they're applied.

💡
Getting Started
Install the CLI extension, then trigger your first workflow in minutes. Browse prebuilt templates on GitHub Next's agentics repository — they cover issue triage, CI doctor, compliance reporting, documentation sync, and more. No personal access token (PAT) required as of the June 11 update.

Security Architecture

Agentic Workflows treats security as a default, not a configuration option.

Layer What It Does
Read-only default permissions Agents can read repository content; write access must be explicitly granted
Sandboxed container Isolated execution; external network access is restricted
Agent Workflow Firewall Only whitelisted API endpoints are accessible
Safe Outputs process Output validation before any changes are applied
Threat detection job Pre-apply scan of all proposed code or content changes
No PAT required Agents authenticate securely without personal access tokens
ℹ️
Real-World Usage
The Home Assistant open-source project is already using Agentic Workflows for issue triage, significantly reducing maintainer burden. The Astro framework team built a "super Dependabot" that automatically opens framework upgrade PRs. Serge, Hugging Face's new AI code reviewer, is also integrating with the GitHub Actions ecosystem to automate pull request review at scale.

What You Can Automate Today

The pre-built workflow library covers the most common repository maintenance pain points:

  • Issue Triage — Auto-label, prioritize, and assign issues by type and age
  • CI Doctor — Diagnose failing CI jobs and propose fixes as PRs
  • Documentation Sync — Keep docs current with code changes
  • Stale Management — Identify and handle inactive issues and PRs
  • Compliance Reporting — Generate audit reports on schedule
  • Dependency Updates — Evaluate and open upgrade PRs for outdated dependencies
Key Takeaways
  • Public preview launched June 11, 2026 — open to all GitHub users
  • Natural language Markdown → standard Actions YAML via Copilot CLI
  • Read-only by default; all proposed changes submitted as pull requests for human review
  • Fully reuses existing GitHub Actions runners, policies, and infrastructure
  • Core use cases: issue triage, CI self-repair, doc updates, compliance reports
🔗
Official Sources & Documentation
— GitHub Actions — Official Overview & Getting Started
— GitHub Copilot — The Engine Behind Agentic Workflows
— GitHub Early Access — Apply for Public Preview