| ▲ | forgotusername6 8 hours ago | |||||||
Interesting that they had a 100% read rate of agents.md. In my test repo lower down agents.md files were occasionally missed by vscode copilot. That fact put me off putting too much effort into nesting agents.md files too much within the repo and I've been focusing on agent skills instead. | ||||||||
| ▲ | weiliddat 7 hours ago | parent | next [-] | |||||||
This is more a harness thing signaling the presence or forcing a read on AGENTS/CLAUDE.md right? | ||||||||
| ||||||||
| ▲ | qingcharles 5 hours ago | parent | prev | next [-] | |||||||
I often start a new session with tagging AGENTS.md in the prompt just to make sure because I've had the same issue happen a couple of times. | ||||||||
| ▲ | lelandbatey 7 hours ago | parent | prev [-] | |||||||
The 100% read rate is very harness/CLI dependent. The "original" idea for AGENTS.md was: the AGENTS.md file will be included as-is in the system prompt by the harness, so the agent doesn't have any choice in whether it'll be read or not. For example, this is a shortened form of what opencode sends as a system prompt for a new session when interacting with a provider (displayed in YAML for formatting, and edited for formatting):
My AGENTS.md file contents start at the "# Overview" line.Notice that the harness is just unceremoniously dumping the AGENTS.md file into the exact same text stream as the system prompt, barely contextualizing that hey, starting now, this text is from AGENTS.md and not from the harness. If you want AGENTS.md to work (likewise, if you want skills or anything else to work) you have to know how the harness is handling/feeding them to the LLM, because no LLM will reliably look on their own. | ||||||||