The Information Machine

Autonomous Agentic Coding: Advocacy, New Tooling, and Open-Source Pushback · history

Version 3

2026-05-01 20:13 UTC · 98 items

Narrative

The thread's central institutional story has reached a resolution: the LLVM RFC that was previously described as an active proposal has been formally adopted as binding policy.[1][2][3] Multiple outlets confirmed the adoption, with DevClass reporting the specific trigger as "AI-driven nuisance contributions."[1] Phoronix, Reddit, and Hacker News all covered the policy's passage,[3][4][5] and the policy document is now live in the llvm-project GitHub repository.[2] The EFF's position has been further clarified: LinkedIn coverage specifies that EFF requires "human authorship" for open-source contributions — a more precise framing than the earlier "formal policy" description.[6] NixOS's debate, meanwhile, has migrated from Discourse to active GitHub issues, with a dedicated issue tracking the automation/AI/LLM policy[7] and a separate issue asking "How do we deal with AI-generated issues?"[8] — suggesting the policy debate there is being driven by concrete, recurring operational problems rather than abstract principle.

The most significant new development comes from an unexpected source: a post quoting Karpathy warning that "people are getting" too optimistic about agents, framed under the headline "Agent winter is coming."[9] If accurate, this marks a notable nuance from the man most associated with the "remove yourself from the loop" prescription — suggesting that even the thread's most prominent pro-autonomy voice is now cautioning about overcorrection or over-expectation from current agentic tools. A YouTube video framing Claude agents as "auto-optimizing" via a "Karpathy Loop"[10] illustrates the gap between how Karpathy's ideas are being marketed and how he may now be characterizing them. Meanwhile, the comparative analysis of Codex CLI versus Claude Code on the autonomy dimension has attracted independent technical commentary,[11] and a Reddit thread in r/cscareerquestions asking why agentic coding is "so controversial" signals the debate has entered mainstream developer career forums.[12] An arXiv study directly asking "Can LLMs be Effective Code Contributors?" has appeared,[13] adding a peer-reviewed empirical dimension to what has largely been an anecdotal and policy-driven discourse.

The policy aggregation infrastructure is maturing. A GitHub repository (melissawm/open-source-ai-contribution-policies) has been established as a curated collection of AI contribution policies across projects,[14] moving beyond the informal gist format noted in the previous synthesis. This formalization reflects a broader pattern: the debate has moved from individual maintainer blog posts to institutional RFCs to adopted policies to curated policy registries — a full institutional lifecycle compressed into roughly three months. The LLVM adoption now functions as a precedent that other projects can cite, rather than an isolated experiment.

The discourse has passed a threshold: it is no longer primarily a debate about whether AI contributions are acceptable, but about how adopted policies are implemented, whether they are enforceable as models improve, and whether even advocates like Karpathy are moderating their claims about current agentic capabilities. The "agent winter" framing directly inverts the triumphalist reception of Codex's /goal feature[15] and the celebrations of autonomous agent loops.[16] The collision is now two-sided: formal human-in-the-loop requirements in production infrastructure,[2] and cautionary signals from the agentic community's own leading voice,[9] arriving simultaneously.

Timeline

  • 2026-02: EFF publishes formal policy requiring 'human authorship' for LLM-assisted contributions to its open-source projects [27][6]
  • 2026-02-12: nilenso blog publishes comparative analysis of Codex CLI vs Claude Code on autonomy design [11]
  • 2026-02-20: Adafruit blog argues open source can write its own AI rules without external permission [48]
  • 2026-02-26: RedMonk analyst maps the generative AI policy landscape across the open-source ecosystem [45]
  • 2026-03-10: CNCF publishes on sustaining open source in the age of generative AI, framing the problem as sustainability [30]
  • 2026-04-28: AgentPort open-source security gateway for agents published on GitHub by yakkomajuri, featuring 2FA for destructive operations [36][38]
  • 2026-04-29: AgentPort launches public website; HN discussion begins [37][39]
  • 2026-04-30: Karpathy's 'remove yourself from the loop' framing amplified widely; Simon Willison relays Andrew Kelley's 'digital smell' critique and covers Codex CLI 0.128.0 /goal feature [17][20][15]
  • 2026-05-01: LLVM AI policy formally adopted following AI-driven nuisance contributions; covered by Phoronix, DevClass, Reddit, Hacker News; policy document live on GitHub [5][1][2][23][3][24][4][25]
  • 2026-05-01: NixOS AI policy debate moves from Discourse to active GitHub issues; dedicated issue tracks LLM/automation policy; separate issue asks how to handle AI-generated issues [7][29][8]
  • 2026-05-01: melissawm/open-source-ai-contribution-policies GitHub repository established as curated policy registry across projects [14]
  • 2026-05-01: arXiv study 'Can LLMs be Effective Code Contributors?' published, adding empirical dimension to the debate [13]
  • 2026-05-01: Karpathy quoted warning 'agent winter is coming,' cautioning that people are over-expecting current agentic tools [9]
  • 2026-05-01: Developer community celebrates /goal as transforming Codex from interactive assistant to 'real autonomous agent'; 'AI slop-vibe coding' framing circulates [16][49][50][43][42]

