AIToday
AI Coding AssistantsOpen-Source AIAI Business & IndustryLatent SpacePublished: Sep 2, 2026, 04:01 JST2 min read

Top AI open source projects shutting off PRs

Top AI open source projects shutting off PRs

Key takeaway

  • Top AI open source projects are closing PRs and using their own agents.

  • Vercel's AI SDK cuts backlog significantly this way.

  • The trend shifts community roles from code contribution to reporting and discussion.

3 Key Points

  1. What happened

    Top AI-native open source projects like Flue and tldraw are refusing external pull requests, often because they are AI-generated. Maintainers prefer using their own agents to create and manage PRs.

  2. Why it matters

    Vercel's AI SDK, with over 20 million npm downloads per week, deployed a 'software factory' of agents to clear a backlog of over 1,000 open issues and almost 800 pull requests by late June. Four weeks later, Vercel says the factory authors 25–35% of merged PRs and closes 70–80% of issues.

  3. What to watch

    Astro creator Fred Schott says the 'auto-triage' system shifted control in the last six months and led to his new framework Flue. Flue and tldraw now convert every external PR into an issue or discussion rather than accept the code.

Ask the AI about this article →

Context & Analysis

The shift described here is a response to the scale of community contributions in AI-era open source. Astro's Fred Schott notes that for five years issues came in faster than they could handle them, but with agents handling triage they have reestablished control. Vercel's system similarly targets a specific pain point: a backlog of over 1,000 open issues and almost 800 pull requests.

The underlying motivation is trust. Vercel engineer Lars Grammel says the company trusts its own optimised agents more than community-run ones, because historical success on a category of bugs builds confidence in a configuration. This reduces review time. Mitchell Hashimoto goes further, predicting large open source projects will close contributions completely.

The open question is community involvement. Traditional PR review also mentored contributors and assessed future maintainers. Schott admits this narrowing leaves a hole if maintainers go on vacation. The article suggests a possible answer: by redirecting contributors to issues and discussions, community members still engage, learn from peers, and can prove themselves worthy of being a maintainer, while code work stays with trusted agents.

FAQ

Why are these projects refusing external pull requests?
Maintainers say external PRs are usually AI-generated and less trusted. They prefer using their own optimized agents to create and manage PRs instead.
What happens if I submit a PR to Flue or tldraw?
For Flue, external PRs are automatically closed and turned into issues or discussions. Bug reports become issues, feature requests become discussions. tldraw similarly auto-closes external PRs.
What is a 'software factory' in this context?
It is a team of agents that triage a PR, reproduce a bug, implement a fix or feature, review it, and then hand it back to a human to merge. Vercel and Astro use this system.

Get the latest AI Coding Assistants news every morning

For example, today's edition would include:

  • John Ternus takes over as Apple CEO, faces AI eraSemafor Tech · 1h ago
  • VS Code's 'Rubber Duck' feature lets developers get a second AI opinionPublickey · 4h ago
  • Claude Code to permanently raise usage limits by 25%Ben's Bites · 4h ago

AI-summarized, only the topics you pick — one digest a day via Email, Slack, or Discord.

Free · takes 30 seconds · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. Q&As are published on this page for other readers too.

Related Articles

Next articlePhysical AI takes center stage at RoboBusiness 2026