GitHub opens Copilot cloud agent tasks to REST API automation

GitHub has made a public-preview Agent tasks REST API available for Copilot Pro, Pro+, and Max users, letting developers programmatically start and track Copilot cloud agent tasks.

The company announced the availability in the GitHub Changelog, describing the API as a way to connect Copilot’s cloud agent to custom automation workflows. GitHub’s examples include multi-repository refactors, repository setup, and release preparation.

What the new API does

According to GitHub Docs, the REST API for agent tasks includes endpoints to start and manage Copilot cloud agent tasks. The documented operations include starting a task, listing tasks, and retrieving details for a specific task.

That means teams can invoke Copilot cloud agent work from their own tools rather than relying only on interactive product surfaces. For example, an internal developer platform could start a Copilot task after creating a new repository, or a release checklist tool could trigger a task related to release preparation.

GitHub’s changelog frames the feature as a public preview, so developers should treat the API as newly available rather than a fully mature interface. Public-preview APIs can be useful for early adopters, but teams adopting them in production systems typically need to monitor documentation and behavior for changes.

Who can use it

GitHub Docs states that Copilot cloud agent is available for all paid Copilot plans. The same access-management documentation says the cloud agent is enabled by default for Copilot Pro, Pro+, and Max subscribers.

The changelog specifically names Copilot Pro, Pro+, and Max in the announcement for the Agent tasks REST API. For organizations and enterprise environments, access may also depend on how Copilot cloud agent is configured by administrators, as GitHub’s access-management documentation covers controls for managing availability.

Why it matters for developer workflows

The main change is not that Copilot can perform cloud agent tasks, but that those tasks can now be started and monitored through a REST interface. REST APIs are a common integration point for developer platforms, CI/CD-adjacent tooling, repository management systems, and internal automation services.

For engineering teams, that could make Copilot cloud agent tasks easier to include in repeatable processes. GitHub’s own examples point to tasks that often span more than a single manual prompt: refactoring across multiple repositories, setting up repositories, and preparing releases.

The API also gives developers a more structured way to track task state. GitHub Docs lists endpoints for retrieving task information, which is important for any external system that needs to display progress, handle completion, or decide whether a follow-up action should run.

Limits and open questions

The provided GitHub sources describe availability and core endpoint categories, but they do not establish how widely teams are using the API yet or whether it changes the accuracy, reliability, or autonomy of Copilot cloud agent itself. The announcement should therefore be read as an integration and access update, not as evidence of new agent capabilities beyond what GitHub documents.

Developers evaluating the API should consult GitHub’s REST documentation for authentication requirements, supported operations, request parameters, and current preview behavior. Administrators should also review GitHub’s Copilot cloud agent access-management documentation before enabling broad use in team environments.

For now, the practical takeaway is straightforward: GitHub is giving paid Copilot users a programmatic way to create and observe Copilot cloud agent tasks, making it easier to connect those tasks to custom developer automation.