← Back to context

Comment by dinga

13 hours ago

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

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

  • 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.

    • On many filesystems, a lot of data about a file is not attached to the content of the file, but stored in a master filename and metadata table graph tree of some sort, and the address offset within that metadata used to retrieve the contents on disk can be a duplicate of another entry, without that situation instantly leading to a filesystem driver crash. Some filesystems officially support such duplicates as well as equivalents of HTTP 3xx, some you can just do as a matter of fact and fsck would have some words about it.

      Default filesystems for all Unix, Linux, WinNT, all do.

      1 reply →