mirror of
https://github.com/deepseek-ai/awesome-deepseek-agent.git
synced 2026-11-05 01:07:37 +00:00
[GH-ISSUE #36] 本地部署的deepseek v4 pro如何接入claude code #15
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#15
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 @BigBean666 on GitHub (Apr 30, 2026).
Original GitHub issue: https://github.com/deepseek-ai/awesome-deepseek-agent/issues/36
我已经成功通过代理连接到部署机器了,但是好像用不了模型?感觉是不是tool call 有问题,但我启动脚本里加了--enable-auto-tool-choice
@keydexofficial commented on GitHub (May 1, 2026):
或许你可以考虑一下Langcli的自定义模型 方法
https://langcli.com/cn/docs/model_providers
备注:Langcli的使用方法与claude code是完全一样的。
@Agents365-ai commented on GitHub (May 6, 2026):
Try https://github.com/Agents365-ai/dsclaude
use one script to start claude code with deepseek api key
@tianhao8687 commented on GitHub (Aug 17, 2026):
--enable-auto-tool-choice只解决“模型是否可以选择工具”,并不能让本地推理服务自动兼容 Claude Code 的通信协议。Claude Code 调用的是 Anthropic Messages API(
POST /v1/messages),而多数本地 vLLM/SGLang 部署默认暴露的是 OpenAI Chat Completions(POST /v1/chat/completions)。两者在请求结构、流式事件、tool_use/tool_result内容块以及 thinking 内容块上都不同。因此即使模型本身能 tool call,只提供 OpenAI endpoint 仍会失败。需要在本地服务前增加一个 Anthropic-compatible 适配层,并逐项确认:
POST <base>/v1/messages能返回 Anthropic Messages 结构;message_start、content_block_*、message_delta、message_stop;tool_use与tool_result能双向转换且 ID 保持一致;建议先用一个最小
/v1/messagescurl 请求验证适配层,再启动 Claude Code。若本地服务只打算保留 OpenAI 格式,改用原生支持 OpenAI-compatible Provider 的 Agent 会比强接 Claude Code 更稳定。