Products

GitHub Copilot coding agent

3 synchronized stories carry this tag.

GitHub Copilot coding-agent runner routing changes take effect

GitHub moved self-hosted and Azure-private Copilot coding-agent traffic to plan-specific hostnames, so missing firewall allowlists could prevent tasks from reaching required services.

Why it matters: Private runners are often intentionally isolated; a hostname change can make agent jobs fail even when repository configuration and runner health appear unchanged.

Read storyOriginal source · github.blog

GitHub Copilot coding agent reaches general availability

GitHub made its asynchronous coding agent generally available for paid Copilot plans. Developers can delegate issues, review session logs and proposed changes, and require normal pull-request checks before merge.

Why it matters: Repository-native delegation moved from preview into a supported workflow, making governance, review and CI—not chat quality—the practical adoption boundary.

Read storyOriginal source · github.blog

Cursor and GitHub move coding agents into remote background work

Cursor began gradually previewing Background Agent on May 15 with parallel remote environments, status checks, follow-ups, and takeover. On May 19, GitHub put Copilot coding agent into public preview, letting users assign issues that produced tested draft pull requests in a GitHub Actions environment.

Why it matters: Coding assistance became asynchronous delegation: the unit of value shifted from an inline suggestion to a reviewable pull request created while the developer did other work.

Read storyOriginal source · cursor.com