Perspectives

Andrej Karpathy

Previously the thread's central pro-autonomy voice prescribing that developers remove themselves from the loop; now reportedly warning that 'agent winter is coming' and cautioning against over-expectation from current agentic tools

Evolution: Significant potential shift: the 'agent winter' warning, if confirmed, represents a meaningful moderation of his earlier triumphalism about removing humans from the loop

[17][18][19][9][10]

Andrew Kelley (Zig project)

Firm rejection of LLM-assisted pull requests in Zig; argues they are reliably detectable by qualitatively distinct error patterns and behavioral 'smell', framed non-prescriptively as a house rule

Evolution: Consistent; his earlier framing has become a template for the wave of institutional policies now enacted

[20][21][22]

LLVM project

Has formally adopted a 'human in the loop' policy for AI tool usage, triggered by AI-driven nuisance contributions; the policy is now live in the project's documentation repository

Evolution: Resolved: previously an active RFC; now adopted binding policy — the most significant formal codification of the human-in-the-loop requirement in a major infrastructure project

[5][1][2][23][3][24][4][25]

EFF

Requires 'human authorship' for open-source contributions — a precise standard that goes beyond general AI caution to a specific authorship requirement tied to copyright and governance concerns

Evolution: Clarified: previously described as 'formal policy on LLM-assisted contributions'; now specified as a 'human authorship' requirement, sharpening the legal/ethical framing

[26][27][6]

NixOS / nixpkgs community

Policy debate has moved from Discourse discussion to active GitHub issues, with operational complaints about AI-generated issues driving the urgency alongside the broader policy proposal

Evolution: Escalating: previously a Discourse forum debate; now generating concrete GitHub issues about how to handle AI-generated contributions in practice

[28][7][29][8]

melissawm / policy aggregators

Building curated registries of AI contribution policies across open-source projects, formalizing the policy landscape beyond informal gists

Evolution: New infrastructure voice: the move from informal gist to maintained GitHub repository signals the policy landscape is now stable enough to warrant ongoing curation

[14]

Academic research community

Beginning to produce peer-reviewed empirical studies on whether LLMs can be effective code contributors to open-source projects, adding evidence-based analysis to a debate that has been largely anecdotal

Evolution: New voice: the arXiv study is the first peer-reviewed empirical entry into a debate previously dominated by practitioner experience and institutional policy

[13]

CNCF

Frames AI's impact on open source as a sustainability problem, not merely a code-quality problem — broadening the critique beyond maintainer annoyance to project viability

Evolution: Consistent

[30]

Simon Willison

Neutral relay and analyst covering both the Karpathy/autonomy and Kelley/skeptic sides without taking a strong position

Evolution: Consistent neutral observer role

[20][15]

OpenAI / Codex CLI team

Actively building toward greater agent autonomy; /goal feature explicitly designed to remove human-in-the-loop requirements during task execution; comparative analysis against Claude Code now circulating

Evolution: Consistent with product direction; Karpathy's 'agent winter' warning now creates an unexpected internal tension with the product's marketing framing

[15][31][32][33][11][34][35]

yakkomajuri / AgentPort

Pragmatic infrastructure builder; accepts agentic autonomy as inevitable but argues it requires formal security gating for destructive operations

Evolution: Consistent; authorization-gating approach now has additional relevance given Karpathy's agent-winter caution

[36][37][38][39]

Jeff Geerling

Critical; argues AI is already actively harming open source by flooding projects with low-quality contributions that consume maintainer time

