We currently only detect AGENTS.md as the agents resource. Many projects use tool-specific files instead, and some ship several at once.
Candidates to pick up:
CLAUDE.md (Claude Code)GEMINI.md (Gemini CLI).cursorrules and .cursor/rules/ (Cursor).windsurfrules (Windsurf).github/copilot-instructions.md (GitHub Copilot).aider.conf.yml / CONVENTIONS.md (Aider).clinerules (Cline).rules (Zed).junie/guidelines.md (JetBrains Junie)replit.md (Replit)
The current agents field on ResourceInfo is a single string, so the first match wins. That works if we just want to know a project has agent instructions, but it loses information when a repo has both AGENTS.md and CLAUDE.md. Probably worth turning this into an agents group so each tool gets its own field, similar to how community and security work in _resources.toml.
We currently only detect
AGENTS.mdas the agents resource. Many projects use tool-specific files instead, and some ship several at once.Candidates to pick up:
CLAUDE.md(Claude Code)GEMINI.md(Gemini CLI).cursorrulesand.cursor/rules/(Cursor).windsurfrules(Windsurf).github/copilot-instructions.md(GitHub Copilot).aider.conf.yml/CONVENTIONS.md(Aider).clinerules(Cline).rules(Zed).junie/guidelines.md(JetBrains Junie)replit.md(Replit)The current
agentsfield onResourceInfois a single string, so the first match wins. That works if we just want to know a project has agent instructions, but it loses information when a repo has bothAGENTS.mdandCLAUDE.md. Probably worth turning this into anagentsgroup so each tool gets its own field, similar to howcommunityandsecuritywork in_resources.toml.