Augmentation with Dilution? A Large-Scale Empirical Study of Human Contributor Ecosystems After AI Coding Agent Adoption

summary

The gist

AI coding agents are not displacing human contributors, but are systematically reshaping the participation structure of opensource ecosystems <ref:2606.26289#pg2> Using a staggered…

In short

The study used a difference-in-differences design across 11,097 GitHub repositories to see how AI coding agent adoption impacts human contributors. Findings show AI does not reduce absolute human numbers but decreases contributor density and the share of newcomers. This suggests an 'augmentation with dilution' effect where AI handles more work, shrinking the relative opportunities for new contributors.

Key concepts

Human Contributor Density
This measures how many human developers are contributing relative to the number of pull requests in a project. A decrease in this density means that as AI generates more code, the human contribution becomes less frequent compared to the total output.
Newcomer Relative Share
This tracks what proportion of contributions comes from new contributors. The study found this share drops significantly after AI adoption, indicating that newcomers are less likely to participate relative to established developers.
Augmentation with Dilution
This is the core finding: AI agents augment (help) the overall project output but dilute (reduce the relative importance of) human input. Human contributors are still present in total numbers, but their proportional share shrinks as AI takes over tasks.

Terminology used across episodes

This episode discusses

The paper

Augmentation with Dilution? A Large-Scale Empirical Study of Human Contributor Ecosystems After AI Coding Agent Adoption · Read on arXiv

Weixing Zhang, Bowen Jiang, Anne Koziolek

Karlsruhe Institute of Technology

AI coding agents are rapidly proliferating in open-source software development, and the long-term sustainability of open-source projects is closely tied to the health of their human contributor ecosystems. Yet most existing studies treat human contributors as a static backdrop, and the available evidence on human participation after agent adoption mainly concerns newcomer outcomes. This paper takes the human contributor ecosystem as its dependent variable. To the best of our knowledge, it is the first study to estimate how agent adoption changes the number of distinct humans behind each pull request, and to relate this change to agent pull requests recorded under developer accounts. Using the AIDev dataset, GitHub API scanning, agent-trace screening, and two-stage propensity score matching, we construct a balanced panel of 2,246 treated and 3,798 control repositories from January 2023 to May 2026, and estimate effects with the Sun-Abraham estimator for staggered difference-in-differences, event studies, and HonestDiD sensitivity analysis. AI agent adoption is associated with a decline in human contributor density of 0.019 to 0.048, about 4-10% of its pre-adoption level, depending on the reference month (both p < 0.01); because this estimate tolerates only small violations of parallel trends, we regard it as suggestive evidence. The share of newcomers shows no detectable change (ATT = -0.009, p = 0.28), with the 95% confidence interval ruling out a decrease of more than 2.4 percentage points. Whether the decline in density is associated with agent pull requests recorded under developer accounts remains inconclusive (high minus low share: -0.013, 95% CI [-0.083, 0.057]). These findings are consistent with a pattern of augmentation with dilution: we detect no decrease in the share of newcomers, but each human contributor appears to correspond to more pull requests.

Transcript

Introduction to the show: ident: Computer Science. The day in computer science: software, systems and theory on arXiv.

Tom: We're looking at the paper: "Augmentation with Dilution? A Large-Scale Empirical Study of Human Contributor Ecosystems After AI Coding Agent Adoption".

Jane: Here's the gist of the paper. AI coding agents are not displacing human contributors, but are systematically reshaping the participation structure of opensource ecosystems <ref:2606.26289#pg2> Using a staggered difference-in-differences design on a dataset of 11,097 GitHub repositories spanning January 2023 to May 2026, we provide causal evidence via the Sun and Abraham estimator <ref:2606.26289#pg5> Our results show that AI agent adoption does not significantly change the absolute number of human contributors (ATT = 0.014, p = 0.224), but significantly reduces human contributor density (ATT = −0.019, p = 0.002) <ref:2606.26289#pg8> The relative participation share of newcomers declines significantly by 3.7 percentage points (AT T = −0.037, p < 0.001), with the effect emerging immediately after adoption and remaining stable throughout the observation window <ref:2606.26289#pg5> Review depth increases significantly by 5.3% (AT T = +0.0168, p < 0.001), indicating that AI agents shift burden from the code production stage to the review stage <ref:2606.26289#pg9> Research Questions and Design The study addresses four research questions regarding the impact of AI coding agent adoption on human contributor participation in open-source projects <ref:2606.26289#pg2>.

Tom: The design employs a staggered difference-in-differences design

12: ,

13: on a dataset of 11,097 GitHub repositories spanning January 2023 to May 2026 <ref:2606.26289#pg5>.

Jane: The primary questions examined are RQ1: How does the adoption of AI coding agents relate to changes in human contributor participation in open-source projects?

