From d0aaf046736312fe3c7555586b54c185c6bc4c11 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E6=B2=88=E7=91=97=E6=9D=B0?= <3695888@qq.com> Date: Thu, 4 Sep 2025 13:51:48 +0800 Subject: [PATCH] Change DeepSeek max token count to 128k (#36864) https://api-docs.deepseek.com/zh-cn/news/news250821 Now the official API supports 128k token content and have modify the name to v3.1/v3.1 thinking Release Notes: - N/A --------- Co-authored-by: Ben Brandt --- crates/deepseek/src/deepseek.rs | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/crates/deepseek/src/deepseek.rs b/crates/deepseek/src/deepseek.rs index e09a9e0f7a19642253245b381abdc9fa05d0af00..64a1cbe5d96354260c2bf84a43ed70be7336aa7a 100644 --- a/crates/deepseek/src/deepseek.rs +++ b/crates/deepseek/src/deepseek.rs @@ -96,7 +96,7 @@ impl Model { pub fn max_token_count(&self) -> u64 { match self { - Self::Chat | Self::Reasoner => 64_000, + Self::Chat | Self::Reasoner => 128_000, Self::Custom { max_tokens, .. } => *max_tokens, } } @@ -104,7 +104,7 @@ impl Model { pub fn max_output_tokens(&self) -> Option { match self { Self::Chat => Some(8_192), - Self::Reasoner => Some(8_192), + Self::Reasoner => Some(64_000), Self::Custom { max_output_tokens, .. } => *max_output_tokens,