GitHub Copilot Automations Schedule Agent Work

This moves coding agents from on-demand assistants toward persistent repository operators, but unattended execution makes permissions, cost, and prompt design operational concerns.

• –Scheduled agents can handle recurring maintenance such as issue triage, nightly test repair, and release-note drafting.
• –Tool-level permissions let teams limit whether an automation can push code, modify issues, or create pull requests.
• –Automations are scoped to one repository and currently require private or internal repositories, limiting public open-source use.
• –Each run consumes GitHub Actions minutes and AI Credits, so high-frequency schedules can become an infrastructure expense.
• –GitHub’s protections against untrusted issue and pull-request inputs are important because agent-triggered workflows expand the prompt-injection attack surface.