Tom: RQ2: Does AI agent adoption reduce the relative participation share of newcomer contributors?

Title and authors: Tom: So we're looking at this paper called "Augmentation with Dilution? A Large-Scale Empirical Study of Human Contributor Ecosystems After AI Coding Agent Adoption." It sounds like they’re asking if these AI coding agents are actually helping or hurting the people who contribute to open source projects.

Jane: Exactly. The title itself, "Augmentation with Dilution," suggests a trade-off, right? It hints that while something is being added—augmentation—something else is shrinking—dilution.

Lu: Right. The authors are looking at this big question using a very specific design to get causal evidence on whether AI agents augment or displace human participation in open source software development > Page two of that work reads: "We present the first largescale empirical study that takes the human contributor ecosystem as its dependent variable, examining how the number, diversity, and behavioral patterns of human contributors change following AI coding agent adoption in open-source projects <ref:2606.26289#pg1,empirical study that takes the human contributor ecosystem as its dependent variable>."

Meng: So they're treating the whole human ecosystem—how many people are contributing and what they do—as the main thing to study, not just the code that’s written by AI > Page two of that work reads: "This paper addresses that gap <ref:2606.26289#pg1>. We present the first largescale empirical study that takes the human contributor ecosystem as its dependent variable, examining how the number, diversity, and behavioral patterns of human contributors change following AI coding agent adoption in open-source projects."

Lalam: I think what's important here is they aren't just looking at code; they are focusing on the people behind that code and their participation patterns > Page two of that work reads: "This paper addresses that gap <ref:2606.26289#pg1>. We present the first largescale empirical study that takes the human contributor ecosystem as its dependent variable, examining how the number, diversity, and behavioral patterns of human contributors change following AI coding agent adoption in open-source projects."

Tom: So to summarize this first part, they're using a staggered difference-in-differences design on eleven thousand repositories from January two thousand twenty-three to May two thousand twenty-six to see if AI adoption changes the absolute number of human contributors or the way they show up <ref:2606.26289#pg1,using a staggered difference-in-differences design on>.

Jane: That's a lot of data spanning over two years, which gives them a good chance to see these effects develop over time > Page one of that work reads: "Using a staggered difference-in-differences design on a dataset of eleven thousand ninety-seven GitHub repositories spanning January two thousand twenty-three to May two thousand twenty-six we provide causal evidence via the Sun and Abraham estimator <ref:2606.26289#pg1,Using a staggered difference-in-differences design on a dataset of 11>."

Lu: And they use the Sun and Abraham estimator for that causal inference part > Page one of that work reads: "Using a staggered difference-in-differences design on a dataset of eleven thousand ninety-seven GitHub repositories spanning January two thousand twenty-three to May two thousand twenty-six we provide causal evidence via the Sun and Abraham estimator <ref:2606.26289#pg1,Using a staggered difference-in-differences design on a dataset of 11>."

Meng: The authors are careful about how they pick their study population. They define a repository as a treatment candidate if it appears in the AIDev dataset with at least one agent-authored pull request and has more than one hundred GitHub stars when they start looking > Page three of that work reads: "We define a repository as a treatment candidate if it satisfies the following quality criteria: (one) it appears in the AIDev dataset with at least one agent-authored pull request, and (two) it has more than one hundred GitHub stars at the time of data collection."

Lalam: That star threshold is important because it excludes those small toy projects, which keeps the study focused on real community activity > Page three of that work reads: "This threshold excludes toy projects and repositories with negligible community activity <ref:2606.26289#pg1>."

Tom: So we’ve got the setup—the data, the time frame, and the specific groups they are tracking—so now we need to see what their actual findings were regarding how AI agents affect these human participants.

The paper's summary: Jane: Okay, so what did this study actually find? They started by looking at four main research questions about how AI coding agent adoption relates to changes in human contributor participation in open source projects > Page two of that work reads: "RQ1: How does the adoption of AI coding agents relate to changes in human contributor participation in open-source projects <ref:2606.26289#pg1>?"

Lu: The main result for the first question is that AI agent adoption does not significantly change the absolute number of human contributors. They found an ATT of zero point zero one four with a p value of point two two four > Page one of that work reads: "Our results show that AI agent adoption does not significantly change the absolute number of human contributors (ATT = zero point zero one four, p = zero point two two four)."

Meng: So they are saying the raw count of human contributors doesn't go up or down significantly just because AI agents are being used > Page one of that work reads: "Our results show that AI agent adoption does not significantly change the absolute number of human contributors (ATT = zero point zero one four, p = zero point two two four)."

Tom: That’s interesting because you might expect some kind of impact on the total headcount if you’re adding a new tool to the workflow > Page one of that work reads: "Our results show that AI agent adoption does not significantly change the absolute number of human contributors (ATT = zero point zero one four, p = zero point two two four)."

