NewFeather Wand
A JMeter plugin that adds AI chat and Agent Mode, with optional Jev routing to select a focused tool pack for a request.
Added to Jevfast
NewHow it uses Jev
When optional routing is enabled, the current request is classified before the selected chat model runs. Confident single-purpose requests receive a focused tool subset; complex, uncertain, or failed routing uses the full set. Separate optional triage analyzes failure summaries.
What Jev decides
Choose an initial JMeter Agent Mode tool familyExample answers · not a recorded Jev response · Source ↗
Question 1 · route
YOUR APP
INSTRUCTION
Choose the single best initial tool family. Choose COMPLEX_OR_UNCLEAR for multi-family, multi-stage, no-tool, or unsafe-to-focus requests.
STATE
The current sanitized user message and agent_mode=true are state. Six route options are fixed in the implementation.
JEV · CHOICE
- INSPECT_EXPLAIN
- EDIT_TEST_PLAN
- RUN_DIAGNOSE
- CORRELATE
- PLAN_FILES
- COMPLEX_OR_UNCLEAR
App workflow
- Enable optional Jev routing
With the feature enabled and configured, Agent Mode sends the current request for classification.
- Select tool pack
A confident single-purpose route gets a focused tool subset; uncertain, complex, or failed routing receives the full registry.
- Run Agent Mode
The selected chat model reasons, selects tool arguments, and executes tools. Jev does not bypass destructive-operation confirmations.
- Optionally triage failures
A separate opt-in triage path can classify test failure information for advisory display.
Why it is interesting
Jev narrows the available tool pack before a separate chat model acts, while leaving tool arguments, execution, and destructive-operation confirmations to that model and the existing safety flow.