---
title: "Octoverse 2026: agents now start over 40% of pull requests"
description: "GitHub's Octoverse 2026 shows how fast agent-written code is growing. What it means for your projects, plus four settings to fix this week."
url: "https://vibe-code.blog/en/octoverse-2026-agents-pull-requests"
lang: "en"
author: "Thierry Gustin"
published: "2026-11-04"
updated: "2026-11-21"
---

# Octoverse 2026: agents now start over 40% of pull requests

> **Key takeaways** — GitHub's Octoverse 2026 report, published October 28, 2026, says agents started more than 40% of pull requests in September 2026, up from 17% in March. Commits reached 34.3 billion over twelve months. For vibe coders, the takeaway is simple: version control, written project rules for your agent and secret blocking are now the baseline.

GitHub's **Octoverse 2026** report, published October 28, 2026, puts numbers on what many vibe coders already feel: in September 2026, AI agents opened more than 40% of pull requests on GitHub, up from 17% in March. The same day, at its Universe conference, GitHub unveiled a [Copilot](https://github.com/features/copilot) app built to direct agents rather than autocomplete lines. Here are the figures that matter and what to do about them in your own projects.

## What does the Octoverse 2026 report say?

Octoverse 2026 describes a year in which GitHub activity grew three- to sixfold, driven by coding agents. It covers October 1, 2025 to September 30, 2026, public and private repositories combined.

| Metric (12 months) | 2025 | 2026 |
| --- | --- | --- |
| Commits | 12.9 billion | 34.3 billion |
| Merged pull requests | 538 million | 1.3 billion |
| Pushes | 6.7 billion | 17.9 billion |
| Agent-started pull requests (monthly share) | 17% in March 2026 | over 40% in September 2026 |

A few details deserve your attention:

- **110 million pull requests** were started by an agent in September 2026, six times March's volume. GitHub calls this a floor, since it only counts agents it can detect.
- **90% of agent pull requests** were merged within two weeks in September, against about 86% for the comparison group.
- Among repositories created in 2026, **those with an agent configuration file** logged roughly eight times as many commits as those without one.
- **TypeScript** is still the top language by monthly contributors. It is the primary language in 35% of repos where an agent was detected, versus 24% of the rest.
- **Push protection**, which blocks API keys and passwords before they land on GitHub, ran 5.8 billion scans, nearly four times the 2025 pace.
- GitHub now serves **more than 225 million developers**, including 38.3 million in the United States.

> **Read the numbers carefully** — GitHub recalculated its 2025 figures under new rules (private repos included, October-to-September year), so they don't match what was published last year. The report also shows activity rising alongside stronger models, but it doesn't prove one caused the other.

## What did GitHub announce at Universe 2026?

On October 28, 2026, GitHub introduced an agent-first **Copilot app** that connects specs, design discussions, telemetry and issue-to-merge work. Jay Parikh, Microsoft's EVP of CoreAI, summed it up in the keynote post: "Completed work, not more code, is the output that matters."

The announcements most useful to a vibe coder:

1. **Copilot Fusion** picks the right model, or combination of models, for each task. You choose an effort level, not a model. According to GitHub's docs, Fusion Standard is included on every plan, Free included, and Fusion is generally available in VS Code, Copilot CLI, the Copilot app, JetBrains IDEs and GitHub.com.
2. **Copilot projects** runs agent work across several repositories in parallel, tracked in one place.
3. **Copilot code review Max** adds a deeper review tier for risky changes.
4. **Copilot automations** runs AI workflows in the cloud, triggered manually, by events or on a schedule.

On billing, the Fusion docs say each model is charged at its standard rate with no Fusion surcharge, and paid plans get 30% off model costs through November 30, 2026.

## Why does this matter if you vibe code?

Octoverse confirms that the vibe coding way of working is now mainstream. When four in ten pull requests start with an agent, the question is no longer "should I use AI?" but "how do I stay in control of what it ships?" If you're new to this, the [complete vibe coding guide](https://vibe-code.blog/en/vibe-coding-complete-guide) covers the basics.

Three signals apply directly to vibe-coded projects.

### Context for your agent makes a difference

The eightfold commit gap between repos with and without an agent config file doesn't prove that an `AGENTS.md` makes you eight times more productive. Busy repos also tend to have organized owners. But it lines up with what many users report publicly: an agent that knows the project rules makes fewer wrong guesses. The method is in CLAUDE.md, AGENTS.md and rules files.

