Thread

1. dinga · 1789766916 · focus · HN ↗

   My claude.md:

   # CLAUDE.md

   This project uses `AGENTS.md` as its agent instruction file (kept provider-agnostic). Treat any `AGENTS.md` file exactly as you would a `CLAUDE.md` file — at the root level and in any subdirectory you are working in.

   @AGENTS.md

   1. frizlab · 1789767027 · focus · HN ↗

      If only there was a technology that existed to link files together… /s

      1. dinga · 1789767700 · focus · HN ↗

         The idea was to have it automatically detect nested AGENTS.md

         Does your tech do that?

         Anyway, the joke is on me I guess, because it might not work reliably.

         1. adastra22 · 1789772853 · focus · HN ↗

            CLAUDE.md is handled by the harness, not the agent.

            1. dinga · 1789773952 · focus · HN ↗

               I phrased it wrong. It was not about "automatically detect nested AGENTS.md". The idea was that when AGENTS.md files should be treated just like CLAUDE.md files in all subdirectories, when encountered.

               Anyway, with the change they announced, I can now simply delete my CLAUDE.md and everything will just work the way I wanted.

               Thanks for your clarification.

               1. adastra22 · 1789776841 · focus · HN ↗

                  What I meant is that the LLM isn’t the one that loads the agent file. It’s not trained to look for CLAUDE.md. It’s only training is to edit that file, and the harness does the magic of injecting it. So I would predict that with those instructions it rarely or only intermittently loaded AGENTS.md, but if you asked it to add a rule it would probably have put it on the right file.

Unofficial Hacker News client; not affiliated with Y Combinator.