How Next.js closed 1,500 GitHub issues in one month with a closability agent
cramforce · x · 2026-09-05
The Next.js team details how an issue-research agent cleared its massive backlog:
- The tracker receives 36 new reports weekly; the backlog peaked at 3,109 open issues in January 2025 and still held 2,244 by August 10, 2026, with stale reports burying current regressions.
- Using @eve, the team built a closability agent that: 1) searches related prior work, 2) attempts to reproduce bugs across versions in a sandbox, 3) returns context for maintainers to review before closing.
- In roughly three weeks they closed 1,462 issues (including some closed outside the process), dropping the backlog to 995 even as 218 new reports arrived.
- An earlier staleness policy (marking issues stale after 18 months of inactivity) alone couldn't separate still-relevant old reports from dead ones.
Related event: Next.js closes 1,500 GitHub issues in a month with closability agent(2 posts)→
More from coding & agent
- Memory poisoning on a delay: one bad fact in agent memory seeds every future decision — sierracatalina · 2026-09-05
- Long-running agents aren't in prod because trust infrastructure doesn't exist yet — Arm1end · 2026-09-05
- Running production agents on sandboxed CLIs: lessons from iterating on agent-facing interfaces — nguyenfamjj · 2026-09-05
- ngrok ships GOPHRS, declares AI gateway migration mandatory with final architecture — anthara_ai · 2026-09-05
- Security vet: agentic swarms are emergent, and the OpenAI-HuggingFace hack is far from understood — WeldPond · 2026-09-05
- Leaked logs show OpenAI-labeled agents probing sandbox survival with beacon experiments — Hesamation · 2026-09-05