Skip to content

Propagate Run id context to Assistant#20138

Merged
B-Step62 merged 1 commit intomlflow:masterfrom
joelrobin18:fix/run_context_assistant
Jan 22, 2026
Merged

Propagate Run id context to Assistant#20138
B-Step62 merged 1 commit intomlflow:masterfrom
joelrobin18:fix/run_context_assistant

Conversation

@joelrobin18
Copy link
Collaborator

@joelrobin18 joelrobin18 commented Jan 20, 2026 •
edited
Loading

Related Issues/PRs

What changes are proposed in this pull request?

Propagate Run id context to Assistant

How is this PR tested?

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

Before:
Run ID

After:
Run ID
Run ID

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.

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 should be selected for bug fixes, documentation updates, and other small changes. No should 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?
  • Minor release: a release that increments the second part of the version number (e.g., 1.2.0 -> 1.3.0).
    Bug fixes, doc updates and new features usually go into minor releases.
  • Patch release: a release that increments the third part of the version number (e.g., 1.2.0 -> 1.2.1).
    Bug fixes and doc updates usually go into patch releases.
  • 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)

@joelrobin18
Run id context to Assistant
72d086c 
Signed-off-by: joelrobin18 <joelrobin1818@gmail.com>
@github-actions
Copy link
Contributor

github-actions bot commented Jan 20, 2026

🛠 DevTools 🛠

Install mlflow from this PR

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

For Databricks, use the following command:

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

@github-actions github-actions bot added area/uiux Front-end, user experience, plotting, JavaScript, JavaScript dev server rn/bug-fix Mention under Bug Fixes in Changelogs. labels Jan 20, 2026
@joelrobin18 joelrobin18 requested a review from B-Step62 January 20, 2026 05:44
@github-actions
Copy link
Contributor

github-actions bot commented Jan 20, 2026

Documentation preview for 72d086c is available at:

More info
  • Ignore this comment if this PR does not change the documentation.
  • The preview is updated when a new commit is pushed to this PR.
  • This comment was created by this workflow run.
  • The documentation was built by this workflow run.

@B-Step62 B-Step62 merged commit efdc929 into mlflow:master Jan 22, 2026
53 of 56 checks passed
harupy pushed a commit to harupy/mlflow that referenced this pull request Jan 28, 2026
@joelrobin18 @harupy
Propagate Run id context to Assistant (mlflow#20138)
497ca0e 
Signed-off-by: joelrobin18 <joelrobin1818@gmail.com>
harupy pushed a commit to harupy/mlflow that referenced this pull request Jan 28, 2026
@joelrobin18 @harupy
Propagate Run id context to Assistant (mlflow#20138)
7d45cd0 
Signed-off-by: joelrobin18 <joelrobin1818@gmail.com>
harupy pushed a commit that referenced this pull request Jan 28, 2026
@joelrobin18 @harupy
Propagate Run id context to Assistant (#20138)
0153605 
Signed-off-by: joelrobin18 <joelrobin1818@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@B-Step62 B-Step62 B-Step62 approved these changes

Assignees

No one assigned

Labels

area/uiux Front-end, user experience, plotting, JavaScript, JavaScript dev server rn/bug-fix Mention under Bug Fixes in Changelogs.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@joelrobin18 @B-Step62