This week on r/LocalLLaMA, a user shared a concrete scenario: running DeepSeek's newly released V4-Flash-0731 model on a long programming task, the model stops generating mid-way once the context (the amount of text the model can "see" at once) exceeds 100,000 tokens — no error, no crash, it just halts. Type "resume" in the command line and it continues normally.
What this is
This is a failure report from local deployment (running AI models on your own computer or server, rather than calling cloud APIs). DeepSeek is a leading Chinese large-model company; V4-Flash is its newest lightweight version, built around "small, fast, runs locally." The user was running the community (Unsloth) quantized version (a compressed model that fits on consumer GPUs) Q8_K_XL inside OpenCode (an open-source coding assistant).
The issue isn't the model getting answers wrong — it's "stopping dead." Past 100k tokens, manual "resume" hits are needed periodically to keep going. This isn't an isolated incident — "long-context instability" is a familiar old problem in open-source large models, but seeing it on a flagship vendor's new release shows local deployment maturity still has ground to cover.
Industry view
Pro-open-source voices argue this is precisely the value of open models: once a bug gets posted, authors and community can patch it within days, while closed-source failures leave you without even logs. Quantization teams like Unsloth typically follow up with optimizations.
But the counterargument is worth noting: a senior user in the comments pointed out that long-context stability's root cause isn't the model itself — it's the inference framework (llama.cpp and similar low-level software that actually runs the model) and the prompt caching mechanism (so models don't re-read the entire conversation history each turn, saving time and compute). In other words, the same bug could appear across different models; the underlying cause is infrastructure, not DeepSeek's fault.
The more honest read: this tells us the gap between "DeepSeek open-sourced another new model" and "you can actually run it reliably locally" is still wide.
Impact on regular people
For enterprise IT: Teams wanting AI on internal infrastructure for data protection will re-evaluate the total cost of "open-source model + self-built team" — human operational costs are often underestimated.
For individual professionals: Regular office workers needn't worry — this is developer-community territory. But if your company is evaluating "self-built AI," it's fair to ask: who owns long-task stability?
For consumers: Consumer-facing AI products (ChatGPT, Ernie Bot, and other cloud services) are unaffected — their server-side stacks carry heavy engineering optimizations. But the "local AI replaces cloud" narrative is further off than commonly claimed.