Feature hasn't been suggested before.
Describe the enhancement you want to request
Based on my testing, when using DeepSeek V4 (which only supports the OpenAI-compatible endpoint) with Claude Code CLI, the only viable integration method is protocol translation through a proxy. However, the protocol translation layer appears to be incompatible with DeepSeek.
This results in frequent tool-calling failures and related errors. I have also tested the official DeepSeek OpenAI-compatible endpoint, and the same issue occurs. In contrast, when using the Anthropic endpoint, tool calls work normally without any problems.
Other models seem unaffected by this translation layer. For example, I tested MiniMax and did not encounter similar tool-calling issues.
My question is: has anyone observed compatibility issues between DeepSeek's OpenAI-compatible endpoint and the protocol translation layer used by Claude Code CLI? If so, what is the root cause of these frequent tool-calling failures, and are there any known workarounds or configuration changes that can improve compatibility?
Feature hasn't been suggested before.
Describe the enhancement you want to request
Based on my testing, when using DeepSeek V4 (which only supports the OpenAI-compatible endpoint) with Claude Code CLI, the only viable integration method is protocol translation through a proxy. However, the protocol translation layer appears to be incompatible with DeepSeek.
This results in frequent tool-calling failures and related errors. I have also tested the official DeepSeek OpenAI-compatible endpoint, and the same issue occurs. In contrast, when using the Anthropic endpoint, tool calls work normally without any problems.
Other models seem unaffected by this translation layer. For example, I tested MiniMax and did not encounter similar tool-calling issues.
My question is: has anyone observed compatibility issues between DeepSeek's OpenAI-compatible endpoint and the protocol translation layer used by Claude Code CLI? If so, what is the root cause of these frequent tool-calling failures, and are there any known workarounds or configuration changes that can improve compatibility?