Add simulation_guidelines field to conversation simulation#20449
Merged
smoorjani merged 5 commits intomlflow:masterfrom Feb 11, 2026
Merged
Add simulation_guidelines field to conversation simulation#20449smoorjani merged 5 commits intomlflow:masterfrom
smoorjani merged 5 commits intomlflow:masterfrom
Conversation
Contributor
🛠 DevTools 🛠
Install mlflow from this PRFor Databricks, use the following command: |
bd57847 to
56f534d
Compare
Contributor
|
Documentation preview for 288a4d8 is available at: Changed Pages (2)
More info
|
xsh310
reviewed
Jan 30, 2026
xsh310
reviewed
Jan 30, 2026
mlflow/genai/simulators/simulator.py
Outdated
| persona: str | ||
| conversation_history: list[dict[str, Any]] | ||
| turn: int | ||
| simulation_guidelines: str | None = None |
Collaborator
There was a problem hiding this comment.
I'm reading this example in slack:
"simulation_guidelines": [
"In the first user turn, you should not specify any time period of your query.",
"In the first user turn, you should not specify whether you want percentages or absolutes.",
]
Do we prefer list of strings or strings for simulation_guidelines? And also in this example, I'm not sure the user agent directly have information of which turn is the current turn (maybe it is able to infer it from conversation history). But we need to worry about the case where guideline is specific to the turn number or other metadata?
Collaborator
Author
There was a problem hiding this comment.
Good call! I think list of strings makes most sense, but we can support str as syntactic sugar.
29 tasks
dbczumar
approved these changes
Feb 9, 2026
Collaborator
dbczumar
left a comment
There was a problem hiding this comment.
@smoorjani LGTM once:
- Comments are addressed
- We add an example of how to use this field to the MLflow GenAI docs
d2a608a to
5e71f29
Compare
Signed-off-by: Samraj Moorjani <samraj.moorjani@databricks.com>
- Add simulation_guidelines field to generate_test_cases distillation - Add guidance in simulator prompts clarifying guidelines describe user behavior, not assistant behavior (fixes role confusion) - Update distillation prompt to extract information withholding patterns, implicit expectations, and pacing from conversations Co-Authored-By: Claude <noreply@anthropic.com> Signed-off-by: Samraj Moorjani <samraj.moorjani@databricks.com>
Co-Authored-By: Claude <noreply@anthropic.com> Signed-off-by: Samraj Moorjani <samraj.moorjani@databricks.com>
Co-Authored-By: Claude <noreply@anthropic.com> Signed-off-by: Samraj Moorjani <samraj.moorjani@databricks.com>
8198bfa to
1167447
Compare
…st_cases description Co-Authored-By: Claude <noreply@anthropic.com> Signed-off-by: Samraj Moorjani <samraj.moorjani@databricks.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
3 participants
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.
Related Issues/PRs
#xxxWhat changes are proposed in this pull request?
How is this PR tested?
Does this PR require documentation update?
Release Notes
Is this a user-facing change?
What component(s), interfaces, languages, and integrations does this PR affect?
Components
area/tracking: Tracking Service, tracking client APIs, autologgingarea/models: MLmodel format, model serialization/deserialization, flavorsarea/model-registry: Model Registry service, APIs, and the fluent client calls for Model Registryarea/scoring: MLflow Model server, model deployment tools, Spark UDFsarea/evaluation: MLflow model evaluation features, evaluation metrics, and evaluation workflowsarea/gateway: MLflow AI Gateway client APIs, server, and third-party integrationsarea/prompts: MLflow prompt engineering features, prompt templates, and prompt managementarea/tracing: MLflow Tracing features, tracing APIs, and LLM tracing functionalityarea/projects: MLproject format, project running backendsarea/uiux: Front-end, user experience, plotting, JavaScript, JavaScript dev serverarea/build: Build and test infrastructure for MLflowarea/docs: MLflow documentation pagesHow should the PR be classified in the release notes? Choose one:
rn/none- No description will be included. The PR will be mentioned only by the PR number in the "Small Bugfixes and Documentation Updates" sectionrn/breaking-change- The PR will be mentioned in the "Breaking Changes" sectionrn/feature- A new user-facing feature worth mentioning in the release notesrn/bug-fix- A user-facing bug fix worth mentioning in the release notesrn/documentation- A user-facing documentation change worth mentioning in the release notesShould this PR be included in the next patch release?
Yesshould be selected for bug fixes, documentation updates, and other small changes.Noshould be selected for new features and larger changes. If you're unsure about the release classification of this PR, leave this unchecked to let the maintainers decide.What is a minor/patch release?
Bug fixes, doc updates and new features usually go into minor releases.
Bug fixes and doc updates usually go into patch releases.