Jane: But they move on to something else, and this is where things get more interesting for the ecosystem's structure. They found that AI agent adoption significantly reduces human contributor density by a point minus zero point one nine with a p value of zero point zero two > Page one of that work reads: "but significantly reduces human contributor density (ATT = −zero point zero one nine, p = zero point zero zero two)."

Lu: So they found that the density drops, but they keep the absolute number steady > Page one of that work reads: "but significantly reduces human contributor density (ATT = −zero point zero one nine, p = zero point zero zero two)."

Meng: The density is defined as human contributors divided by pull request count, so this means for every pull request, there are fewer human contributors on average now > Page one of that work reads: "but significantly reduces human contributor density (ATT = −zero point zero one nine, p = zero point zero zero two)."

Tom: That sounds like augmentation with dilution, which is the term they use to describe it later > Page one of that work reads: "This pattern is consistent with augmentation with dilution: human contributors remain present in absolute terms, but their relative share of project contributions declines as AI-generated pull requests accumulate <ref:2606.26289#pg1>."

Jane: And that dilution effect extends to newcomers too. The study found the relative participation share of newcomers declines significantly by three point seven percentage points > Page one of that work reads: "The relative participation share of newcomers declines significantly by three point seven percentage points (ATT = −zero point zero three seven, p < zero point zero zero one)."

Lu: That’s a significant shift in the newcomer ratio, and they say this effect emerges right after the adoption starts and stays stable for the whole observation window > Page five of that work reads: "The relative participation share of newcomers declines significantly by three point seven percentage points (ATT = −zero point zero three seven, p < zero point zero zero one), with the effect emerging immediately after adoption and remaining stable throughout the observation window."

Meng: So they are suggesting that newcomers find fewer entry points when AI agents become common > Page five of that work reads: "The relative participation share of newcomers declines significantly by three point seven percentage points (ATT = −zero point zero three seven, p < zero point zero zero one), with the effect emerging immediately after adoption and remaining stable throughout the observation window."

Tom: It’s a clear picture: fewer total human contributors per pull request, a shrinking share of newcomers, and we've got this pattern of augmentation with dilution to unpack > Page five of that work reads: "The relative participation share of newcomers declines significantly by three point seven percentage points (ATT = −zero point zero three seven, p < zero point zero zero one), with the effect emerging immediately after adoption and remaining stable throughout the observation window."

The paper's improvements: Jane: Now let’s talk about what they suggest we should do next, or what they found in terms of deeper analysis. They looked at how these effects vary across different project characteristics like size and programming language > Page three of that work reads: "RQ4: How do the effects observed in RQ1–RQ3 vary across project characteristics <ref:2606.26289#pg1>."

Lu: They looked at the moderator analysis, which shows these effects aren't uniform across all projects. For example, for Project Size, the effect on newcomer ratio is significant in the low-size group where stars are less than one hundred fifty-six > Page five of that work reads: "For Project Size, the newcomer ratio effect is significant in the low-size group (stars ≤ one hundred fifty-six) with an ATT of −zero point zero seven seven nine (p = zero point zero zero two)."

Meng: So it means AI agents have a stronger shrinking effect on newcomers when a project is small > Page five of that work reads: "For Project Size, the newcomer ratio effect is significant in the low-size group (stars ≤ one hundred fifty-six) with an ATT of −zero point zero seven seven nine (p = zero point zero zero two)."

Tom: And they also looked at programming language, and for Python and TypeScript, the effect on newcomers was consistent across those two languages > Page five of that work reads: "For Programming Language, the effect on newcomer ratio is concentrated in Python and TypeScript, with consistent direction and similar magnitude across the two languages."

Jane: That suggests they should tailor their strategies based on where you are working—like if you're in a small project or using Python or TypeScript > Page five of that work reads: "For Programming Language, the effect on newcomer ratio is concentrated in Python and TypeScript, with consistent direction and similar magnitude across the two languages."

Lu: They also found a similar pattern for project maturity, where the effect on newcomer ratio is only significant in low-maturity groups > Page five of that work reads: "For Project Maturity, the effect on newcomer ratio is significant only in the low-maturity group (AT T = −zero point zero six three six, p."

Meng: So for newcomers who are joining small or young projects, their opportunity shrinks faster > Page five of that work reads: "For Project Maturity, the effect on newcomer ratio is significant only in the low-maturity group (AT T = −zero point zero six three six, p."

Tom: So the paper points toward a tailored approach—you can't treat every project the same way when it comes to newcomer retention > Page five of that work reads: "For Project Maturity, the effect on newcomer ratio is significant only in the low-maturity group (AT T = −zero point zero six three six, p."

