Excited to see this problem start to go away now that others will follow what OpenAI does (though other agents could have worked on openly and collectively deciding their own path but didn't). I maintain that “agent(s)” are what consume context and inside this structure is the explicit context. Categorically, this should have been more oriented towards “context” language - like other efforts to standardize around context. Also, such a deep bet on .md file types being cemented into the naming of the solution. I can’t see the future but I can guarantee it doesn’t stay with markdown being the solution for context file types - just isn’t going to happen. I also hope that standardization around context (what’s in an agents.md) files actually happens openly via an actual forum for identifying great solutions for context. Great to see a shared file location but without coordination on the rest, this will remain an effort of follow the leader and least common denominator feature compatibility. We were collaborating with agent labs on solving this problem openly but we’ll move research work to focus on some other problems now that this seems to be heading in this direction. I’m sure that context delivery standards work will find its way back to help influence client-hosted context as well. This how we developed the spec openly, would love to see agents.md’s future support show up in a similar forum or literally in this forum. github.com/opencontextsta…