GitHub Copilot · Coding agents and development assistant
Product and access
GitHub Copilot includes several interfaces. This profile focuses on the GitHub Copilot Cloud Agent; IDE agent mode, CLI, Code Review, and the Copilot app are related, separate features.
Core features
7 features from provider sources · sources reviewed on 30 September 2026. Availability and limitations are listed directly below.
Explore the repository and plan
Cloud Agent can research a repository, create an implementation plan, and edit code.
Source 1Isolated development environment
The GitHub Actions environment enables code exploration, changes, and automated checks.
Source 1Branch and pull request
Work takes place on a branch; a pull request can be created directly or after iteration.
Source 1Specialized custom agents
Custom agent profiles can specialize tasks, instructions, and tools.
Source 3Hooks and skills
Hooks run commands at defined points; skills bundle instructions, scripts, and resources.
Source 1
Requirements and limits
‘Still open’ means the reviewed sources do not answer this point clearly.
Requirement
Paid Copilot plan
Cloud Agent is available for paid Copilot plans; Business and Enterprise organizations also require administrator approval.
Source 1Requirement
GitHub repository required
Cloud Agent works in a GitHub-hosted repository; managed user accounts and disabled repositories are excluded.
Source 1Limitation
One repository and branch boundary
A session modifies only the repository it starts with and works on a branch; one pull request is intended per task.
Source 1Limitation
Runtime and usage
A session can run for up to 59 minutes and uses GitHub Actions minutes and AI credits.
Source 1Limitation
Workflows with review
GitHub Actions workflows for agent pull requests start only after approval by a person with write access.
Source 4
Practical tasks
Editorial examples based on documented features. No product tests performed.
Handle a small issue
- Your input
- Clearly described GitHub issue, repository, and project instructions
- Possible result
- Cloud Agent creates a branch with the change and an optional pull request.
- What to check
- Check the diff, verification logs, and acceptance criteria in the pull request.
Research a repository change
- Your input
- Repository question and clearly limited investigation goal
- Possible result
- Agent creates a traceable analysis and can then propose a plan.
- What to check
- Open evidence in the repository itself; check Plan Mode availability for each entry point.
Handle a clearly described issue and prepare a reviewable pull request.
Your possible prompt
Read the project rules. Investigate [error], propose a small change, and run the relevant checks. Show me the diff and any remaining uncertainties.
Getting-started idea based on documented capabilities. Not an executed product test. Adapt the task, data, and permissions.
What you should know first
GitHub Docs reviewed. Cloud Agent requires GitHub-hosted repositories and a paid Copilot plan; Business and Enterprise accounts require suitable administrator settings. Cloud Agent, IDE agent mode, and the Copilot app are clearly separate interfaces.
Requirements & limitations
Review code, tests, and changes. Specific access depends on the environment, plan, and project configuration.
Setup
Configure repository and access.
Pricing model
Plan + AI credits / actions. Check current terms and included quotas with the provider.
The classification indicates the scope of effort. It is not a price or performance commitment.
Sources from the provider
Editorial team: Michael Meierhoff · sources reviewed on . Provider information is not independent evidence of performance.
-
docs.github.com /en/copilot/concepts/agents/cloud-agent/about-cloud-agent
-
docs.github.com /en/copilot/concepts/agents
-
docs.github.com /en/copilot/concepts/agents/cloud-agent/agent-management
-
docs.github.com /en/copilot/concepts/security-governance-and-network-settings/risks-and-mitigations