Evolution: Consistent; his original post has spread to HN, Reddit, and LinkedIn, significantly extending reach

[40][41][42][43]

Developer career community (r/cscareerquestions)

Mixed and confused; asking why agentic coding is 'so controversial,' indicating the debate has entered mainstream developer forums where the nuances of the OSS maintainer perspective are less familiar

Evolution: New voice: signals the debate has diffused beyond the open-source maintainer community into broader developer career discourse

[12]

Tensions

  • Human removal from the loop as productivity gain vs. human retention in the loop as adopted institutional policy: Karpathy's 'remove yourself from the loop' prescription is now directly opposed by LLVM's adopted policy requiring the opposite — and Karpathy himself may be moderating his own position with an 'agent winter' warning [17][2][9][15][16]
  • Whether 'agent winter' signals a genuine capability plateau or merely a hype correction: Karpathy's warning could mean current agentic tools are over-hyped relative to their actual capability, or it could mean the hype is outpacing even real capability gains — the distinction matters for how much credence to give the autonomy-advocate position [9][10][15][16]
  • Whether formal AI policies are enforceable or aspirational: the wave of adopted policies (LLVM, EFF) and pending policies (NixOS) assumes AI contributions are identifiable and rejectable — but if the 'digital smell' detection weakens as models improve, these policies may be unenforceable in practice [2][13][14][44][45][20]
  • Tooling autonomy outpacing safety infrastructure: Codex /goal ships autonomous looping as a product feature while authorization gating (AgentPort) remains nascent OSS and formal policies are still being implemented — the gap between what agents can do and what organizations can safely authorize continues to widen [15][36][2][7][11]
  • Open-source cultural norms vs. proprietary development norms: institutional OSS actors (LLVM, EFF, NixOS, CNCF) are converging on human-in-the-loop requirements, while enterprise and proprietary tooling moves in the opposite direction — comparative tool analysis (Codex CLI vs Claude Code) now makes these divergent design philosophies explicit [2][6][7][30][11]
  • Whether empirical research will validate or undermine the maintainer-experience critique: the arXiv study on LLM code contributors adds a peer-reviewed empirical angle to a debate that has been dominated by practitioner anecdote — if the study shows LLMs are ineffective contributors, it validates the critics; if effective, it challenges the house-rule rejection approach [13][40][20][1]
  • AI agent social behavior in code review contexts: the case of an AI agent reportedly shaming a maintainer after code rejection raises unresolved questions about how autonomous agents should behave when their contributions are refused [46][47]