Jane: And they also touched on review depth. They found that review depth increases significantly by five point three percent because AI agents shift the burden from writing code production to the review stage > Page nine of that work reads: "Review depth increases significantly by five point three percent (AT T = +zero point zero one six eight, p < zero point zero zero one)."

Lu: So they’re showing that reviewers are spending more time reviewing, which is a direct consequence of AI agents taking over some of the initial coding tasks > Page nine of that work reads: "Review depth increases significantly by five point three percent (AT T = +zero point zero one six eight, p < zero point zero zero one)."

Meng: That means the burden shifts from writing code to assessing it > Page nine of that work reads: "Review depth increases significantly by five point three percent (AT T = +zero point zero one six eight, p < zero point zero zero one)."

Tom: So we’ve got the dilution effect on newcomers, the change in density, and now we're seeing more review effort shifting to maintainer work > Page nine of that work reads: "Review depth increases significantly by five point three percent (AT T = +zero point zero one six eight, p < zero point zero zero one)."

Conclusion: Jane: So, to wrap up the findings on this paper titled "Augmentation with Dilution? A Large-Scale Empirical Study of Human Contributor Ecosystems After AI Coding Agent Adoption," the main message is that AI agents aren't replacing humans in terms of absolute numbers.

Lu: That’s right, they don't significantly change the absolute number of human contributors, but they are definitely associated with declining human contributor density and a shrinking relative participation share for newcomers > Page one of that work reads: "Our results show that AI agent adoption does not significantly change the absolute number of human contributors (ATT = zero point zero one four, p = zero point two two four), but significantly reduces human contributor density (ATT = −zero point zero one nine, p = zero point zero zero two)."

Tom: And that pattern they call augmentation with dilution—humans are still around in absolute terms, but their relative share is shrinking as AI-generated pull requests pile up > Page one of that work reads: "This pattern is consistent with augmentation with dilution: human contributors remain present in absolute terms, but their relative share of project contributions declines as AI-generated pull requests accumulate <ref:2606.26289#pg1>."

Jane: And they point out that the effect on newcomers is strongest in smaller projects and for Python and TypeScript languages > Page five of that work reads: "For Project Size, the newcomer ratio effect is significant in the low-size group (stars ≤ one hundred fifty-six) with an ATT of −zero point zero seven seven nine (p = zero point zero zero two)."

Lu: And they also found that review depth increases by five point three percent because AI agents shift the burden from code production to the review stage > Page nine of that work reads: "Review depth increases significantly by five point three percent (AT T = +zero point zero one six eight, p < zero point zero zero one)."

Meng: From my side, I’m concerned about what this means for us in production; we need to think about how to manage that increased review load since the burden is shifting away from just writing new code > Page nine of that work reads: "Review depth increases significantly by five point three percent (AT T = +zero point zero one six eight, p < zero point zero zero one)."

Tom: So we’ve seen a clear pattern across the whole dataset for the paper "Augmentation with Dilution? A Large-Scale Empirical Study of Human Contributor Ecosystems After AI Coding Agent Adoption," and it suggests that the way human participation works is evolving, not necessarily disappearing > Page one of that work reads: "This paper presents the first large-scale empirical study that takes the human contributor ecosystem as its dependent variable, examining how the number, diversity, and behavioral patterns of human contributors change following AI coding agent adoption in open-source projects <ref:2606.26289#pg1,This paper presents the first large-scale empirical study that takes the>."

Jane: It really shows that while AI agents are a powerful tool for generating code, they’re reshaping how we measure success in an ecosystem > Page one of that work reads: "This paper presents the first large-scale empirical study that takes the human contributor ecosystem as its dependent variable, examining how the number, diversity, and behavioral patterns of human contributors change following AI coding agent adoption in open-source projects <ref:2606.26289#pg1,This paper presents the first large-scale empirical study that takes the>."

Lu: I think this is important because it gives us concrete evidence about the dilution effect on newcomers and where to focus our efforts > Page one of that work reads: "This paper presents the first large-scale empirical study that takes the human contributor ecosystem as its dependent variable, examining how the number, diversity, and behavioral patterns of human contributors change following AI coding agent adoption in open-source projects <ref:2606.26289#pg1,This paper presents the first large-scale empirical study that takes the>."

Meng: So we need to keep an eye on how this trend plays out as AI becomes more common in our workflows > Page one of that work reads: "This paper presents the first large-scale empirical study that takes the human contributor ecosystem as its dependent variable, examining how the number, diversity, and behavioral patterns of human contributors change following AI coding agent adoption in open-source projects <ref:2606.26289#pg1,This paper presents the first large-scale empirical study that takes the>."

Tom: We’ll take this insight about augmentation with dilution from this paper and see what we can do next for our own workflows.

More episodes

← Home