# mlflow
pip install git+https://github.com/mlflow/mlflow.git@refs/pull/19842/merge
# mlflow-skinny
pip install git+https://github.com/mlflow/mlflow.git@refs/pull/19842/merge#subdirectory=libs/skinny

%sh curl -LsSf https://raw.githubusercontent.com/mlflow/mlflow/HEAD/dev/install-skinny.sh | sh -s pull/19842/merge

Related Issues/PRs

What changes are proposed in this pull request?

Enable the Scorers UI feature flags to make the scorers functionality available in the MLflow UI:

• enableScorersUI() - Enables the Scorers tab in experiment pages
• isRunningScorersEnabled() - Enables running LLM scorers on sample traces
• isEvaluatingSessionsInScorersEnabled() - Enables evaluating sessions in scorers

This change enables users to:

• View and manage scorers from the experiment page UI
• Run LLM scorers on sample traces
• Evaluate sessions using scorers

How is this PR tested?

• Existing unit/integration tests
• New unit/integration tests
• Manual tests

Manually verified the feature flags enable the Scorers tab and related functionality in the MLflow UI.

Does this PR require documentation update?

• No. You can skip the rest of this section.
• Yes. I've updated:
  • Examples
  • API references
  • Instructions

Release Notes

Is this a user-facing change?

• No. You can skip the rest of this section.
• Yes. Give a description of this change to be included in the release notes for MLflow users.

Enable the Judges UI in MLflow, allowing users to view and manage LLM judges.

What component(s), interfaces, languages, and integrations does this PR affect?

Components

• area/tracking: Tracking Service, tracking client APIs, autologging
• area/models: MLmodel format, model serialization/deserialization, flavors
• area/model-registry: Model Registry service, APIs, and the fluent client calls for Model Registry
• area/scoring: MLflow Model server, model deployment tools, Spark UDFs
• area/evaluation: MLflow model evaluation features, evaluation metrics, and evaluation workflows
• area/gateway: MLflow AI Gateway client APIs, server, and third-party integrations
• area/prompts: MLflow prompt engineering features, prompt templates, and prompt management
• area/tracing: MLflow Tracing features, tracing APIs, and LLM tracing functionality
• area/projects: MLproject format, project running backends
• area/uiux: Front-end, user experience, plotting, JavaScript, JavaScript dev server
• area/build: Build and test infrastructure for MLflow
• area/docs: MLflow documentation pages

How 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" section
• rn/breaking-change - The PR will be mentioned in the "Breaking Changes" section
• rn/feature - A new user-facing feature worth mentioning in the release notes
• rn/bug-fix - A user-facing bug fix worth mentioning in the release notes
• rn/documentation - A user-facing documentation change worth mentioning in the release notes

Should this PR be included in the next patch release?

• Yes (this PR will be cherry-picked and included in the next patch release)
• No (this PR will be included in the next minor release)

🤖 Generated with Claude Code