Who can trigger Copilot cloud agent to work?
Why D is the answer
Only users with write access to the repository
GitHub limits triggering to users with write access, and comments from others are never shown to the agent.
In detail
- Only users with write access can trigger it.
- That keeps outsiders from starting work in your repository.
- This stops outsiders from starting work in your repository.
Use case
An illustrative scenario, not a real incident.
A public repository gets a comment asking the agent to act. Nothing happens, because only users with write access can trigger it.
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 TD
Q{"Does the user have write access?"}
Q -->|"Yes"| A0["Can trigger the agent"]
Q -->|"No"| A1["Cannot trigger it"]Key point: Triggering needs write access.
Why the other options are wrong
- A. Only enterprise owners
- It is not limited to enterprise owners.
- B. Any user who leaves a comment on an issue
- A comment alone from any user does not trigger it.
- C. Anyone who can view a public repository
- View access is not enough.