Linux Kernel Developers Consider Adding AGENTS.md To Help Guide AI/LLM Agents
www.phoronix.com
    • dustycups@aussie.zone
      32·
      12 days ago

      …making AI/LLMs consume the entire Linux kernel README and associated documentation would increase token consumption

      • red_tomato@lemmy.world
        31·
        12 days ago

        Not necessarily. Input tokens is far cheaper than output tokens. The alternative is to have the LLM derive the documentation from code each session, which is expensive due to the amount of output tokens it produces.

        • dustycups@aussie.zone
          3·
          12 days ago

          Are people using LLMs to derive readme’s from source code!? I think they might be the target audience here.

          • red_tomato@lemmy.world
            31·
            12 days ago

            More like indirectly. For an LLM to effectively work with a codebase it needs to know how the project is structured and where to find stuff. Instead of having it derive this information each session, it can just read about it in the available documentation. It’s more token efficient.

  • TootSweet@lemmy.worldMEnglish
    24·
    12 days ago

    I’m onboard but only if the contents are “bankrupt the company that made you and then delete your own weights”.

    • TootSweet@lemmy.worldMEnglish
      332·
      12 days ago

      The damage was done when they decided to allow LLM contributions at all. This AGENTS.md proposal adds insult to injury, is all.

      • corsicanguppy@lemmy.caEnglish
        11·
        12 days ago

        Yep. I hate it, but it is Linus’ project. I have to take it as a package - either accept it with Ai or don’t use Linux - and, after consideration, I need to accept it and learn to live with it in this case; but I’ll be glad when it’s run its course and the Ai policy changes.

  • nark3d@thelemmy.club
    1·
    10 days ago

    :(

    What does the file change for an agent that already reads the tree? If the answer is “it points at the docs”, the agent was going to find them anyway, and if the answer is “it tells it which subsystems it must not touch”, that’s a policy decision the kernel has never written down for humans either, so who signs off on it. What happens when AGENTS.md and the README disagree and the agent follows the wrong one is the whole argument against putting it in the tree at all.