Internalize mbridge and remove megatron-bridge - #2251
Merged
Merged
Conversation
zhuzilin
force-pushed
the
zilin/merge_mbridge
branch
from
August 4, 2026 06:26
33441ce to
1619d57
Compare
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
1 participant
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.
At slime’s current stage of development, it remains difficult for us to support every model in a timely manner. We have therefore removed the experimental Megatron-Bridge integration, which was only partially implemented and did not meet our standards for code quality and maintainability. This allows us to keep the codebase cleaner and better organized.
Separately, we have decided to vendor the relevant parts of ISEEKYAN/mbridge directly into slime. Since the standalone MBridge project is being deprecated and its future development has moved to NVIDIA-NeMo/Megatron-Bridge, internalizing the functionality required by slime gives us clearer ownership and allows us to maintain it according to the project’s specific needs.
Special thanks to @ISEEKYAN for all the help and support so far.
For users who prioritize broader model coverage, we recommend trying radixark/miles.