MLflow integration with GEPA optimize_anything#228
Merged
calreynolds merged 7 commits intodatabricks-solutions:mainfrom Mar 9, 2026
Merged
MLflow integration with GEPA optimize_anything#228calreynolds merged 7 commits intodatabricks-solutions:mainfrom
calreynolds merged 7 commits intodatabricks-solutions:mainfrom
Conversation
…ent-eval where an instance of claude code is ran to properly assess tool selection as well
…ing for per skill and tool call. Adjust this per eval. MLflow integration improvements
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The initial PR for using GEPA did not use claude code as a Agentic test. It was simply an LLM call with the loaded skill and then, the scorers would review if the output of that LLM was good or not. This was also difficult to debug without an integrated tracing capability. There were also issues with how the tools were being optimized since the code looked across all the skills and tested a single tool against every instance of skill. That plus multiple iterations and passes is very expensive.
What's in the PR
This PR address the following:
Test Plan.
You can run the following commands to test the new flags and optimizations. You will need to set the correct env variables according to the .test/README.md:
This one will optimize the sql tools
uv run python .test/scripts/optimize.py --tools-only --tool-module sql --reflection-lm databricks/gepa-fallbacks --judge-model databricks/gepa-fallbacks --preset quick --agent-eval --mlflow-experiment "/Users/austin.choi@databricks.com/GenAI/mlflow updates/AC updates dc-assistant-agent_experiment" --max-per-skill 2This one will optimize the databricks-metric-views
uv run python .test/scripts/optimize.py databricks-metric-views --reflection-lm databricks/gepa-fallbacks --judge-model databricks/gepa-fallbacks --preset quick --agent-eval --mlflow-experiment "/Users/austin.choi@databricks.com/GenAI/mlflow updates/AC updates dc-assistant-agent_experiment" --mlflow-assessments "/Users/austin.choi@databricks.com/GenAI/mlflow updates/AC updates dc-assistant-agent_experiment"Test plan