Turn a well-defined repository issue into a reviewable branch and pull request.
Coding & development · Documented · Documentation checked 2026-10-04
Editor assistance and agents, GitHub cloud agent, and code review have different execution contexts.
Plan, supported IDE, repository permission, AI credits, and organization policy determine access.
The worked example is illustrative and has not been tested in a signed-in product account.
What it does and how it connects
Turn a well-defined repository issue into a reviewable branch and pull request.
The cloud agent can research a repository, plan a change, and create a pull request. It runs in a different context from an IDE agent. Current documentation also provides scheduled / event automations and API entrypoints; those need their own operational controls.
Walkthrough
Use the product named in the access panel. The steps below combine documented controls with the editorial example.
- Confirm repository access, plan eligibility, and organization enablement.
- Create a small well-defined issue or task with acceptance criteria.
- Start the supported cloud-agent session and inspect its work and checks.
- Review the resulting branch / pull request through the normal repository process before merging.
Worked example
Ask for an accessible empty state in a sample search page. The issue should name the trigger, expected text, keyboard behavior, and scope. A pull request is a handoff for review, not a deployed feature.
In this sample repository, add the specified empty-search state. Acceptance criteria: clear explanation, working link to reset search, keyboard access, and no changes to stored content. Run appropriate checks and open a reviewable change. Do not merge or deploy.
Inspect and verify the result
Read the PR diff and test the original trigger. Inspect session logs and checks. Verify no unrelated configuration, dependency, or credential change was introduced.
Limits and troubleshooting
Repository policy, environment setup, and plan access can block tasks. A cloud agent may not reach your local services. Automations need explicit trigger scope, exception routes, and budgets beyond an ordinary one-off issue.
Data, permissions, and actions
Cloud execution receives repository context and configured tool access. Review secrets, network, and external connections. Branch protection and human review should govern merge and publication separately from agent completion.
Related reading
Code review, plans, and AI credits
Check suggested findings against the code and understand the account budget used by agentic features.
An editor fix with a checked handoff
Move from a checked suggestion to a scoped IDE agent change.
From a clear issue to a reviewed pull request
Create a cloud-agent change and a human-reviewed pull-request handoff.
Permissions and meaningful approvals
Decide what a system may read, what it may change, and when someone needs to authorize a concrete action.
Sources and verification
Documentation checked 2026-10-04. Examples are illustrative unless described otherwise.
Copilot cloud agent · GitHub
About GitHub Copilot · GitHub