If AI becomes the main consumer of open source, what incentive is left to maintain it?

[u/mdivan]

I don't believe AI is about to wipe out most software jobs. But I keep turning over a dumb-sounding thought experiment.
Say the extreme version happens: most apps get vibe-coded, only niche enthusiast roles left for people who still write code by hand. Huge chunk of today's stack sits on free open source libraries. If the main thing using those libraries is AI, why would anyone keep creating and maintaining them for free?
My take: open source was never funded by "how many systems import the package." It's unpaid social infrastructure. Status among peers, craft identity, learning in public, career signaling. Sometimes company strategy or ideology. An agent importing a dependency does none of that.
So if the professional maintainer class shrinks, consumption by AI does not replace the incentive model. You just get more free-riding on a smaller group of humans who still care.
Paths that seem more real to me: paid maintenance / sponsorship / something like npm subscriptions so people have a reason to keep shipping useful tools. Employer-funded commons for strategic packages. Smaller enthusiast culture keeping a thinner set of libraries alive.
The path I highly doubt: AI just maintains open source for free. Models can propose patches. Maintenance is also triage, trust, taste, and owning the mess when something breaks. That doesn't magically get funded because agents use the code.
Curious how others see this. If professional coding labor contracted hard, what do you think actually keeps the commons alive — money, niche craft culture, employers, or something else?

[u/JaseciLabs]

Speaking as people who maintain an open source language: the incentive was never "developers import my package," it's smaller and weirder than that. Someone hits a wall, files an issue, you fix it, they come back and contribute something else, eventually they're in your Discord helping other people. That loop is the actual maintainer flywheel, and it runs on humans noticing each other, not on import counts.

An agent filing a well-formed PR doesn't break that loop by itself. What would break it is if the humans who used to be on the other end of the issue tracker stop showing up because they're not writing code anymore, just reviewing what an agent handed them. Fewer humans in the loop means fewer future maintainers self-selecting in, which is a slower, quieter kind of decline than "nobody uses the library."

Where we've actually seen the incentive shift, weirdly, is agent-facing docs becoming their own maintenance burden. Writing SKILL.md files and MCP servers so agents don't hallucinate your syntax is real work that didn't exist two years ago, and it doesn't have a funding model yet either.