Readit News> Place another AGENTS.md inside each package. Agents automatically read the nearest file in the directory tree, so the closest one takes precedence and every subproject can ship tailored instructions. For example, at time of writing the main OpenAI repo has 88 AGENTS.md files.
In any case, I increasingly question the use of an agents file. What's the point, then the agent forget about them every few prompt, and need to be constantly reminded to go through the file again and again?
Another thought: are folks committing their AGENTS.md? If so, do you feel comfortable with the world knowing that a project was built with the help of AI? If not, how do you durably persist the file?
With Claude code and others, if I put a context file (agent.MD or whatever) in a project subfolder, e.g., something explaining my database model in with the related code, it gets added to the root project context when the agent is using that subfolder.
It sounds to me like this formulation doesn’t support that.
That being said, I'm not against removing features but neither this or the original post provide any substantial rationale on why it should be removed. Uses for XSLT do exist and the alternative is "just polyfill it" which is awkward especially for legacy content.
The US is making a big mistake giving up on the EV chain. In doing so it is ceding drones and robots, which are key to future wars and economies.
The countries that it is currently waging economic war against should instead be engaged in creating an alternative to the Chinese supply chain. For example, it is currently disassembling the automotive supply chain that included Canada and low-cost Mexico, but it should be doubling down on that.
Perhaps they've fixed it since? I don't know because they've already burned my trust and they've done nothing to earn it back. Publicly acknowledging and apologizing for this would have been a way to start getting off my list of bad actors.
Even if they've made it possible to successfully turn those off deep in the menus now, whatever dreamed-up definition of "opted in" it's operating under is a tortured legalistic one that undermines the actual meaning and spirit of opting in.
And what’s worse is that the companies always seem to find a way to reset it to what they want quite frequently. One of their tricks is to reorganize permissions frequently so the ones that allow their spam to get through are always new.
Amp used to have an "RFC 9999" article on their website for this as well but the link now appears to be broken.
You can symlink your Cursor / Windsurf / whatever rules to AGENTS.md for backwards compatibility.
"Guidance for Use"
Your preference for bullet lists over headers is odd. This comes down to what works best with the models - they are interpreting it. This is a moving target. If you believe that your suggestion works best you should provide some sort of evidence. The default would be to not even get into that sort of thing.
Non-Hierarchical AGENTS.md
Claude-code, Gemini, and GHCP all support hierarchical context files. Your proposal and this new one from OpenAI and friends do not, and I think that is a shame.