While the agentic shift has made development faster, it’s also led to disjointed workflows, more context switching, and too much time spent reviewing agent-generated code.
If agents are going to be a durable part of how software gets built, they need a real place in the developer workflow. Yet most developer tools were not designed for directing multiple agents in parallel. Context scatters across windows. You lose track of what’s running. Code lands in pull requests without a clear trail of what the agent tried, what it validated, or where human judgment is needed.
Get started with the GitHub Copilot app today using your existing Copilot Pro, Pro+, Business, or Enterprise plan. Learn more >
Across GitHub, developers are using agents to move from prompt to plan, from issue to pull request, from review feedback to merged code. As agentic workflows become the norm, repository creation, pull request activity, and API usage are all accelerating with no evidence of slowing down. On GitHub alone, commits nearly doubled year over year, crossing 1.4 billion per month, plus over 2 billion GitHub Actions minutes a week.
To meet this demand and continue to be the home for all developers (and now their agents), our focus is scaling our underlying systems and improving resilience and stability across all of our services, at every layer of the stack.
