Appeng 4536 multi prompt/model factory#267
Conversation
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
84e151a to
026e556
Compare
There was a problem hiding this comment.
Hi @heatherzh01 @gnetanel @etsien , Good job all!.
There are still some gaps:
- Code Understanding sub-agent in the agent loop was left untouched ( with all of its components), means that if the gemma/granite models will be configured in agent config, it will still use the hardcoded prompts defined in code understanding sub-agent ( only tested on legacy Llama-3.1), So this is an inconsistency as some parts of the checklist items are being routed and dispatched to the code understanding sub-agent, and not to the reachability sub-agent. might not work well with conjunction to other parts and stages that are using the multi prompts factory prompts' based on the configured model in the agent configuration.
- The dispatcher component in the agent loop, which route a checklist item to the appropriate sub-agent, also stayed untouched.
Same meanings and consequences as the above.
-
RPM Analysis is exempted from this enhancement, worthwhile considering if there is a necessity in apply this multi prompt factory to the RPM Agent as a future enhancement in the future ( POST GA enhancement).
-
You should also make rebase on top of main, to resolve current conflicts, and also to catch up with month and half of new commits added to main, another testing cycle should be conducted afterwards.
-
Please see the rest of my comments in the code.
…endering (#235) Introduce a catalog-driven prompt resolver so vulnerability-analysis prompts can be selected and customized by prompt type, LLM family/version, and programming language without scattering template strings across callers. Co-authored-by: Gal Netanel <gnetanel@redhat.com>
…the module itself (#239) Co-authored-by: Gal Netanel <gnetanel@redhat.com>
…amily and version
… format and minor renaming not to clash language class with other common modules
…is being searched
includes a cursor .mdc file outlining the requirements, setup, and instructions for use (requires a corresponding exploitiq-tests-automation repo to be installed alongside)
It is not called though, because need to figure how to get llm info , see comments for info
A seperate commit has been created for the main branch. In multi prompt feature we generate prompt differently, so a fix is required in here as well.
Missing info is based on llama configuration, this is reflected in the string name that keep the prompt text
It is not called though, because need to figure how to get llm info , see comments for info
A seperate commit has been created for the main branch. In multi prompt feature we generate prompt differently, so a fix is required in here as well.
Missing info is based on llama configuration, this is reflected in the string name that keep the prompt text
Co-authored-by: Zvi Grinberg <75700623+zvigrinberg@users.noreply.github.com>
…db error, vdb disabled, etc.)
…default; document VDB decoupling
0ce5c55 to
0bcb7cf
Compare
…RHEcosystemAppEng/exploit-iq-agent into APPENG-4536_multi_promp_factory
|
/test-heavy |
zvigrinberg
left a comment
There was a problem hiding this comment.
@heatherzh01 @etsien Only 2 comments after this cycle of review...
After these, and UT + IT + default fallback confusion matrix results are good ( no regression on default for cm) We can merge.
…, add exception rules to summary
introducing multi-prompt factory with different configs for different models (gemma, granite, or llama), replacing previous single shared prompt for all models, each model get its own tailored prompts tuned to reasoning styles. Switching models only requires config changes, system will route to correct prompt catalog accordingly.