News for hackers. Stuff that matters.
Re:Cursor CLI by fastball on Thursday August 07, 2025 @10:04PM (#44832655)
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.

Re:Cursor CLI by JamesSwift on Friday August 08, 2025 @09:48AM (#44836914)
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