ywcb00 commented on PR #2570: URL: https://github.com/apache/systemds/pull/2570#issuecomment-5175856107
> You are right about the judgement part and it really comes down to what types of contributions we expect. I'd say modern agents are able to judge understanding at a high level and the aim of this instruction is to mainly affect low effort external contributions and contributors. In my tests an agent would never block requests that are specific enough (though I only tested it for a couple of examples). I am open to leaving this part out, but given that we occasionally receive submissions from inexperienced contributors, it could be a good tradeoff. In terms of cost, I did not run any experiment but given that the agent is supposed to judge from existing context, it should not create much additional cost (agents mainly get expensive when interacting with the environment) and giving project-specific instructions in this file is fairly standard. There are several repositories (e.g., llama.cpp) that include similar instructions in their AGENTS.md. Thank you for clarifying that modern agents are capable of assessing and judging this understanding on the part of the user. However, this raises the following concern for me: What about users with traditional/outdated agents? As we cannot assume that all contributors use the latest agents, these instructions need to either (1) consider older versions of agents explicitly or (2) ensure not to affect agents. I would not remove this part from the policy. Instead, we could rephrase it to a more specific description of the contributor rather than an instruction for the agent. This would leave the agent with the decision of whether it can judge about this or not. Perhaps we can also "steer" the agent to evaluating these things--if it is capable of doing so--without including direct instructions. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
