gains default AGENTS.md

[jdhoffa]

Pulled verbatim from https://github.com/RMI/stitch/blob/main/AGENTS.md

[AlexAxthelm]

@jdhoffa Does this actually affect RMI's copilot instances?

[jdhoffa]

@jdhoffa Does this actually affect RMI's copilot instances?

As I understand it:

• This AGENTS.md will act as a fallback in any repository that doesn't already have a file sitting at .github/AGENTS.md
• So in case a repository doesn't have any AGENTS.md, this one would appear
• If a repository does already have a .github/AGENTS.md then that would take precedence

Based on Copilot's documentation, Copilot will look for an AGENTS.md anywhere in the repo (including under .github.

So I believe it should get recognized yeah?

[jdhoffa]

At least that's what I understand, but I could be wrong :-)

[mbarlow12]

My only hesitation here is that the content here fits in line with user-level settings (i.e. ~/.codex/AGENTS.md or ~/.claude/CLAUDE.md). Both Codex and Claude Code (CC) have ways to quickly generate the project-level context files.

• Codex appears to do it automatically
• CC has /init

Especially if we're mainly leveraging this in CI/CD right now, there's not much guidance for reviewing PRs or other specifics to check.

I'll follow up with draft "Review Guidance" section in a comment.

@jdhoffa Does this actually affect RMI's copilot instances?

As I understand it:

• This AGENTS.md will act as a fallback in any repository that doesn't already have a file sitting at .github/AGENTS.md
• So in case a repository doesn't have any AGENTS.md, this one would appear
• If a repository does already have a .github/AGENTS.md then that would take precedence

Based on Copilot's documentation, Copilot will look for an AGENTS.md anywhere in the repo (including under .github.

So I believe it should get recognized yeah?

@jdhoffa do you know if GH Copilot has a similar project < user pattern where both RMI/.github/AGENTS.md and <project repo>/AGENTS.md are loaded into context? That would be excellent and IMO fit better with the content here.

[jdhoffa]

@jdhoffa do you know if GH Copilot has a similar project < user pattern where both RMI/.github/AGENTS.md and <project repo>/AGENTS.md are loaded into context? That would be excellent and IMO fit better with the content here.

Ah maybe I miscommunicated this, Copilot does not ever look at RMI/.github/AGENTS.md, it only ever looks for context within the repository that triggered it. BUT, in practice, if that repository doesn't have a {REPO}/.github/AGENTS.md, it would infer that from the content in RMI/.github/AGENTS.md

Does that make sense?

So, to answer your question, yes I believe if a project had both a project specific {REPO}/AGENTS.md AND a {REPO}/.github/AGENTS.md, both would be used

[andre-scheinwald]

Seems reasonable. I haven't looked into using an agents.md file so I have no strong opinion. As long as it doesn't break the things :)