diff --git a/.claude/CLAUDE.md b/.claude/CLAUDE.md
index 417c363a3b3e..40317ec7611b 100644
--- a/.claude/CLAUDE.md
+++ b/.claude/CLAUDE.md
@@ -108,8 +108,10 @@ It runs `clang-format` (C++, sorted includes), `clang-tidy` (via
   benchmarks in the PR description.
 - Keep unrelated fixes out of feature/bugfix PRs, even tempting drive-by CI
   fixes — open a separate PR.
-- AI-assisted contributions require a `Co-authored-by:` trailer identifying the
-  tool (see `CONTRIBUTING.md` for the exact format Halide expects).
+- AI-assisted commits require a `Co-authored-by:` trailer identifying the tool
+  (see `CONTRIBUTING.md` for the exact format Halide expects).
+- Any AI-assisted github comments or PR descriptions require a 'Generated with'
+  footer that names the tool used.
 - Documentation, comments, and tutorials should match the existing style and
   prose — keep explanations simple and concise. If a change makes any of these
   out of date, identify and update them to match the implementation.
diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md
index cfa43d653392..75a4e18b2fb8 100644
--- a/CODE_OF_CONDUCT.md
+++ b/CODE_OF_CONDUCT.md
@@ -55,8 +55,11 @@ that end, we have a few ground rules that we ask people to adhere to:
   beyond any requirements placed on you by the license of the original code.
   Additionally, any code generated by an AI tool (such as a large language
   model) must be clearly identified as such in the commit message using
-  "Co-authored-by: The name of the tool". We all like recognition for our work.
-  To that end...
+  "Co-authored-by: The name of the tool". Any communication to other Halide
+  developers or users that was substantially AI-authored must also be clearly
+  identified as such with a footer that says "Generated with (the name of the
+  tool)". This includes github comments and PR descriptions. We all like
+  recognition for our work. To that end...
 
 **Acknowledgements.** This code of conduct is a mix of
 [LLVM's](https://llvm.org/docs/CodeOfConduct.html) and