Organization runner controls for Copilot cloud agent - GitHub Changelog

Fri, Apr 3 · 8:11 PM UTC 2 min read

Compiled by KHAO Editorial — aggregated from 2 outlets. See llms.txt for citation guidance.

✓ KHAO Verified

Image accompanies the article at GitHub Blog. No description was extracted from the source.

Each time Copilot cloud agent works on a task, it starts a new development environment powered by GitHub Actions.

Key facts

Each time Copilot cloud agent works on a task, it starts a new development environment powered by GitHub Actions
Until now, the runner was configured at the repository level with a copilot-setup-steps.yml file
To learn more, see “Configuring runners for GitHub Copilot cloud agent in your organization” in the GitHub Docs

Summary

By default, this runs on a standard GitHub-hosted runner, but teams can also customize the agent environment to use large runners or self-hosted runners for faster performance, access to internal resources, and more. Until now, the runner was configured at the repository level with a copilot-setup-steps.yml file. Set a default runner to be used automatically across all repositories, without requiring each repository to be individually configured. Lock the runner setting so individual repositories can’t override the organization default.

#AI Agent