Skip to content

Chinese Model provider#1131

Closed
wing (Malowking) wants to merge 4 commits intolangchain-ai:masterfrom
Malowking:model_provider
Closed

Chinese Model provider#1131
wing (Malowking) wants to merge 4 commits intolangchain-ai:masterfrom
Malowking:model_provider

Conversation

@Malowking
Copy link
Copy Markdown

feat(cli): add Qwen and DeepSeek model support via ChatOpenAI

Adds Qwen and DeepSeek model support using langchain_community.chat_models.ChatOpenAI base implementation. Extends model providers while maintaining existing functionality.

Fixes #ISSUE_NUMBER

Changes:

  • Added Qwen and DeepSeek to model providers
  • Implemented ChatOpenAI-based model creation
  • Added API key validation
  • Preserved backward compatibility

Verification:

  • make format and make lint passed
  • Tested model instantiation
  • Confirmed error handling works

No breaking changes.

@github-actions github-actions Bot added cli Related to `deepagents-cli` dependencies Pull requests that update a dependency file external User is not a member of the `langchain-ai` GitHub organization labels Feb 5, 2026
Copy link
Copy Markdown
Collaborator

@eyurtsev Eugene Yurtsev (eyurtsev) left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We want to support this by allowing folks to configure something like

--completions-api --base-url --api-key etc

rather than using a lot of specific env variables per provider -- since a lot of providers rely on the exact same conventions

Using the completions API will be basically unlock all models at once that rely on completions API compatibility

@mdrxy Mason Daugherty (mdrxy) added integration Partner or extension integration model Model provider or model config labels Feb 5, 2026
@Malowking
Copy link
Copy Markdown
Author

我们希望通过允许用户配置类似的功能来支持这一点

--完成 --基础-URL --api-key等

而不是每个供应商使用大量特定的环境变量——因为很多供应商依赖完全相同的约定

使用完备API基本上可以一次性解锁所有依赖完备API兼容性的模型

We want to support this by allowing folks to configure something like

--completions-api --base-url --api-key etc

rather than using a lot of specific env variables per provider -- since a lot of providers rely on the exact same conventions

Using the completions API will be basically unlock all models at once that rely on completions API compatibility

Even if we add this kind of configuration when starting the service, Google and Anthropic still have their own API invocation patterns. This means we would still need to add a lot of conditional logic to distinguish between the Completions API and other API styles.

If we introduce a .env file and switch to configuring the model through environment variables instead, the create_model method would only need to read parameters from the file, without requiring changes in many other places.

I’m not sure whether this approach is feasible, so I would greatly appreciate your advice. Thank you.

@mdrxy
Copy link
Copy Markdown
Member

Closing in favor of #1127

@Malowking wing (Malowking) deleted the model_provider branch February 9, 2026 06:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cli Related to `deepagents-cli` dependencies Pull requests that update a dependency file external User is not a member of the `langchain-ai` GitHub organization integration Partner or extension integration model Model provider or model config

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants