Add HuggingFace chat model integration examples #1522
Merged
+38
−0
Conversation
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
This adds HuggingFace chat model integration examples to the chat-model-tabs.mdx snippet file. Includes: - Installation instructions for langchain[huggingface] - init_chat_model example with HuggingFace provider - Direct model class usage with HuggingFaceEndpoint and ChatHuggingFace - Uses microsoft/Phi-3-mini-4k-instruct as the example model Resolves issue #28226
lnhsingh
approved these changes
Nov 21, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Type: Update existing documentation
Related issues/PRs
Related to langchain-ai/langchain#28226
Description
Adds HuggingFace chat model integration examples to the chat-model-tabs.mdx snippet file.
Includes:
This provides users with a clear example of how to use init_chat_model with HuggingFace models, addressing the documentation gap mentioned in issue #28226.