How to assign GitHub issues to Copilot cloud agent and review the PR
After cloud agent access checks, assign an issue to Copilot on GitHub and review the resulting PR diff, workflows, and follow-up agent iterations.
To delegate backlog work with Copilot cloud agent on GitHub.com, confirm access and repo settings, assign the issue to Copilot, then review the agent pull request, CI, and follow-ups.
Facts follow docs.github.com/en/copilot/concepts/agents/cloud-agent/about-cloud-agent and docs.github.com/en/copilot/how-tos/use-copilot-agents/cloud-agent/use-cloud-agent-on-github. Queries: assign issue to Copilot, Copilot cloud agent review PR. For a short huddle see sitdraw and create and join a room.
Cloud agent vs IDE agent mode
Copilot cloud agent
Runs on GitHub.com; issue assignment always creates a PR and requests your review when finished.
IDE agent mode
Edits locally in your editor—you own commit and push. Different troubleshooting path.
| Stage | You do | First-hour check |
|---|---|---|
| Access | Paid Copilot + org policy; repo not opted out | Copilot appears in Assignees |
| Assign | Assignees → Copilot → optional prompt / repo / branch | PR link on the issue timeline |
| Review | Files changed; Approve and run workflows if needed | Diff matches acceptance criteria |
| Iterate | @copilot on the PR or Fix with Copilot | 👀 reaction + timeline event |
Enable, assign, review
- 01Confirm cloud agent access
Paid Copilot plan; admins enable Business/Enterprise policy; you have write on the target repo and cloud agent is enabled there. See Managing access to GitHub Copilot cloud agent.
- 02Write a actionable issue
Clear acceptance criteria and paths. Copilot reads comments at assignment time only—post updates on the PR instead.
- 03Assign the issue to Copilot
Issue sidebar Assignees → Copilot. Use Optional prompt for tests, style, and off-limits directories; pick target repo and base branch if needed. Feature is public preview in docs.
- 04Review the agent PR
Copilot opens a PR and requests your review. Inspect diffs; Actions do not run by default—click Approve and run workflows after checking
.github/workflows/changes. - 05Iterate on the PR
Comment
@copilot(write access required) or use Fix with Copilot on review threads. Hard 59-minute session timeout—split large tasks.
# Copilot cloud agent on GitHub · 2026-09
# Assignees → Copilot · always opens a PR
# Approve and run workflows before trusting CI
# @copilot on PR for follow-ups · 59 min cap- Same as IDE Copilot agent?
- No—cloud agent runs on GitHub. Compare local agents: Cline in VS Code, Codex CLI.
- New issue comments after assign?
- Copilot does not see them—comment on the PR or mention
@copilot. - Why is CI idle?
- Workflows are not auto-run on agent PRs until you approve; inspect workflow edits first.
- Whiteboard?
- No—open sitdraw for architecture alignment.
Clear issues, strict PR review
Treat agent PRs like any external contributor—protect secrets and branch rules.