Hey, thanks for the report. There’s a related open issue with auto-loading nested AGENTS.md files (we’re tracking it here: Nested agents.md files not being loaded). It seems like you’re also seeing unpredictable failure to apply even the root AGENTS.md in 2.1.26.
I need details to pass this to the engineers:
- Project structure (brief tree with paths to AGENTS.md); exact file name and case (AGENTS.md or AGENTS.MD)
- Reproduction steps + where exactly you create the new chat (root/subfolder)
- Two Request IDs: one from the chat where AGENTS.md wasn’t picked up, and one where it was (Chat → menu ⋯ → Copy Request ID)
- Screenshot/video showing that AGENTS.md didn’t appear in the context
- Logs from Developer Tools (
CMD+Shift+P→ Toggle Developer Tools → Console tab) when creating the chat - If possible—a minimal repro repository
Temporary workaround: explicitly mention @AGENTS.md at the start of the chat or open the file and ask the bot to “add AGENTS.md to the context”.
I’ll link your case to the current investigation.