Explanation:
Box 1: Select View session from the pull request
To best confirm the agent's progress, troubleshoot the stagnation, and ensure the work resumes seamlessly from where it left off, you should interact directly with the agent's active workspace.
Open the Session View: Navigate to the pull request on GitHub and click the View session button.
This opens the step-by-step agent workflow and reasoning interface.
Inspect the Logs: Review the detailed execution log in the session timeline to identify exactly where the background task (running in GitHub Actions) stalled or encountered an error.
Steer or Prompt to Resume: Instead of unassigning and reassigning the issue (which completely restarts the task from scratch), use the chat input or steering tools directly inside the View session page or Agents panel to nudge Copilot. Providing a clarification prompt allows the agent to continue its current approach without losing completed steps.
Box 2: Post a pull request comment that mentions @copilot
You can resume the work by commenting on the pull request and mentioning @copilot, along with a prompt instructing it to continue.When a GitHub Copilot coding agent stalls or pauses on a draft pull request, posting a comment mentioning @copilot wakes the agent back up. Because the agent evaluates the entire conversation history, code changes, and task checklists within that pull request lifecycle, it will resume from its last saved state. It maintains the previously chosen approach and carries on with the remaining items without repeating already completed steps.
Reference:
https://docs.github.com/en/copilot/how-tos/use-copilot-agents/cloud-agent/troubleshoot-cloud-agent