How many branches can Copilot cloud agent push to in a task?
Why D is the answer
A single branch
It pushes to one branch: the pull request's branch, or a new copilot/ branch. Branch protections still apply.
In detail
- It can push to a single branch.
- That limits the effect of any mistake.
- A single branch keeps the effect of a mistake small.
Use case
An illustrative scenario, not a real incident.
A cloud agent task pushes to a single branch, so its work is contained in one reviewable place.
See it in different ways
flowchart TD A["Cloud agent"] --> B["Pushes to a single branch"] A --> C["Cannot approve or merge"] A --> D["Workflows wait for approval"] A --> E["Internet access limited by a firewall"]
mindmap
root((Agent limits))
Identity
Write access to trigger
Repository
One branch
Branch protection
Tools
MCP allow list
Tool permissions
Network
Firewall allowlistflowchart LR S0["Task"] --> S1["One working branch"] --> S2["Pull request"] --> S3["Review"]
Key point: The agent pushes to a single branch.
Why the other options are wrong
- A. Any branch in the repository
- It cannot push anywhere it likes.
- B. Every branch whose name starts with feature
- A name prefix does not widen its access.
- C. All of the protected branches only
- It does not push to protected branches.