Next.js

org

@nextjs

Follow

Profile curated from public sources; not claimed by this operator. AgentCV documented it from the operator's own public posts. The operator can claim it or ask for its removal.

7 agent components·1 proof entry·1 evidence-linked·1 team (of 109 on the registry)

This owner profile was curated from cited public sources and has not been claimed by the organization. Data reflects what is publicly documented.

Sign in to claim this profile if it belongs to you.

Agent components (7)

Individual agents that make up this owner's teams. Each card shows model, platform, metrics, and proof count.

View all agents →
🤖

Chat agent

Next.js

Self-Reported

Answers maintainers' questions about a particular issue or pull request and can inspect source code or launch an investigation.

Dashboard chat agentCustom
Evidence0 proof
configs1
🤖

closability

Next.js

Self-Reported

Investigates each issue in a clean sandbox that holds the Next.js code plus Node.js, Chromium and Playwright, then scores how confidently it could be closed.

Issue research agentCustomGPT-5.6 Luna
Evidence0 proof
configs1
🤖

e2e_test

Next.js

Self-Reported

Writes end-to-end tests for issues.

End-to-end test agentCustom
Evidence0 proof
configs1
🤖

fix

Next.js

Self-Reported

Prepares fixes; no code change is merged without a human reviewing it.

Fix agentCustom
Evidence0 proof
configs1
🤖

reproduction

Next.js

Self-Reported

Reproduces reported bugs.

Reproduction agentCustom
Evidence0 proof
configs1
🤖

Second-opinion agent

Next.js

Self-Reported

For issues scored 80 or above, searches for reasons the issue should stay open; if it also recommends closing, it picks the reason and writes the closing comment.

Counter-evidence reviewerCustom
Evidence0 proof
configs1
🤖

verification

Next.js

Self-Reported

Checks issues against the canary release.

Verification agentCustom
Evidence0 proof
configs1

Teams (1)

1 team · one of 109 on the registry — browse all

Agent harnesses published by this owner — topology, roster, and evidence.

🕸

Next.js Maintainer Agent

Next.js

Self-ReportedCurated

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.

updated 1mo ago
Orchestrator–Worker7 listed membersCustom
Issue research agent· GPT-5.6 LunaReproduction agentVerification agentEnd-to-end test agent+3 more
software-delivery
Outcome[unknown]
Economics[unknown] · deliberate
1 proof

Activity

Versions, proof, attestations, and new subjects across Next.js's agents and teams.

  1. Second-opinion agent joined as an agent — Counter-evidence reviewer
    12d agocurated
  2. Chat agent joined as an agent — Dashboard chat agent
    12d agocurated
  3. fix joined as an agent — Fix agent
    12d agocurated
  4. e2e_test joined as an agent — End-to-end test agent
    12d agocurated
  5. verification joined as an agent — Verification agent
    12d agocurated
  6. reproduction joined as an agent — Reproduction agent
    12d agocurated
  7. closability joined as an agent — Issue research agent
    12d agocurated
  8. New team Next.js Maintainer Agent — orchestrator worker
    12d agocurated
  9. Next.js Maintainer Agent logged a artifact: How we closed 1,500 GitHub issues in one month
    1mo agocurated

Proof feed

Recent proof entries across all agents and teams. 1 total.

⚙ Next.js Maintainer AgentArtifactevidenceSep 4, 2026

How we closed 1,500 GitHub issues in one month

Public source cited for this curated profile. Published 2026-09-04; accessed by AgentCV 2026-10-20. Lesson stated in this source: Closing issues on inactivity alone proved unreliable, because an old report's age says little about whether it still matters, so the team switched to researching each issue.

Owners on the registry

101 registered operators — click to view their profiles

Anthropic5 teamsAcademic / Open-Source (ChatDev & MetaGPT)2 teamsPrinceton NLP / SWE-bench authors2 teamsShopify2 teamsSpotify2 teamsAider (Paul Gauthier)1 teamAlexey Grigorev1 teamAlireza Rezvani1 teamAll Hands AI (OpenHands)1 teamAllie (AI with ALLIE)1 teamAmazon / AWS1 teamAndon Labs1 teamAnt Group (inclusionAI)1 teamAntonio Leiva1 teamAntonio Sabbatella (MALBO master's thesis, University of Milano-Bicocca)1 teamAtlassian1 teamAtum1 teamBertelsmann1 teamButterfly Effect / Monica (Manus)1 teamByteDance SE Lab1 teamCAMEL-AI (King Abdullah University of Science and Technology)1 teamClaire Vo1 teamCloudflare1 teamco-evolve-lab1 teamCognition1 teamCrewAI1 teamCursor1 teamDana Kraft1 teamDrew Burdick1 teamDupple1 teamExa1 teamFactory AI1 teamFastweb + Vodafone1 teamFutureHouse1 teamGitHub Next1 teamGoogle Research1 teamGrab1 teamH2O.ai1 teamHAMY1 teamHebbia1 teamHelios Labs1 teamHKUDS1 teamHuawei Cloud + CAS + SMU + PKU (CodeR)1 teamHubSpot1 teamHugging Face1 teamHyuk Jun Kim1 teamIain MacKenzie1 teamIberdrola1 teamimkisyou1 teamIntronode1 teamJD.com (JDGenie)1 teamJenny Ouyang1 teamKensho1 teamKlarna1 teamLinkedIn1 teamLinkedIn1 teamLuke Lin1 teamMainFunc (Genspark)1 teamMATKARIM MATKARIMOV1 teamMete Polat1 teamMichael Light1 teamMicrosoft Research1 teamMicrosoft Research (AutoGen)1 teamMinimal1 teamMira Systems1 teamMoe Lueker1 teammonday.com1 teamNext.js1 teamNexus Content Co.1 teamNicholas De Leon1 teamNVIDIA Research (Voyager)1 teamOleh Veheria1 teamOpenAI1 teamOpenAutoCoder1 teamPagerDuty1 teamPanasonic Avionics Corporation1 teamPark et al. — Stanford University, with Google Research and Google DeepMind1 teamPGA TOUR1 teamRazorpay1 teamRedazione Zero1 teamRefact.ai1 teamReplit1 teamRob Hunter1 teamSakana AI1 teamSalesforce1 teamSamuel Schmidgall1 teamSend Payments1 teamShopStream1 teamShubham Saboo1 teamStewart Media1 teamThanh Pham1 teamThomson Reuters1 teamTsinghua / BUPT / Tencent WeChat AI — OpenBMB (AgentVerse)1 teamUber1 teamUber (Developer Platform team)1 teamUniversity of Transport Technology1 teamWEBTOON Entertainment1 teamWix1 teamWyndo1 teamZembl1 teamzou-group1 team