### Code volume is outpacing review

1.3 billion merged pull requests in a year is a lot of code someone has to approve. GitHub says it plainly: "Nothing about all this activity changes who decides what the code should do." For you, that means testing what the agent delivers, even if you're not a developer. See [testing AI-generated code](https://vibe-code.blog/en/testing-ai-generated-code).

### Secret leaks grow with volume

5.8 billion push protection scans reflect a risk that rises with generated code. An API key pasted into a file by a hurried agent is still the most common and most expensive mistake. Reread [why API keys must never live in your front end](https://vibe-code.blog/en/api-keys-security) before your next deploy.

## What to do this week

Four concrete steps, in order:

1. **Put your project under Git and on GitHub** if it isn't already. Without history you can't roll back or use review tools. The walkthrough is in [Git for vibe coders](https://vibe-code.blog/en/git-for-vibe-coders).
2. **Add an `AGENTS.md` file** at the repository root. Here's a starting point:

```markdown
# Project rules
- Stack: Next.js + TypeScript + Supabase
- Never write API keys or passwords in code: use environment variables
- Before every commit: run `npm run build` and `npm test`
- One feature = one branch = one pull request
- Never change RLS policies without asking
```

1. **Check that push protection and secret scanning are on** in your repository's security settings (Settings tab, code security section). It's the safety net that stops a key before it goes public.
2. **If you use Copilot**, try Fusion Standard instead of picking a model by hand, and watch your credit usage before the November 30, 2026 discount ends.

> **The habit to build** — Ask the agent to open a pull request for every change, then read the summary and test the preview before merging. That's exactly the loop Octoverse is measuring.

To compare Copilot with other agents, read our [Cursor vs Claude Code vs Codex comparison](https://vibe-code.blog/en/cursor-vs-claude-code-vs-codex) and the [best vibe coding tools comparison](https://vibe-code.blog/en/best-vibe-coding-tools). And before anything goes live, run through the [vibe coding security checklist](https://vibe-code.blog/en/vibe-coding-security).

## Frequently asked questions

## Frequently asked questions

### What is the Octoverse report?

Octoverse is GitHub's annual report on activity across its platform: commits, pull requests, languages, countries and security. The 2026 edition, published October 28, 2026, covers October 1, 2025 to September 30, 2026 and now centers private repositories alongside public ones. Its main theme is how much software development coding agents now drive.

### Is 40% of the code on GitHub written by AI?

No, that's not what the report says. The "over 40%" figure covers September 2026 pull requests whose first draft was started by an agent GitHub could detect. It doesn't measure the share of lines written by AI. GitHub notes the number is a floor, because some agents can't be detected.

### Should I switch to TypeScript for vibe coding?

You don't have to, but it's a sensible choice. TypeScript is GitHub's most used language in 2026 and dominates repos where agents are active. Types help both you and the agent catch errors before the code runs. Most app builders, such as [Lovable](https://lovable.dev/) and [Bolt](https://bolt.new/), already generate TypeScript by default.

### Is Copilot Fusion free?

Fusion Standard is included on every GitHub Copilot plan, including Free, according to GitHub's documentation. The High and Max levels require higher tiers. Every model Fusion calls is billed at its standard rate, with no Fusion-specific fee. High and Max can use more credits than Standard because they may call several models for one task.

### Is an AGENTS.md file enough to get better results from an agent?

No, but it helps. Octoverse found that 2026 repos with an agent configuration file had about eight times more commits, without proving cause and effect. A good file lists your stack, your test commands and what the agent must never touch, so it doesn't have to guess the rules every session.

## Sources

- [Octoverse: Commits, pushes, reach new highs in 2026 as developers build with agents — GitHub Blog](https://github.blog/news-insights/octoverse/octoverse-commits-pushes-reach-new-highs-in-2026-as-developers-build-with-agents/)
- [GitHub Universe 2026: Evolving every layer of the stack — GitHub Blog](https://github.blog/news-insights/company-news/github-universe-2026-evolving-every-layer-of-the-stack/)
- [Copilot Fusion — GitHub Docs](https://docs.github.com/copilot/concepts/models/copilot-fusion)
- [GitHub : plus de 40 % des pull requests démarrent désormais avec un agent IA — Blog du Modérateur](https://www.blogdumoderateur.com/github-plus-40-pourcent-pull-requests-demarrent-avec-agent-ia/)

— Thierry Gustin, Formateur en intelligence artificielle (GustinAI) · November 21, 2026
