Why you can't trust cloud API endpoints: 40 days of coding-agent telemetry showing the exact day providers silently overwrote deepseek-v4.1-flash with -1017 ("faster execution, shorter answers" = 3x more swearing and 6.7x more model switches)

Reddit r/LocalLLaMA News
model-update cloud-api telemetry coding-agent deepseek silent-overwrite versioning

Summary

作者分析本地编码代理40天的会话日志，发现云API提供商在10月17日发布了deepseek-v4.1-flash的-1017更新后于10月19日悄悄替换了模型权重，修复了中文泄漏并更激进地触发工具调用，但模型表现明显下降（爆粗率3倍、切换模型次数增加6.7倍），且由于是云端API无法回滚旧权重。

Around mid-October deepseek-v4.1-flash suddenly started feeling much dumber in my coding agent, so I parsed my local session logs to see when it broke. Before the update it had a funny quirk where it would randomly reply in Chinese while being 100% convinced it was speaking English. In the -1017 update (released Oct 17) they fixed the Chinese leak and made it fire tool calls more aggressively - and somehow lobotomized the model in the process. Providers silently overwrote the deepseek-v4.1-flash endpoint with the new weights by Oct 19. My swearing rate tripled, I ended up switching models mid-session 6.7x more often, and because it's a cloud API, there's no way to roll back to the old weights.
Original Article

Similar Articles

Why isn't the industry freaking out about DeepSeek 4.1 Flash?

Hacker News Top

作者基于一个月的重度使用体验，认为 DeepSeek 4.1 Flash 在编程任务上已与 Claude Opus 等前沿模型难以区分，但成本低几个数量级，业界却未因此震动。文章指出 KV 缓存缩减约 437 倍使全天会话成本不到一美元，预示便宜且'足够好'的中国模型正在改变开发者的工作方式。

@FuckAnthropic: Conducted a comparative analysis. Overall, DeepSeek V4 Flash-0731 is roughly a model at the level between Opus 4.7 and 4.8, entering the frontier Agent model competition with a minimal activation scale, and at about 1/12 to 1/60 of the token cost to enter the frontier Ag…

X AI KOLs Timeline

The author's comparative analysis concludes that DeepSeek V4 Flash-0731 achieves Opus 4.7–4.8 level performance with an extremely small activation scale, entering the frontier agent model tier at a very low token cost. It surpasses GLM-5.2 overall, but its shortfalls remain difficult repository-level coding and long-horizon engineering.

@NullableX: If this model's real-world experience turns out to be as good as the current benchmark data, it's actually a positive for the AI profitability side, not a negative. It's quite different from the "DeepSeek shock" on 2025/1/20 that broke the monopoly — the environment has changed, and the version is different. The three major cloud providers essentially connect downstream to large, medium, and small companies building AI apps and AI services at the application layer...

X AI KOLs Timeline

A commenter analyzes the release of DeepSeek-V4.1-Flash-1017 as a positive for the AI industry's profitability: improved token cost-efficiency will drive up AI penetration and demand for cloud providers' infrastructure. Unlike the earlier DeepSeek shock, market conditions have since changed.

@MaxForAI: Breaking: DeepSeek-V4-Pro-0813 was indeed the wrong model uploaded. Yesterday, when the community inspected the V4-Pro-0813 that DeepSeek uploaded to Hugging Face, they found a very unusual problem: the open-source model architecture exactly matched the previous V4...

X AI KOLs Timeline

The community discovered that the open-source model architecture of V4-Pro-0813 uploaded by DeepSeek to Hugging Face was actually V4 Flash. The repository was taken down and then re-uploaded, and the hashes and sizes of some safetensors weight files also changed, suspected to be a release/deployment error.