Next.js closed 1,462 issues with a read-only closability agent

The Next.js issue backlog peaked at 3,109 open reports in January 2025 and still had 2,244 on August 10, 2026. On September 4, 2026, the team described closability, built on eve, Vercel's open-source agent framework, with Vercel Sandbox. The agent is research-only: it cannot comment, close, push, or deploy, and it ignores prompt-injection instructions in issue text. It ran on GPT-5.6 Luna, with investigations averaging about 30 minutes and up to 200 concurrent eve sessions.

By September 4, 1,462 issues were closed across the repository, including some outside this review. The reasons were Already fixed 543 (37%), Duplicate 278 (19%), Expected behavior 237 (16%), No longer reproducible 89 (6%), Unsupported or obsolete 66 (5%), and Other 249 (17%). The Maintainer Agent also includes reproduction, verification, e2e_test, and fix agents, and code changes still need human review before merge. Each week, closability researches up to 100 stale open issues, and the team is starting auto-close for the clearest cases (a score of 80 or higher plus a second agent, up to 25 a week) with a reopen window.

The closability review is about the same Next.js codebase you start from in Chapter 1.

Read original: How we closed 1,500 GitHub issues in one month — Next.js

Related in the book: Chapter 1