Author: Nadali. Prepared using AI.
On October 28, 2026, GitHub added optional AI credit limits per run, day, week and month to Copilot Automations. Automations without configured limits continue as before.
Who benefits
Small-business owners whose team or contractor automates website or application work in GitHub. This controls an individual automation’s consumption, not the total cost of every service the company uses.
Two different mechanisms
According to GitHub’s instructions, a per-run limit stops that run when reached; the minimum is 30 AI credits. Daily, weekly and monthly limits prevent new runs but do not stop an already active run.
Periods reset at 00:00 UTC: daily, on Mondays and on the first day of each month, respectively. That is not the team’s local midnight.
Checks to make
Our editorial recommendation:
- Ask the responsible person to list the automations and their owners.
- Agree both a per-run limit and a period limit. An empty field does not mean a zero budget.
- Check who pays: personal automation usage is charged to the user; shared automation usage is charged to the repository owner.
- Decide who will review unfinished work after a stop. Do not treat a spending limit as a substitute for checking changes before release.
Availability and limits
The feature overview lists Pro, Pro+, Max, Business and Enterprise plans, with private and internal repositories where Copilot cloud agent is enabled. Public repositories are not supported; administrator restrictions may also prevent access.
The takeaway: check both levels before the next automatic run. This differs from allowing a server-side app to consume an organization’s credits.
Sources checked October 28, 2026. Nadali has not tested stopping runs or credit charges. The cover is a reused conceptual AI illustration, not GitHub’s interface.