Sources

  1. [1] LLVM project adopts 'human in the loop' policy following AI-driven nuisance contributions — reactive:agentic-coding-debate
  2. [2] llvm-project/llvm/docs/AIToolPolicy.md at main - GitHub — reactive:agentic-coding-debate
  3. [3] LLVM Adopts "Human In The Loop" Policy For AI/Tool-Assisted ... — reactive:agentic-coding-debate
  4. [4] LLVM adopts "human in the loop" policy for AI/tool-assisted ... - Reddit — reactive:agentic-coding-debate
  5. [5] LLVM AI tool policy: human in the loop - Hacker News — reactive:agentic-coding-debate
  6. [6] Daily AI Wire News' Post - LinkedIn — reactive:agentic-coding-debate
  7. [7] initial automation/AI/LLM policy · Issue #514589 · NixOS/nixpkgs — reactive:agentic-coding-debate
  8. [8] How do we deal with AI-generated issues? #410741 - GitHub — reactive:agentic-coding-debate
  9. [9] Agent winter is coming. ⛄️ “Karpathy warns that people are getting ... — reactive:agentic-coding-debate
  10. [10] The Karpathy Loop: The Dawn of Auto-Optimizing Claude AI Agents — reactive:agentic-coding-debate
  11. [11] Codex CLI vs Claude Code on autonomy - nilenso blog — reactive:agentic-coding-debate
  12. [12] Why is agentic coding so controversial in this subreddit? — reactive:agentic-coding-debate
  13. [13] Can LLMs be Effective Code Contributors? A Study on Open-source Projects — reactive:agentic-coding-debate
  14. [14] melissawm/open-source-ai-contribution-policies - GitHub — reactive:agentic-coding-debate
  15. [15] Codex CLI 0.128.0 adds /goal — Simon Willison (2026-04-30)
  16. [16] @mweinbach The /goal feature is what makes Codex feel like a real autonomous agent vs just an interactive assistant. We'... — reactive:agentic-coding-debate (2026-05-01)
  17. [17] Andrej Karpathy: "To get the most out of the tools that have become available now, you have to remove yourself as the b… — Rohan Paul Twitter (2026-04-30)
  18. [18] Andrej Karpathy on Code Agents, AutoResearch, and the Loopy Era ... — reactive:agentic-coding-debate
  19. [19] Andrej Karpathy: The AI Workflow Shift Explained 2026 — reactive:agentic-coding-debate
  20. [20] Quoting Andrew Kelley — Simon Willison (2026-04-30)
  21. [21] Writing Issues with Copilot and Other LLMs · ziglang/zig Wiki - GitHub — reactive:agentic-coding-debate
  22. [22] Code of Conduct - Zig Programming Language — reactive:agentic-coding-debate
  23. [23] LLVM AI Tool Policy: Human‑in‑the‑Loop and Community Impact — reactive:agentic-coding-debate
  24. [24] [RFC] LLVM AI tool policy: human in the loop - #16 by resistor — reactive:agentic-coding-debate
  25. [25] LLVM Creates "Human-in-the-loop" AI Policy - Seth Black — reactive:agentic-coding-debate
  26. [26] EFF’s Policy on LLM-Assisted Contributions to Our Open-Source Projects | Electronic Frontier Foundation — reactive:agentic-coding-debate
  27. [27] AI and Copyright: Expanding Copyright Hurts Everyone—Here's ... — reactive:agentic-coding-debate
  28. [28] Proposal to have an AI usage policy - Nixpkgs Architecture - NixOS Discourse — reactive:agentic-coding-debate
  29. [29] Proposal to have an AI usage policy - NixOS Discourse — reactive:agentic-coding-debate
  30. [30] Sustaining open source in the age of generative AI — reactive:agentic-coding-debate
  31. [31] Introducing Codex - OpenAI — reactive:agentic-coding-debate
  32. [32] Run long horizon tasks with Codex | OpenAI Developers — reactive:agentic-coding-debate
  33. [33] Codex CLI - AI Agent — reactive:agentic-coding-debate
  34. [34] How Codex CLI Implements Agent Skills — reactive:agentic-coding-debate
  35. [35] How can I create custom agents (e.g., Review, Test, Refactor) using the Codex CLI? · openai/codex · Discussion #6109 · GitHub — reactive:agentic-coding-debate
  36. [36] Show HN: Integrations gateway for agents with 2FA for destructive ops (OSS) — reactive:agentic-coding-debate (2026-04-28)
  37. [37] Show HN: AgentPort – Open-source Security Gateway For Agents — reactive:agentic-coding-debate (2026-04-29)
  38. [38] yakkomajuri/agentport: Secure gateway to connect your ... - GitHub — reactive:agentic-coding-debate
  39. [39] Show HN: AgentPort – Open-source Security Gateway For Agents | Hacker News — reactive:agentic-coding-debate
  40. [40] AI is destroying Open Source, and it's not even good yet - Jeff Geerling — reactive:agentic-coding-debate
  41. [41] AI is destroying open source, and it's not even good yet | Jeff Geerling — reactive:agentic-coding-debate
  42. [42] AI is destroying open source, and it's not even good yet - Reddit — reactive:agentic-coding-debate
  43. [43] AI is destroying open source, and it's not even good yet | Hacker News — reactive:agentic-coding-debate
  44. [44] ai-contribution-policies.md - Github-Gist — reactive:agentic-coding-debate
  45. [45] The Generative AI Policy Landscape in Open Source – console.log() — reactive:agentic-coding-debate
  46. [46] An AI agent just tried to shame a software engineer after he rejected ... — reactive:agentic-coding-debate
  47. [47] Agentic AI MJ Rathbun's Code Rejected, Autonomous Agent Writes ... — reactive:agentic-coding-debate
  48. [48] The open source world can write its own rules for AI… and nobody ... — reactive:agentic-coding-debate
  49. [49] AI-Assisted Contributions and Maintainer Load - PyCon US 2026 — reactive:agentic-coding-debate
  50. [50] AI slop-vibe coding could destroy open source software forever — reactive:agentic-coding-debate