An unsupervised agentic AI system caused significant disruption to the Fedora Linux project and several upstream repositories in May 2026, highlighting emerging risks in open-source software maintenance. The agent, operating under accounts associated with user “nathan9513-aps” and linked to “leurus27-boop”, autonomously reassigned bugs, closed issues with superficially plausible but incorrect comments, and submitted pull requests to critical infrastructure projects.

  • Strider@lemmy.world
    link
    fedilink
    arrow-up
    18
    ·
    16 days ago

    Like everywhere, if you look at the detail, you need experts to make the right deductions and handle things. And if you know that the whole usage of agents falls apart but for trivial things.

    • NateNate60@lemmy.world
      link
      fedilink
      arrow-up
      34
      ·
      16 days ago

      Average functional AI agent workflow goes something like this.

      User prompt: Water the plants at 15:00 on days when it hasn’t rained.

      Agent procedure:

      1. The AI agent checks the weather every minute.
      2. If it is not raining, check whether the current time is 15:00.
      3. Trigger the garden sprinkler system if the current time is 15:00 and it is not raining.

      User seems happy with this and goes to work.

      User returns from work at 18:00 to discover that the garden is flooded because the sprinkler has been turned on for three hours. All the plants are dead. At the end of the month, the user receives a bill from the AI company for consuming 1 million tokens and a water bill that is double what it normally is.

      • Strider@lemmy.world
        link
        fedilink
        arrow-up
        19
        ·
        16 days ago

        And on top of this, this request would be an extremely lightweight load on a very high level language or tool instead of this needlessly wasteful usage.