GitHub Adds Comment Triggers to Copilot Cloud Agent Automations
Repository teams can launch documentation, error-investigation and follow-up workflows from issue or pull-request comments.
GitHub released comment triggers for Copilot cloud agent automations on August 3. The official changelog says a repository automation can now run when a new issue comment or pull-request comment contains the configured trigger text.
What changed
Repository users configure the comment text that should start an automation. GitHub directs them to the Agents tab and then the Automations section in the repository sidebar. Once configured, a qualifying comment becomes the event that starts the cloud-agent workflow.
GitHub lists three example patterns. A pull-request comment can ask an automation to generate or refresh documentation from code changes. An issue comment can start an investigation of stack traces or error logs. A pull-request comment can also launch a workflow that creates follow-up issues for refactoring or technical debt.
The feature is available to Copilot Pro, Pro+, Max, Business and Enterprise users. On Business and Enterprise accounts, an administrator must enable the Copilot cloud agent policy before users can run these automations.
Why it matters
Comments are already where developers supply context, request changes and record decisions. Making them an automation trigger turns that existing collaboration surface into an operational control point: a maintainer can start a defined agent workflow without leaving the issue or pull request.
The practical value is narrower than a general-purpose command system. Teams choose the trigger text and the automation in advance, which gives the workflow an explicit entry condition. The announcement establishes the trigger and plan availability; teams still need to test each automation against their own repository rules, expected inputs and review practices.
This release is separate from GitHub's earlier controls for reviewing agent changes. Those controls govern how automated issue actions are proposed or approved. The new capability governs when a cloud-agent automation starts. Together, they move repository automation toward a clearer sequence of trigger, work and review.
Status
Confirmed. GitHub documents the release and availability through its official changelog. Internal confidence is medium because the operational details come from one first-party source.
Sources
Update note: Last reviewed 2026-08-05. We will revise this post if GitHub changes trigger configuration, plan availability or administrator requirements.
Sources
Drafted with AI assistance from source briefs; reviewed for citation completeness and label accuracy.