Next.js Maintainer Agent
Next.js
Independent agents the Next.js maintainers use to research, reproduce, verify and fix GitHub issues; they helped cut the backlog by 1,462 closed issues in about three weeks.
Use case
Teams whose listed work includes fixing bugs, debugging or resolving reported issues.
2 operated · 11 reference designs
A team is listed when its task kinds include bug-fixing, github-issue-resolution or distributed-debugging.
Operated teams first (real, then curated), then reference designs, then illustrative demos. Every card is labeled.
Rob Hunter
A product-manager agent and a coder agent, built from the author's own Bobbo agent code, that take turns running his MCP deals server.
Listed for: task kind github-issue-resolution
OpenAutoCoder
Non-agentic 3-stage pipeline — 40.7% Lite / 50.8% Verified with Claude 3.5 Sonnet.
Listed for: task kind github-issue-resolution
Anthropic
Swarm teammates sharing a task list — parallel exploration on a single codebase.
Listed for: task kind distributed-debugging
Huawei Cloud + CAS + SMU + PKU (CodeR)
5-agent supervised pipeline — 28.33% SWE-bench Lite, $3.09/issue.
Listed for: task kind github-issue-resolution
ByteDance SE Lab
39.33% on SWE-bench Lite (lab-page claim).
Listed for: task kind github-issue-resolution
Princeton NLP / SWE-bench authors
Minimal bash-only agent — reference floor on SWE-bench Verified.
Listed for: task kind github-issue-resolution
From 36 listed members of the 13 real and curated teams above. Illustrative demo teams are not counted.