>Do you have example from JMeter gitHub? +1
>I've prototyped the adoption on a branch: it works cleanly with our GitHub >Issues, the dev@/private@ lists (via the ASF PonyMail archive), and the ASF >CVE tooling. Can you share the branch and the workflows Magpie improved? >I open a PR, I wanted to check with you: are the PMC and committers >OK with integrating Magpie (directly the Method 3 — git branch - main) ? Frankly, I am pessimistic regarding Magpie even though I am optimistic regarding LLM. If the changes are minimal, I won't object. If Magpie occupies the context window with stuff that LLMs already know by heart, then, well, that is just a waste of resources. --- I think we should add CLAUDE.md / AGENTS.md to explain JMeter specifics to agents. For instance, we have a build flag to configure "test jdk version". Agents should know it so they know the way to trigger tests with different JDK versions. Then, I think we should consider https://github.com/microsoft/apm for "agent package" (~skill) management. For example, I have a set of skills for creating English, French, and Russian texts (see https://github.com/Netcracker/qubership-ai-packages/tree/main/agent-packages ), and they would be helpful when creating/updating the translations. I do not think Magpie helps with that though. Vladimir
