mirror of
https://github.com/deepseek-ai/awesome-deepseek-agent.git
synced 2026-11-05 01:07:37 +00:00
[GH-ISSUE #238] 【doc】Existing integration document issues / 现有对接文档问题 #85
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
deepseek-ai/awesome-deepseek-agent#85
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Small-tailqwq on GitHub (Jun 21, 2026).
Original GitHub issue: https://github.com/deepseek-ai/awesome-deepseek-agent/issues/238
关于 接入 Langcli 的对接文档，我注意到这是所有对接文档中唯一没有提到如何接入 deepseek 的文档了。我想请问这个 cli 是否支持 deepseek？为何没有写明相关对接流程？作为一个对接指南是否有点过于草率了呢？
另外作为对接文档，对第三方提供商（或者说中转商？）进行跳转的行为，出现在这里是否恰当，这是否会被用来当作背书？以上两点（没有 ds api 对接说明、包含第三方服务提供商）都是所有已收录文档中首次出现的问题，个人觉得最好是规范一下文档介入规范：应该出现什么、可以出现什么、避免出现什么。
en:
Regarding the integration documentation for 接入 Langcli, I noticed that this is the only integration document among all that does not mention how to integrate with deepseek. I would like to ask if this supports deepseek? Why isn't the relevant integration process clearly stated? As an integration guide, is it a bit too casual? Additionally, as an integration document, is it appropriate for the behavior of redirecting to third-party providers (or intermediaries?) to appear here? Could this be used as an endorsement? These two points—lack of ds api integration instructions and inclusion of third-party service providers—are issues that have never appeared in any of the previously included documentation. Personally, I think it would be best to standardize the documentation guidelines: what should appear, what can appear, and what should be avoided.