6 ms·

I wonder when all of them will adopt AGENT.md and stop using gemini.md/claude.md/crush.md/summary.md/qwen.md https://agent.md https://agent.md [redirect -> htt

• js2 1y ago
  That's a more obvious (but less fun) name than what I've been using: ROBOTS.md with symlinks.
  • thehamkercat 1y ago
    https://ampcode.com/AGENT.md#migration https://ampcode.com/AGENT.md#migration they also suggest using symlinks for now
• sneak 1y ago
  When they stop getting desperate for differentiation by spamming their brand advertising in your repo against your will. Claude Code likes to add "attribution" in commit messages, which is just pure spam.
  • striking 1y ago
    You can turn it off: https://docs.anthropic.com/en/docs/claude-code/settings#available-settings https://docs.anthropic.com/en/docs/claude-code/settings#avai... `includeCoAuthoredBy: false`
    • arcanemachiner 1y ago
      5 years from now: Subscribe to the Ultra plan for the ability to prevent the LLM from putting ads for Coca-Cola into your code comments!
  • what 1y ago
    It’s not spam, it lets people know it was written by an LLM and maybe you should look closer at it.
  • computerfriend 1y ago
    I've experimented a little with LLM agents (only Claude Code). I definitely don't want the agent to write the commit messages (they should be written by a human as they're for human consumption) so I manually added the co-author trailer. It's morally correct to provide attribution.
    • CubicalBatch 1y ago
      I find LLM written commits are more often than not better than humans one
    • sneak 1y ago
      Code is also for human consumption. SICP contains the famous quote: “Programs must be written for people to read, and only incidentally for machines to execute.”
• prmph 1y ago
  Yep, that's a peeve of mine. I've resorted to using AGENT.md, and aliasing Claude, Gemini, etc to a command that calls them with an initial instruction to read that file. But of course they will forget after some time. The whole agentic coding via CLI experience could be much improved by: - Making it easy to see what command I last issued, without having to scroll up through reams of output hunting for context - Making it easy to spin up a proper sandbox to run sessions unattended - Etc. Maybe for code generation, what we actually need is a code generator that is itself deterministic but uses AI, instead of AI that does code generation.
  • thehamkercat 1y ago
    I think most of them provide an option to change the default file, but it'll be really good if they all can switch to AGENT.md by default Till then you can also use symlinks there are issues opened in some repos for this - Support "AGENT.md" spec + filename · Issue #4970 · google-gemini/gemini-cli https://github.com/google-gemini/gemini-cli/issues/4970#issuecomment-3125482368 https://github.com/google-gemini/gemini-cli/issues/4970#issu...
    • ximeng 1y ago
      https://github.com/anthropics/claude-code/issues/1091 https://github.com/anthropics/claude-code/issues/1091 Here for Claude
    • troupo 1y ago
      And then they should standardize on usage rules (an idea in Elixir space: https://hexdocs.pm/usage_rules/readme.html https://hexdocs.pm/usage_rules/readme.html )
  • manmal 1y ago
    In case you haven’t seen this, you can just pipe contents into Claude. Eg cat AGENT.md | claude IIRC this saves some tokens.
    • adastra22 1y ago
• irrationalfab 1y ago
  Thank you so much for this!
• ijidak 1y ago
  Agree. It's all English. That's the whole point of these tools. Why are we purposely creating CLI dialects?
• stillsut 1y ago
  Yeah I suspect some of these providers will become Microsoft in the '90s type bully holdouts on implementing the emerging conventions. But ultimately with CLI interface you have workarounds to all the major providers read in your system guidelines. But in an IDE - e.g. like MS had with VisualStudio - you more lock-in potential for your config files. Yesterday, I was writing about a way I found to pass the same guideline documents into Claude, Gemini, and Aider CLI-coders: https://github.com/sutt/agro/blob/master/docs/case-studies/aba-vidstr-2.md#adding-documentation-as-guides https://github.com/sutt/agro/blob/master/docs/case-studies/a...
  • rapind 1y ago
    Isn't think just a symlink?
    • mrits 1y ago
      I'm at a point where I symlink differnet sets of docs to try to focus context so much I feel like maybe I need a git submodule with different branches of context I want. I left managing people to now manage AI
• neuronexmachina 1y ago
  I really like the idea of standardizing on AGENT.md, although it's too bad it doesn't really work with the .cursor/rules/ approach of having several rules files that get included based on matching the descriptions or file globs in frontmatter. Then again, I'm not sure if any other agents support an approach like that, and in my experience Cursor isn't entirely predictable about which rules files it ends up including in the context. I guess having links to supplementary rules files is an option, but I'm not sure which agents (if any) would work well with that.
• dgunay 1y ago
  I just wish the AGENTS.md standard wasn't a single file. I have a lot of smaller context documents that aren't applicable to every task, so I like to throw them into a folder (.ai/ or .agents/) and then selectively cat them together or tell the agent to read them.
  • esafak 1y ago
    You can put them in subdirectories like CODEOWNERS files. https://ampcode.com/AGENT.md#multiple-agent-files https://ampcode.com/AGENT.md#multiple-agent-files
    • what 1y ago
      >When multiple files exist, tools SHOULD merge the configurations with more specific files taking precedence over general ones. How is the tool supposed to merge multiple md files?
      • esafak 1y ago
        The same way it synthesizes anything else. We're talking about LLMs here; this is their bread and butter.
      • yunohn 1y ago
        Most AI solutions make tracing the finally assembled prompt a bit difficult. However, if you look through the source code or network requests, you’ll see that merging just means naive “concatenation”.
  • troupo 1y ago
    Elixir has this idea with usage rules: https://hexdocs.pm/usage_rules/readme.html https://hexdocs.pm/usage_rules/readme.html
  • dotancohen 1y ago
    You could have a python script that generates the MD file on the fly, based on how you want to prompt the model. I think it's kind of funny, how deep we are getting with tools instructing tools instructing tools.
• bikeshaving 1y ago
  Every time I’ve ever read a {CLAUDE|GEMINI|QWEN}.md I’ve thought all this information could just be in CONTRIBUTING.md instead.
  • hahajk 1y ago
    Yes! I want an option to always add README.md to the context; It would force me to have a useful, up to date document about how to build, run, and edit my projects.
    • tyre 1y ago
      You can include in your prompt for it to read the README!
      • ______ 1y ago
        Ultimately if this stuff is actually intelligent it should be using the same sources of information that we intelligent beings use. Feels silly to have to have to jump through all these hoops to make it work today
      • adastra22 1y ago
        It’s a crapshoot of it actually does.
    • eru 1y ago
      > It would force me to have a useful, up to date document about how to build, run, and edit my projects. Not really: our AI agents are probably smart enough to even make sense of somewhat bad instructions.
      • yunohn 1y ago
        They’re definitely not, Claude and all other agents frequently forget the build and test commands present in CLAUDE/etc.md for my various repos (even though most of them were were initialized by the AI).
• stonecharioteer 1y ago
  Symlinks $AGENT.md to AGENT.md in your repo.
• anp 1y ago
  FWIW at least with Claude and Jules on a project I have a decent setup where I put all of the real content in an agents.md and then use “@agents.md” in CLAUDE.md. If all of the tools supported these kinds of context references in markdown it wouldn’t be that hard to have a single source of truth for memory files.
  • yougotwill 1y ago
    Same here each specific instruction file (vs code, cursor, etc.) just says read the AGENTS.md for instructions
• fastball 1y ago
  That sounds nice and I have the same pain, but not sure AGENT.md is the right abstraction either. After all, these models are indeed different and will respond differently even given the same prompting. Not to mention that different wrappers around those models have different capabilities. e.g. maybe for CURSOR.md you just want to provide context and best practices without any tool-calling context (because you've found it doesn't do a great job of tool-calling), while for CLAUDE.md (for use with Claude Code) you might want to specify tools that are available to it (because it does a great job with tool calling). Probably best if you have an AGENT.md that applies to all, and then the tools can also ingest their particular flavor in addition, which (if anything is in conflict) would trump the baseline AGENT file.
  • JamesSwift 1y ago
    Then lets do: AGENT.md AGENT.CLAUDE.md They get applied AGENT first, then AGENT.CLAUDE. You are able to specify agent specific instructions in the AGENT.md: @agent-disable CLAUDE These instructions are not parsed by claude @agent-enable CLAUDE
• ako 1y ago
  I asked claude code for a guidelines file so it would collaborate with windsurf. This is what it proposed: --- This project uses shared planning documents for collaboration with Claude Code. Please: 1. First read and understand these files: - PLAN.md - current project roadmap and objectives - ARCHITECTURE.md - technical decisions and system design - TODO.md - current tasks and their status - DECISIONS.md - decision history with rationale - COLLABORATION.md - handoff notes from other tools 2. Before making any significant changes, check these documents for: - Existing architectural decisions - Current sprint priorities - Tasks already in progress - Previous context from Claude Code 3. After completing work, update the relevant planning documents with: - Task completion status - New decisions made - Any changes to architecture or approach - Notes for future collaboration Always treat these files as the single source of truth for project state.
  • novaleaf 1y ago
    problem is that claude doesn't actually read those or keep them in context unless you prompt it to. it has to be in CLAUDE.md or it'll quickly forget about the contents
    • ako 1y ago
      I've added these instructions in CLAUDE.md and .windsurfrules, and yes sometimes you have to remind it, but overall it works quite well.
      • MrGreenTea 1y ago
        Habe you though about adding a Session start hook that reads this file and adds it to the context?
        • ako 1y ago
          Not yet, but that sounds like a good suggestion.
      • 1y ago
• zarzavat 1y ago
  Never. It's a marketing strategy. Some percentage of users will check these files into their repos, and some percentage of repo browsers will think "what is this X.md?" Given how much money people are spending on these things the value of having a unique filename must be enormous.
  • getflourish 1y ago
    Brand asset
  • drdaeman 1y ago
    It’s a marketing strategy that works here and now, but “never” is a very long time. What could be seen as pioneers claiming names today could be also seen as retrogressive stubbornness tomorrow and lose its marketing value.
    • dotancohen 1y ago
      There's a reason we still call the file robots.txt by that name, and not web-scraping.txt or search-engines.txt.
      • adobrawy 1y ago
        Yea, the reason is RFC9309.
        • dotancohen 1y ago
          That's actually a good point, but we have RFCs superceding RFCs all the time. My favorite RFC, 8601, superseded I think half a dozen other RFCs.
• pinoy420 1y ago
  [dead]
• stpedgwdgfhgdd 1y ago
  The deeper problem are the custom commands, hooks and subagents. The time has come that you need to make a strategic choice. Once you have heavily invested into CC, it is not easy to turn to an alternative. Side remark: CC is very expensive when using API billing (compared to e.g. GPT-5). Once a company adopts CC and all developers start to adapt to it at full scale, the bill will go out of the roof.
• asboans 1y ago
  Symlink?
• calmoo 1y ago
  The font on that RFC is aggressively squashed and aliased, why?
• ignoramous 1y ago
  Different file names is easy analytics (ex: 'how many OSS projects use gemini.md and claude.md' is a mere search query).
• leerob 1y ago
  (I work at Cursor) The CLI supports AGENT.md as well as CLAUDE.md and Cursor Rules.
• vmt-man 1y ago
  For example: i'm using Claude Code mostly + Gemini CLI. Gemini CLI is not such powerful as CC, also it won't work with some mcp's. So i have different *.md files.
• neuronexmachina 1y ago
  I haven't tried it yet myself, but I noticed their product page (https://cursor.com/cli https://cursor.com/cli) says: > Set your own rules: Customize Cursor's work with rules, AGENTS.md, and MCP. There's no mention of it in the docs, though. It's also interesting it's AGENTS.md on that page instead of AGENT.md, I wonder if that's a typo.
• enobrev 1y ago
  I think I'd be happier with a standard .agents directory and have all of these in there. I imagine each agent is going to need its own tweaks to get it to work just right with their system prompts, just as Claude already has it's project-specfic .claude directory for hooks and commands and whatnot. I'd rather .agents/claude or something so we can get these files out of the root directory, which, at least for typescript projects, is already a confetti-like jumble of json files for every little "simple" tool that needs its own configuration file. I get why package.json isn't enough. But would a .config directory standard really have hurt us so much?
  • augusto-moura 1y ago
    Ideally (and in practice, so far) they shouldn't change that much. The agent instructions should be close to a human explanation, and they are pretty good at parsing instructions anyway. In my experience you can symlink the same file to all paths and they work as expected.