# Who should own CLAUDE.md and AGENTS.md on a team?

> Source: <https://gethrbr.com/blog/who-owns-claude-md>
> Published: 2026-11-18 00:00:00+00:00

**Recommendation:** Put CLAUDE.md, AGENTS.md and agent rule directories under a CODEOWNERS entry with required code-owner review, and replace copied or merely mentioned AGENTS.md content with an @AGENTS.md import.
More in the playbook "Working with AI coding agents": <https://wpnews.pro/playbooks/coding-agents>

Blog

# Who should own CLAUDE.md and AGENTS.md on a team?

Published

Give the rule files code owners. A `CODEOWNERS` entry for `CLAUDE.md`, `AGENTS.md`, `.claude/`, `.cursor/rules/` and Copilot's instructions, plus GitHub's “Require review from Code Owners”, puts a named reviewer on every change to what the agents read. Then give that owner a regular prune, because nothing in these files expires.

That is the short answer. The rest of this note gives the file, what the owner should ask of each change, and what review alone does not catch. GitHub and Anthropic facts are from their docs, read on 18 November 2026.

## Why a rules file needs an owner

A line in `CLAUDE.md` changes what every teammate's agent does on every task. It is often added inside a feature pull request, where the reviewer is reading the feature. Anthropic already asks for upkeep: the [memory docs](https://code.claude.com/docs/en/memory) say to review CLAUDE.md files, nested ones and `.claude/rules/` “periodically to remove outdated or conflicting instructions.” Without a name next to the file, periodically means never.

The repos that keep two rule files show what an unowned pair looks like. In our scan of public GitHub repos where a root `CLAUDE.md` sits beside a root `AGENTS.md` ([the study](https://gethrbr.com/blog/claude-md-agents-md-github-study), [data](https://gethrbr.com/data/claude-md-agents-md-study-2026-10-18.csv)):

| What CLAUDE.md does with the AGENTS.md beside it | Share of pairs | 
|---|---|
| Never mentions it, so by default Claude Code never reads it | 16.4% | 
| Asks Claude in a sentence to read it, so only if Claude opens it | 14.9% | 
| Was copied from it once, then drifted | 7.0% | 
| Copies its lines, a second copy to keep current | 6.6% | 

Each row is a fix a reviewer who owns both files would ask for in one comment: an `@AGENTS.md` import in place of the sentence or the copy.

## The CODEOWNERS file

GitHub reads `CODEOWNERS` from `.github/`, the repo root or `docs/`, and “code owners are automatically requested for review when someone opens a pull request that modifies code that they own” ([GitHub docs](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners)):

```
# .github/CODEOWNERS
# The last matching pattern wins, so keep these lines at the end.
CLAUDE.md                          @acme/agent-rules
AGENTS.md                          @acme/agent-rules
/.claude/                          @acme/agent-rules
/.cursor/rules/                    @acme/agent-rules
/.github/copilot-instructions.md   @acme/agent-rules
/.github/instructions/             @acme/agent-rules
```

A pattern with no slash, like `CLAUDE.md`, matches the file in any folder, so nested files are covered too. Order matters: “the last matching pattern takes the most precedence”, so a broad line such as `* @acme/everyone` placed after these would take them back. A request is not a requirement, though. To block a merge until the owner approves, turn on “Require review from Code Owners” in the branch protection rule or ruleset for your default branch.

Pick the owner by who answers for agent behaviour, not by who wrote the first file. On a small team that is one senior engineer; on a larger one, a group of two or three, so reviews do not wait on one person's holiday.

## What the owner asks of each change

| The change | The question | 
|---|---|
| A new rule | Could the agent learn this from the code? If yes, it costs context and adds nothing | 
| A new rule | Can someone check it was followed? "Run pnpm test before committing", not "test your changes" | 
| A new rule | Must it hold every time? Then it belongs in a hook or a deny rule, not prose | 
| A rule that names a path, flag or tool | Does that thing still exist on the default branch? | 
| Text pasted into a second file | Can it be an @import instead of a copy? | 
| Anything | Does it contradict a line in another rules file? Claude may pick either one | 
| Anything | Is the file still under about 200 lines, Anthropic’s target? | 

The fuller version of the size and hook questions is in [how long should CLAUDE.md be](https://gethrbr.com/blog/how-long-should-claude-md-be) and [CLAUDE.md vs skills vs hooks](https://gethrbr.com/blog/claude-md-vs-skills-vs-hooks). To test whether a proposed rule changes anything before you approve it, see [how to test a CLAUDE.md rule](https://gethrbr.com/blog/test-claude-md-rule).

## The prune: a recurring job, not a review

Review catches what changes. It does not catch the rule that went stale because the code moved under it, since nobody opened a pull request on the rules file. That needs a scheduled pass by the owner. Claude Code ships one: `/doctor prompt-audit` looks for instructions written for older models, references to files or commands that no longer exist, and files that contradict each other, and changes nothing until you ask it to apply the edits. Our free [rules file checker](https://gethrbr.com/check) says which agents load a file from where it sits. What goes stale, and why, is in [context rot and stale rules](https://gethrbr.com/blog/context-rot-stale-rules).

## Who owns the files outside the repo

- **A managed CLAUDE.md** is owned by whoever ships it to the machines, usually IT through MDM. Developers cannot exclude it with`claudeMdExcludes` , so changes to it deserve the same review as the repo file.
- **Cursor Team Rules** live in the Cursor dashboard on Team and Enterprise plans. An enforced rule “is required for all team members and cannot be disabled” ([Cursor docs](https://cursor.com/docs/context/rules) ), and it has no pull request, so name who may edit it.
- **Each person's home files** , such as`~/.claude/CLAUDE.md` , belong to that person and should stay personal. A team rule that lives only there is a rule the rest of the team never gets ([using one CLAUDE.md for all your projects](https://gethrbr.com/blog/claude-md-for-all-projects) ).

## What an owner cannot catch

An owner reviews what someone writes down. Most corrections never get that far: a teammate tells their agent “we retry on 5xx only” in a session, a reviewer says it in a pull request comment, the payments channel decides it in Slack. None of those opens a change to the rules file, so there is nothing to review. Getting them written down is its own job, covered in [turning review comments into agent rules](https://gethrbr.com/blog/code-review-comments-as-agent-rules).

## Questions

### Who should own CLAUDE.md on a team?

Whoever answers for how the team's agents behave: one senior engineer on a small team, a group of two or three on a larger one. Name them in CODEOWNERS for CLAUDE.md, AGENTS.md, .claude/, .cursor/rules/ and the Copilot instructions, and turn on required review from code owners.

### Can I use CODEOWNERS for CLAUDE.md?

Yes. A line such as "CLAUDE.md @acme/agent-rules" matches the file in every folder. Code owners are requested for review on any pull request that changes it, and "Require review from Code Owners" in branch protection makes their approval a merge condition. The last matching pattern in the file wins.

### How often should we review CLAUDE.md?

On every change, through code owner review, and on a schedule for the rules that went stale without a change. Anthropic's docs ask for a periodic review to remove outdated or conflicting instructions, and /doctor prompt-audit finds references to files and commands that no longer exist.

### Does code review keep agent rules up to date?

Only for what someone writes down. A correction given to an agent in a session, a pull request comment or a Slack decision never opens a change to the rules file, so the owner never sees it. Those need a way into the file first.
