GitHub’s 2026-10-01 Changelog launched Dynamic Workflows in public preview for Copilot CLI, the Copilot app, and the SDK: code-defined reusable orchestration (sequential/parallel steps, pause checkpoints, subagent cross-checks)—unlike Autopilot or /fleet, where Copilot invents the plan each run. CLI needs --experimental or /experimental on; available on all Copilot plans.

Key Takeaways

  • ✓Anchors: Oct 1 Changelog + docs concepts + how-to pages linked above
  • ✓Code defines steps/conditions/handoffs; agents handle judgment. Distinct from Autopilot and /fleet
  • ✓Surfaces: CLI workflow run + /workflows; App Workflows button; SDK/extension canvases; share via personal or repo extensions
  • ✓Limits: max concurrent/total subagents, timeoutSeconds, approx maxAiCredits; prompt > workflow code > personal defaults
  • ✓Public preview; CLI experimental flag; no published agent-bench deltas—don’t conflate with HydraFusion or Computer Use
🧭

Finished reading? Explore benchmark rankings & pricing

Real-world SWE-bench scores & $20/mo vs API cost break-even calculator

🔬

In-Depth Technical Analysis

Core Background & Industry Pain Points

Agentic coding has moved past one-shot edits into multi-step, reusable processes: incident response needs parallel log pulls; PRs need fan-out review; large sweeps need pause/resume. Autopilot and /fleet leave the plan to the model each time—hard to audit or pin in CI. GitHub’s 2026-10-01 Changelog ships Dynamic Workflows in public preview: code fixes the steps and handoffs; agents fill judgment gaps—across CLI, the Copilot app, and the SDK.

Architecture Highlights & Internals

Per the concepts doc, a dynamic workflow is a program that defines how a task runs: sequential/parallel mixes, tools/services, structured returns, subagent cross-checks, and human checkpoints. Implemented as Copilot extensions (session / ~/.copilot/extensions/ / repo .github/extensions/). Trigger via natural language, copilot workflow run NAME, or extension slash/canvas. Docs contrast Autopilot (keep going), /fleet (model divides each time), and dynamic workflow (author-defined process). Subagents inherit session permissions; non-interactive workflow run needs prior --allow-tool grants.

Authoritative Benchmarks & Measured Scores

GitHub publishes no SWE/Terminal-Bench deltas for Dynamic Workflows vs Autopilot//fleet/HydraFusion—do not invent scores. Verified product facts: all Copilot plans; CLI requires experimental mode; limits for concurrent/total subagents, timeoutSeconds, approximate maxAiCredits (prompt overrides workflow code and personal /settings). Do not conflate with same-day Computer Use or HydraFusion in VS Code/App.

Developer Hands-on Guide

  1. Update CLI/App; enable CLI experimental (--experimental or /experimental on).
  2. Ask Copilot to create a named workflow (or request authoring guidance); register then run.
  3. Smoke-test on a tiny scope; monitor via /workflows or the App Workflows button; set credit/timeout limits before large jobs.
  4. Promote to personal or .github/extensions/; for CI use copilot workflow run … --silent --output-format json with auth/permissions pre-granted.
  5. Public preview may change; treat extension code and pre-approved tools as sensitive—trusted sources only.