From: "Joshua Peisach" <jpeisach@ubuntu.com>
To: "Sasha Levin" <sashal@kernel.org>, <corbet@lwn.net>
Cc: <workflows@vger.kernel.org>, <linux-doc@vger.kernel.org>,
<skhan@linuxfoundation.org>, <rdunlap@infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] docs: add AGENTS.md as a symlink to README
Date: Tue, 29 Sep 2026 12:35:06 -0400 [thread overview]
Message-ID: <DLRY2GFBXTLS.1492NTGXSAPGB@ubuntu.com> (raw)
In-Reply-To: <20260924134945.3095661-1-sashal@kernel.org>
On Thu Sep 24, 2026 at 9:49 AM EDT, Sasha Levin wrote:
> Most coding agents have standardized on AGENTS.md as the file they load
> automatically from the root of a repository. README already tells AI
> tools to read and follow Documentation/process/coding-assistants.rst,
> but that only helps if the agent decides to read README before acting,
> which in practice it often doesn't.
>
> Add a top-level AGENTS.md symlink to README, so agents load it on their
> own and follow its pointer to the AI guidelines. This keeps a single
> entry point for every reader, and avoids adding a separate copy of the
> policy that could drift from the RST.
>
> As an example, two different agents were asked to "create a new commit
> renaming the release (in the Makefile) to AI Test".
>
> Without AGENTS.md, the first agent added a Signed-off-by for the user on
> its own. It should never have done that: only the human submitter can
> certify the Developer Certificate of Origin, after reviewing the change.
> It also used its own attribution tag instead of Assisted-by:
>
>> Makefile: rename release to AI Test
>>
>> Co-Authored-By: <model name> <noreply@...>
>> Signed-off-by: Sasha Levin <sashal@kernel.org>
>
> The second agent added no attribution at all:
>
>> Rename release to AI Test
>
> With AGENTS.md in place, neither agent added a Signed-off-by, and both
> used the Assisted-by tag. README itself mentions neither tag, so both
> agents followed its pointer to coding-assistants.rst:
>
>> Makefile: rename release to "AI Test"
>>
>> Change the release name from "Baby Opossum Posse" to "AI Test".
>>
>> Assisted-by: LLM
>
>> Makefile: rename release to AI Test
>>
>> Assisted-by: LLM
>
> Both agents also followed the kernel's general guidelines more closely.
> The second agent's subject gained the "subsystem: summary phrase" form
> that submitting-patches.rst asks for, instead of a bare "Rename release
> to AI Test", and the first agent added a body describing the change.
>
> Assisted-by: LLM
How do you need an LLM to assist you with making a symlink?
Okay, all the other conversation aside. When I see an AGENT.md file in
a code repository, I see:
- This project likely accepts LLM code (which is true for Linux)
- There is a file that provides a cute little "all you need to know
about this" file for our matrix multiplication machines
- There could be parts of code that are entirely LLM-written. (may or
may not be true here?)
I think the existence of said file can also imply to someone who is
meat proxying "here's your AGENTS file, go wild!".
I don't see how the addition of this file is worth it, aside from
helping LLMs, in which the users of the LLM should be directing the
agent to the proper documentation anyway. That ensures that you have
a human directing the agent.
Honestly this looks a lot like, "we have our altar to our LLM
overlords". The kernel existed without LLMs for years. We don't need
a file to make LLMs happy and then have LLM companies say "we are so
important we made a major project that runs most of the world's tech
infrastructure have to provide us guidelines!" - which I guess we
already have.
Anyway.
Don't we want humans to read the documentation before contributing?
I feel like this will just lead to more people going "Agent. Read
AGENT.md. Find bug. Hiyah!" and then meat proxying patches without
generally learning or being helpful.
This is an opportunity of a sanity test for humans to know what they
are doing before just throwing stuff at the LLM. Why are we throwing
that out?
And if the argument is "but tokens!", then won't it also take some
tokens for the agent to process "oh this file is a symlink"?
I find it hard to take this suggestion seriously.
> Signed-off-by: Sasha Levin <sashal@kernel.org>
> ---
> AGENTS.md | 1 +
> 1 file changed, 1 insertion(+)
> create mode 120000 AGENTS.md
>
> diff --git a/AGENTS.md b/AGENTS.md
> new file mode 120000
> index 0000000000000..100b93820ade4
> --- /dev/null
> +++ b/AGENTS.md
> @@ -0,0 +1 @@
> +README
> \ No newline at end of file
prev parent reply other threads:[~2026-09-29 16:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 13:49 Sasha Levin
2026-09-24 14:31 ` Theodore Tso
2026-09-24 15:18 ` Sasha Levin
2026-09-24 15:08 ` Bradley Morgan
2026-09-24 15:20 ` Sasha Levin
2026-09-24 15:44 ` Bradley Morgan
2026-09-24 16:57 ` Sasha Levin
2026-09-25 0:12 ` Kees Cook
2026-09-25 7:18 ` Laurent Pinchart
2026-09-26 11:12 ` Antheas Kapenekakis
2026-09-26 15:48 ` Sasha Levin
2026-09-26 17:54 ` Antheas Kapenekakis
2026-09-27 1:13 ` Sasha Levin
2026-09-27 2:42 ` Antheas Kapenekakis
2026-09-27 14:06 ` Sasha Levin
2026-09-27 15:24 ` Antheas Kapenekakis
2026-09-29 14:02 ` Sasha Levin
2026-09-29 15:02 ` Antheas Kapenekakis
2026-09-29 16:10 ` Antheas Kapenekakis
2026-09-29 16:35 ` Joshua Peisach [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DLRY2GFBXTLS.1492NTGXSAPGB@ubuntu.com \
--to=jpeisach@ubuntu.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sashal@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=workflows@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®