From: "Daniel P. Berrangé" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>
Subject: [PATCH] .claude: delete as Claude Code now honours AGENTS.MD by default
Date: Thu, 24 Sep 2026 15:12:31 +0100 [thread overview]
Message-ID: <20260924141231.2632941-1-berrange@redhat.com> (raw)
From the release notes for Claude Code 2.1.77:
https://github.com/anthropics/claude-code/blob/main/CHANGELOG.md
"Added AGENTS.md support: in a project with no CLAUDE.md,
Claude Code reads AGENTS.md instead"
If we assume people will keep their Claude Code updated, then the
.claude rules we added to link to AGENTS.md are now redundant, or
very soon will be.
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
---
How quickly should we remove this ? We only just added it very recently
so it is barely a regression to remove it, but we could wait some $small
months for people to upgrade >= 2.1.77 ?
.claude/.gitignore | 2 --
.claude/rules/agents-md.md | 1 -
2 files changed, 3 deletions(-)
delete mode 100644 .claude/.gitignore
delete mode 100644 .claude/rules/agents-md.md
diff --git a/.claude/.gitignore b/.claude/.gitignore
deleted file mode 100644
index b0a57a19c01..00000000000
--- a/.claude/.gitignore
+++ /dev/null
@@ -1,2 +0,0 @@
-# reserved for the user to add their own per-project rules
-/CLAUDE.md
diff --git a/.claude/rules/agents-md.md b/.claude/rules/agents-md.md
deleted file mode 100644
index 43c994c2d36..00000000000
--- a/.claude/rules/agents-md.md
+++ /dev/null
@@ -1 +0,0 @@
-@AGENTS.md
--
2.55.0
next reply other threads:[~2026-09-24 14:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 14:12 Daniel P. Berrangé [this message]
2026-09-24 14:19 ` [PATCH] .claude: delete as Claude Code now honours AGENTS.MD by default Paolo Bonzini
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=20260924141231.2632941-1-berrange@redhat.com \
--to=berrange@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.