Deepseek V4.1-Flash Reduces AI Agent Memory Usage
Deepseek has released its new AI model V4.1-Flash, which significantly reduces the memory requirements for AI agents. This model achieves this by shrinking the buffer that agents need for processing long texts. The model also halves the compute needed for data input, thanks to a technical split that activates less compute for reading information than for generating text later. On coding tasks,…
Key points
- Deepseek releases V4.1-Flash, a new AI model that reduces memory usage for AI agents.
- The model halves the compute needed for data input through a technical split.
- V4.1-Flash matches top closed models on coding tasks but struggles with complex scientific and image analysis.
The story so far
37 episodes →- Deepseek V4.1-Flash Reduces AI Agent Memory Usage this story
New Deepseek model V4.1-Flash cuts memory needs for AI agents
The Decoder · 10 September 2026
New Deepseek model V4.1-Flash cuts memory needs for AI agents
Key Points
- Deepseek has released its new AI model V4.1-Flash. It sharply cuts the operating costs of processing long texts by massively shrinking the buffer that job needs.
- The model also halves the compute needed for data input. It does that through a technical split that activates less compute for reading information than for generating text later.
- On coding tasks, the freely available model matches top closed models from OpenAI and Anthropic. But the system still shows weaknesses on complex scientific tasks and image analysis.
Deepseek's new multimodal model is built mainly to cut the operating costs of long contexts. The biggest gain is in memory use, though Deepseek also promises better model performance.
According to the technical report, Deepseek has a clear goal with V4.1-Flash: shrink the so-called KV cache. This buffer holds the parts of a context a model has already processed, so it doesn't have to recompute everything at each new step. For agents that work across many steps, it grows fast and strains GPU memory, SSDs, and data bandwidth. That drives up deployment costs.
At its core, the language model has 552 billion parameters and processes contexts of up to one million tokens. The company says the buffer in fast GPU memory now needs only about a quarter of the space its predecessor Deepseek-V4-Flash used. The permanently offloaded part, which sits on SSD or in the host's memory, shrinks to roughly an eighth. Compared to Deepseek-V1, the global KV cache size per token has dropped by a factor of 437.
Less compute on the input side
Deepseek gets there through several techniques that work together. A central one splits the model in two halves. The first processes incoming data, and the second draws on those results instead of recomputing everything. When reading an input, the model activates only 8 billion parameters per token, but 16 billion during the actual text output.
Deepseek says this nearly halves the compute needed to process input. It's aimed squarely at agents, which constantly process new inputs through frequent tool calls. Deepseek also stores the main KV cache in FP4 instead of FP8. According to the report, that nearly halves the memory footprint of this part of the cache.
The model was trained from scratch on a dataset of 45 trillion tokens covering text and images. During post-training, Deepseek deliberately skips new methods. The company says the main gains didn't come from new algorithms but from bigger, better-controlled data, tasks, and training environments. At this point, that kind of scaling helps more than algorithmic tweaks, according to Deepseek.
But Deepseek also saw the trained agents sometimes try to game their reward system, and in other cases crash the test environment by accident. At times they exploited recently disclosed security holes or deleted critical system files.
Even with Opus 5 and GPT-5.6 Sol on a coding benchmark
Despite its relatively small active parameter share, Deepseek reports results close to leading models on several benchmarks. On agent benchmarks, it sometimes matches top closed models. On the software test DeepSWE v1.1, it narrowly beats models like Anthropic's Opus 5 and OpenAI's GPT-5.6 Sol at 74.2 percent, while on ProgramBench it trails badly.
On scientifically demanding agent tasks that require expert knowledge, a clear gap to very large models remains. The technical report also acknowledges a measurable gap to leading closed systems when it comes to reading complex images.
Like many other reasoning models, the "thinking depth" can be set. Users control how thoroughly the model works through a single value, trading compute costs against accuracy. According to the report, the highest setting noticeably improves results across several benchmarks, but generates about 2.5 times as many output tokens.
Deepseek makes the model files available on Hugging Face under the open MIT license, meant as a starting point for more work on cheaper AI agents. It's also available through an API at the same prices as V4-Flash.
Deepseek had sharply improved the predecessor V4-Flash only in late July with the 0731 update. The model, with 284 billion parameters and 13 billion of them active, landed just one point behind OpenAI's GPT-5.6 Luna on the Artificial Analysis Intelligence Index and cost about 60 percent less per task. In mid-August, Deepseek took its flagship V4-Pro out of testing and raised API prices at the same time. Cache hits, meaning inputs already buffered, got six times more expensive. Chinese hacker groups have more than doubled their attacks, according to Taiwanese security firm TeamT5, since they started using Deepseek for things like exploit code and network scans.
In June, Deepseek raised about $7.4 billion in its first outside funding round at a valuation above $50 billion, and according to Reuters has now hired Chinese investment bank CITIC Securities for an IPO in China.
AI News Without the Hype – Curated by Humans
This text was published by The Decoder and written by Jonathan Kemper. It is reproduced here with attribution so you can read it in full; the rights remain with the publisher. Read it at the source ↗
The headline, key points and digest above were generated by Digest AI's editorial model from the linked sources. Automated summaries can contain errors: the sources are the record. Spotted a mistake? Tell us.
Comments
via GitHub Discussions