DeepSeek

DeepSeek's model releases, open weights and technical reports — the bellwether for open-model price and performance.

194 picksRelated topicsQwen Open source Model releases

Latest picks

161–180 of 194

May 4Monday

QbitAI · WeChatMay 4, 12:24

DeepSeek-TUI, a “DeepSeek Claude Code,” reaches 2.3k GitHub stars

DeepSeek-TUI reached 2.3k GitHub stars; the Rust project is MIT-licensed. It targets DeepSeek V4 with a 1M-token context, RLM up to 16 V4 Flash subtasks, MCP, Shell, Git, and three control modes. Watch cache misses: uncached tokens cost 10x cached tokens.

Why it matters: HKR-H/K/R all pass: the hook is a DeepSeek-flavored Claude Code, with 2.3k stars, 1M tokens, 16 subtasks, and a 10x cache-miss cost gap. Impact is developer-specific, so it sits in the 72–77 band.

Take

DeepSeek-TUI reached 2.3k GitHub stars in four months and wraps DeepSeek V4’s 1M-token context, prefix caching, and V4 Flash subtasks into a Rust TUI. My read is simple: this is less a “Claude Code clone” than an attempt to turn model pricing mechanics into product behavior. Its future depends on long-session reliability, sub-agent routing, and cache hit rates, not on how closely the README resembles Claude Code.

The feature list is broad: file edits, Shell, Git, web search, MCP, Skills, three control modes, session restore, and Git snapshot rollback. On paper, that matches the terminal-agent shape Claude Code popularized. But Claude Code’s edge is not just tool access. Anthropic has been tightening tool-call reliability, permission boundaries, task state, recovery loops, and the fit between Sonnet’s behavior and the UI. DeepSeek-TUI currently looks like a strong open-source interaction shell built around DeepSeek V4’s low cost and long context. That is a credible angle, but the failure mode is obvious: cheap model tokens do not automatically make cheap agents.

The RLM design is the important bit. A main model can dispatch up to 16 V4 Flash subtasks. That matches DeepSeek’s price profile well. The article says Flash output costs roughly one-third of Pro output, but it does not disclose input price, cache-hit price, context distribution, or a real task cost trace. I have doubts here. Parallel sub-agents can improve coverage and offload shallow work to cheaper models. They also create separate context branches, and those branches can destroy prefix-cache reuse. The article says uncached tokens cost 10 times cached tokens. That number matters more than the star count. It defines the product’s unit economics: savings come from stable prefixes; runaway cost comes from cache fragmentation.

I’ve long thought the post-2025 coding-agent divide is not “can it edit files?” It is whether the system can make state compression predictable. Cursor, Claude Code, OpenAI’s Codex CLI, Aider, and similar tools all hit the same wall: repository context is not better just because it is larger. Long context drags retrieval, attention, cache behavior, and cost into the same bottleneck. Gemini 1.5’s 1M-token window taught developers that long context is raw material, not product quality. DeepSeek-TUI defaults to filling V4’s 1M-token window. I understand the marketing value. I am not sure it is the right default. For many repos, stable indexing, symbol-level retrieval, incremental diff summaries, and disciplined prompt layout beat stuffing the window.

The smart mitigation is its compression strategy. The tool tries to preserve stable prefix content so DeepSeek’s prefix cache keeps hitting. That is a real engineering detail. Anthropic prompt caching, OpenAI cached-input pricing, and DeepSeek prefix caching all reward the same behavior: do not mutate the front of the prompt. A TUI agent naturally pollutes context. Users change goals, run Shell commands, paste logs, and branch tasks. The token stream gets messy fast. If DeepSeek-TUI can separate Git snapshots, session summaries, task plans, and tool output so the stable prefix stays stable, it is more than a UI wrapper. The article does not provide cache-hit curves or a one-hour coding-session cost sample. Without those numbers, the cost advantage remains a mechanism, not proof.

The open-source execution looks healthier. Rust, MIT license, prebuilt binaries for Linux/macOS/Windows, npm install, TUNA Cargo mirror support, Chinese README, and China-specific setup paths all fit DeepSeek’s community distribution pattern. The repo was created on January 19 and reached v0.8.8 after 37 releases. That is not a throwaway demo cadence. v0.8.2 fixed file-handle leakage in long sessions. v0.8.6 and v0.8.7 added retry countdowns for rate limits, input-history search, and running-message queue visibility. Those are user-pain fixes. Toy projects usually do not reach that layer this quickly.

I do not buy the “DeepSeek version of Claude Code” label without caveats. It drives clicks and sets the wrong expectation. Claude Code sits behind Anthropic’s model stack, product team, enterprise sales motion, billing system, and safety model. DeepSeek-TUI is an independent project. The detail that Claude authored more than 150 commits is funny and very 2026, but it also says this is still in the AI-assisted indie-tool category. It has not yet been validated across team workflows, private-repo permissions, audit logging, CI integration, enterprise proxies, or security review. YOLO mode that auto-approves Shell and file operations is great for personal hacking. Enterprise security teams will ask about sandboxing, secret redaction, command allowlists, and audit trails. The article does not disclose those protections.

Hunter Bown’s background makes for a good profile, but it does not carry the product case. Music, patent law, Shannon Labs, and “the Bell Labs of the AGI era” are narrative assets, not moats. What can matter is the depth of DeepSeek V4 adaptation: how it compresses 1M-token sessions, how RLM assigns work, how Flash and Pro switch, how cache misses are surfaced, and how MCP plus Git snapshots reduce damage. If the project ships reproducible benchmarks on the same repository and issue set, with success rate, human approvals, token cost, and cache-hit rate, it moves from GitHub heat to practitioner tool.

My stance is cautious-positive. DeepSeek-TUI is one of the first DeepSeek-native attempts to package cheap long-context models into a real coding-agent workflow. The 2.3k stars show demand, not Claude Code replacement readiness. If it keeps adding surface features, it will hit the same agent-tool swamp everyone else hits. If it treats cache cost and long-session reliability as first-class product metrics, it can become the DeepSeek ecosystem’s Aider-like tool. The key number here is not stars. It is the 10x price gap between cached and uncached tokens.

May 3Sunday

r/LocalLLaMAMay 3, 21:59

Local LLM Benchmark for Backend Generation via Function Calling: GLM vs Qwen vs DeepSeek

AutoBe posted a controlled backend-generation benchmark and says qwen3.5-35b-a3b matches gpt-5.4 on DB/API design. One shopping-mall run uses 200–300M tokens, costing $1,000–$1,500 per model at GPT 5.5 pricing. The key caveat is n=4 projects and self-scoring harness bias.

Why it matters: HKR-H/K/R all pass, but Reddit sourcing, n=4 projects, and self-eval harness bias keep it at the low featured band. Concrete cost and test constraints carry the score.

Take

qwen3.5-35b-a3b getting framed as near GPT-5.4 is interesting, but I would discount it hard. The useful hook is concrete: backend generation through function calling, DB/API design, and one shopping-mall task burning 200–300M tokens. At GPT 5.5 pricing, that lands around $1,000–$1,500 per model. This is closer to agent work than toy coding benchmarks.

The problem is the evidence shape. The Reddit page is blocked, and the summary says n=4 projects with a self-scoring harness. AutoBe judging DB/API design inside its own harness can easily measure fit to AutoBe’s workflow, not general model quality. The planned filter for models under $0.25/M or runnable on a 64GB laptop is the part practitioners can use. Open models can win on engineering economics; this does not prove GPT-5.4 parity.

QbitAI · WeChatMay 3, 11:16

DeepSeek V4’s biggest omission

DeepSeek V4’s technical report omits Engram while listing mHC, CSA, HCA, Muon, and FP4. Engram was open-sourced by DeepSeek and Peking University in January, inserting lookup modules between Transformer layers 2 and 15; its 27B test raised MMLU by 3.4 and Multi-Query NIAH to 97.0%. The engineering signal is CXL pooling: 8 servers shared a 4TB memory pool with under 5% throughput loss.

Why it matters: HKR-H/K/R all pass: the omitted-Engram angle is clickable, with layer ranges, benchmark deltas, and CXL memory-pool numbers. It is analysis, not the V4 launch itself, so 78–84 fits.

May 2Saturday

Hacker News front pageMay 2, 16:54

Show HN: Filling PDF Forms with AI Using Client-Side Tool Calling

SimplePDF released a Copilot demo that fills PDF forms via client-side tool calling; SimplePDF has 200k+ monthly users. PDFs stay in the browser, with parsing, rendering, and field detection local. The demo uses a DeepSeek V4 Flash proxy by default, with BYOK, cloud, or LM Studio options.

Why it matters: HKR-H/K/R pass: the client-side PDF-agent angle is specific, with a clear privacy mechanism and builder relevance. It sits in the 72–77 band as a useful product demo, not a major platform release.

May 1Friday

r/LocalLLaMAMay 1, 15:00

16x Spark Cluster Build Update

Reddit user Kurcide finished a 16-node DGX Spark cluster, with all nodes hitting line rate on the fabric. Each node uses one QSFP56 link to an FS N8510, showing 100–111 Gbps per rail and about 200 Gbps aggregate. The key angle is unified memory: 8 nodes served 434GB GLM-5.1-NVFP4, with DeepSeek and Kimi tests next.

Why it matters: HKR-H/K/R all pass: the post gives first-person cluster numbers, networking conditions, and a live 434GB model test. Scope stays local-inference hardware, so it fits the 72–77 band rather than a broader product-release tier.

Take

Kurcide built a 16-node DGX Spark cluster, with the summary claiming one QSFP56 link per node into an FS N8510, 100–111Gbps per rail, and about 200Gbps aggregate. Reddit returns 403 here, so I cannot inspect the original post, images, topology, NCCL settings, RDMA details, latency, throughput, or failure logs.

My read: do not file this under hardware flex. This is a clean example of the local inference crowd running straight into the memory wall. Sixteen DGX Spark boxes are not the story by themselves. The sharper detail is that 8 nodes reportedly served a 434GB GLM-5.1-NVFP4 model. That moves the conversation away from “can my workstation fit the weights” toward “can a small multi-node memory pool serve a huge model without falling apart.” That is a different class from the usual LocalLLaMA setups built around dual 3090s, quad 4090s, or a loaded Mac Studio.

I would be careful with the word “served,” though. The summary gives no tokens per second, no batch size, no context length, no time-to-first-token, and no KV-cache placement. For practitioners, those omissions matter more than line rate. A fabric hitting 100–111Gbps per rail tells us the network is not obviously broken. It does not prove the cluster behaves like a usable inference system. Large-model serving often dies on synchronization, small-message behavior, partitioning strategy, and tail latency, not on a clean peak-bandwidth screenshot.

The outside context is Nvidia’s own product direction. DGX Spark-like systems sit below H100/H200 training clusters. They sell the idea that developers can run serious models locally before going to cloud-scale infrastructure. Nvidia has been pushing that desk-side AI computer story through products like Project DIGITS, DGX Station-style machines, and Grace Blackwell-adjacent systems. The pitch is attractive: keep data local, iterate fast, avoid renting 8×H100 just to test a model. The catch is that cloud H100/H200 setups are not only about FLOPS. They come with mature networking, storage, schedulers, monitoring, replacement processes, and operators who have seen the failure modes before.

The 434GB GLM-5.1-NVFP4 detail is the part I would poke hardest. NVFP4 means this demo leans on a 4-bit-class path to make the model serviceable. The FP4/INT4 debate has moved past “does quantization work at all.” The practical question is now task-specific damage. Chat, summarization, and RAG often tolerate it. Code, math, long-context reasoning, and tool-heavy agents expose quantization errors faster. The summary says DeepSeek and Kimi tests are next, and those are better stress cases. DeepSeek-style models bring routing and reasoning pressure. Kimi brings long-context pressure. Those will say more than one GLM serving example.

I also do not fully buy the casual “unified memory” framing. Unified memory can sound like the VRAM wall disappeared. In practice, the wall often moves into interconnect, scheduling, and cache movement. Weights can be spread across nodes, but KV cache, attention traffic, expert routing, and batch packing still send the bill back. A 200Gbps aggregate interconnect is useful, but it is nowhere near box-level NVLink/NVSwitch behavior. At 200Gbps, you are around 25GB/s before overhead. H100-class NVLink bandwidth lives in the hundreds of GB/s per GPU range. That gap shows up whenever the model architecture needs frequent cross-device communication.

So I see this as an engineering boundary sample, not a production verdict. The useful question is whether a small team can use standard-ish switching and QSFP56 links to run models in the hundreds-of-GB range locally. The answer appears to be yes. The missing question is whether it is worth doing. The article body gives no total cost for the 16 DGX Spark nodes, no switch cost, no optics cost, no cabling cost, no power draw, and no utilization curve. Compared with renting H200 time or using hosted inference from providers like Together, Cerebras, Groq, or cloud GPU vendors, the economics are still unproven.

I would wait for the DeepSeek and Kimi follow-up, but not for another rack photo. Four numbers matter: tokens per second, TTFT, concurrent batch size, and context length. Add a 24-hour error rate and restart story. If Kurcide publishes those, this stops being a Reddit curiosity and becomes a useful reproducibility point for private small-cluster inference. Right now, the evidence is strong on fabric bring-up and memory ambition. It is still thin on serving quality.

Synced · WeChatMay 1, 13:01

The Evolution of RL: From PPO to MaxRL in LLM Reasoning Training

Jiqizhixin translated Alexander Weers' article on RL algorithms for LLM reasoning from 2024 to 2026. It covers REINFORCE, PPO, GRPO, RLOO, Dr. GRPO, DAPO, CISPO, MaxRL, DPPO, and ScaleRL, comparing critic removal, clipping, normalization, and pass@k goals. The key signal is mechanism choice, not algorithm names.

Why it matters: A strong technical explainer, not a model or paper release. HKR-H comes from the PPO→MaxRL arc, HKR-K from concrete mechanism comparisons, and HKR-R from live RL-recipe choices; the higher technical bar keeps it in low featured.

Apr 30Thursday

r/LocalLLaMAApr 30, 21:43

DeepSeek released Thinking with Visual Primitives framework

DeepSeek, Peking University, and Tsinghua released the Thinking with Visual Primitives paper and repository. The framework inserts coordinate points and bounding boxes into chain-of-thought; the post does not disclose benchmark scores.

Why it matters: HKR-H/K/R all pass: the hook is visual primitives inside reasoning, the new fact is point/box CoT plus an open repo, and the audience cares about grounded VLMs. No benchmark scores are disclosed, so it stays at 80, not P1.

Take

DeepSeek’s Thinking with Visual Primitives has the right instinct, but the public evidence is thin. It inserts coordinate points and bounding boxes into chain-of-thought, so a vision model must anchor reasoning to image regions instead of producing free-form explanations. That is useful for GUI agents, medical images, charts, and any workflow where failure needs a location.

The problem: the Reddit body is blocked by a 403, and the available summary gives no benchmark scores, training recipe, or supported VLMs. Coordinate-aware visual reasoning is not new; papers around visual CoT and referring expressions have circled this for a while. DeepSeek’s edge is the open repo plus Peking University and Tsinghua on the paper. Until MMMU, ChartQA, RefCOCO, or agent UI numbers show up, I read this as a strong interface idea, not proof of a multimodal reasoning jump.

Apr 29Wednesday

X · @op7418Apr 29, 21:59

Deepseek’s multimodal model is fully rolled out

Deepseek fully rolled out a multimodal model, available via the web image-recognition mode. The post says it looks like a separate model; it does not disclose name, size, pricing, or API timing.

Why it matters: HKR-H/K/R all pass, but the X post only confirms web image-recognition access; model name, params, price, and API timing are missing. DeepSeek’s multimodal rollout is strong, but the thin sourcing keeps it in 78–84.

Take

DeepSeek only exposed vision through the web image-recognition mode, while the API, pricing, model name, and size are blank. I don’t read this as a direct multimodal assault yet. R1 mattered because developers could reproduce the economics: weights, distillation, inference cost, and deployment paths. Here the only reproducible condition is “try it on the web,” and the post says it looks like a separate multimodal model.

That helps product usage, not developer gravity. GPT-4o-class and Gemini vision won because they sit behind APIs with latency, batching, tool calls, and billing that teams can wire into workflows. If DeepSeek keeps this inside the web UI, it is collecting demand and edge cases inside its own front end. The interesting read is cautious: test distribution and safety first, then decide whether vision deserves an API surface.

QbitAI · WeChatApr 29, 20:44

DeepSeek’s multimodal AI has entered testing

DeepSeek researchers confirmed V4 vision mode is in gray testing, with an image-recognition mode on the homepage. A screenshot shows it identified drinks and cup types in a non-text-heavy image after 4 seconds. The post does not disclose rollout scope, API access, or pricing.

Why it matters: HKR-H/K/R all pass: DeepSeek’s V4 vision gray test is a real domestic flagship update with a concrete 4s sample. Score stays at 80 because access scope, API form, pricing, and benchmarks are not disclosed.

r/LocalLLaMAApr 29, 12:39

DeepSeek V4 pricing is genuinely silly; the math made me question my stack

A Reddit user calculates DeepSeek V4-Pro input at $0.145 per million tokens, about 34x cheaper than Claude Opus 4.7. A May promo cuts it to $0.036, while cache hits are $0.0036, about 173x below Opus cached pricing. The key issue is agent-loop cost; the post does not verify the 1M context under production loads.

Why it matters: HKR-H/K/R all pass on the pricing hook, concrete token prices, and agent-cost pressure. Capped below 78 because this is a Reddit calculation, not an official release or production benchmark.

Computing Life · Share · YageApr 29, 08:00

DeepSeek V4 Explained: Engineering Decisions Around Agentic Workloads

DeepSeek V4 targets long-horizon agent tasks with a 1M context. The snippet cites hybrid attention, OPD, Muon, and mHC; the post does not disclose size, data, pricing, or release timing.

Why it matters: HKR-H/K/R all pass: DeepSeek V4, 1M context, and agentic workload engineering create a strong hook with concrete mechanisms. Missing params, data, price, and launch timing keep it at 78, not P1.

Apr 27Monday

QbitAI · WeChatApr 27, 11:47

DeepSeek V4 Cuts Prices Permanently; Cached Inputs Get 90% Off, Coding Test Costs Drop 83%

DeepSeek V4 cut prices twice in two days: input/output pricing is 75% lower, with cached inputs getting another 90% off. QbitAI’s coding test fell from 31.73 yuan for 35M tokens to 5.34 yuan under new pricing, an 83% drop. The key case is high cache-hit workloads, with V4-Pro at about 95–96% cache hits.

Why it matters: HKR-H/K/R all pass: DeepSeek V4 pricing has a sharp cost hook, concrete test numbers, and strong cost resonance. It is still a pricing update, not a new model release, so it stays below the 85 P1 band.

Take

DeepSeek V4 cut prices twice in two days, with 75% off input/output and another 90% off cached inputs. The article body is blocked by WeChat verification, so the original pricing table, billing rules, context length, and V4 versus V4-Pro differences are not disclosed. I would not treat this as a full launch readout. Still, the disclosed numbers point to a clear move: DeepSeek is pricing for long-context, repeated-call, high-cache coding workloads.

QbitAI says its coding test used about 35 million tokens. The bill dropped from 31.73 yuan to 5.34 yuan, an 83% reduction. If that test is clean, the number matters. Coding agents do not spend like chatbots. They reread the same repo files, dependency maps, tool schemas, test logs, and error traces across many attempts. A cache hit rate moving toward 95% changes the cost of retries. The summary says V4-Pro reached roughly 95–96% cache hits, which sits near the ideal zone for prompt caching on stable codebase context.

My read is that DeepSeek is using price to force a product architecture choice. Teams building coding agents often still resend repo summaries, file chunks, tool definitions, and logs on every loop. A 90% cached-input discount tells them to stop treating context layout as plumbing. Stable system prompts, stable tool schemas, pinned repo indexes, dependency graphs, and deterministic file ordering now affect gross margin. For agent infrastructure teams, cache-key design and context segmentation are no longer backend niceties. They are pricing mechanics.

The competitive angle is sharp. Anthropic’s Claude Sonnet line has owned a lot of serious coding-agent mindshare, and I remember Sonnet 4.5 pricing sitting around $3 per million input tokens and $15 per million output tokens, though I have not rechecked the latest table. OpenAI’s GPT-5 family also leans on mini and nano tiers for cheaper volume calls. DeepSeek’s move feels more like the Chinese cloud playbook: do not win the story first, win the workload spreadsheet. The question it asks customers is not whether one benchmark moves by two points. It asks who can run the same code task 100 times without finance killing the rollout.

I have real reservations about the 83% figure. The disclosed test comes from QbitAI’s summary, not a public DeepSeek invoice in the body we can inspect. We do not get repo size, task type, number of turns, retry count, cache warmup method, or whether the same files were reused heavily. If the workload was built around stable repeated context, a 95% hit rate says less about messy daily development. In real enterprise repos, branches change, CI logs refresh, generated files move, and agents reorder snippets. Multi-agent systems make this worse. Tiny changes in tool schema versions or context assembly can break cache reuse. Since the article body does not disclose those conditions, I would treat the 83% drop as an upper-bound case for cache-friendly workloads.

The word “permanent” also deserves skepticism. China’s model vendors already ran brutal price cuts, and many promo prices later became normal prices. Sustaining them requires actual inference-cost improvements. If DeepSeek can keep cached-input pricing at another 90% discount, it either has strong confidence in KV-cache reuse, batching, routing, and memory economics, or it is accepting margin pressure to pull developers over. Those are very different stories. The available text does not give enough evidence to choose between them.

For practitioners, the action item is plain: replay your own traces. If you run code review, test generation, migration tooling, documentation sync, or knowledge-base agents with stable repeated context, DeepSeek V4’s new pricing can change unit economics now. If your workload is one-off reasoning, fresh long-form queries, or low-reuse tool calls, the headline discount will not show up the same way. Do not benchmark the discount from the marketing number. Measure stable cache hit rate across real retries. If it cannot stay above 90%, the bill will not fall by 83%.

Apr 26Sunday

Hacker News front pageApr 26, 07:44

DeepSeek-V4 on Day 0: From Fast Inference to Verified RL with SGLang and Miles

SGLang and Miles added day-0 inference and RL support for DeepSeek-V4, covering 1.6T Pro and 284B Flash. The post cites a 1M-token context, FP4 MoE expert weights, 128-token SWA, and 4:1 or 128:1 KV compression. The key systems detail is ShadowRadix coherence across three KV pools and two compression-state pools.

Why it matters: HKR-H/K/R all pass: a DeepSeek-V4 day-0 systems stack, concrete context/compression mechanisms, and clear deployment-cost stakes. The systems depth narrows reach, but no hard-exclusion rule is triggered.

Apr 25Saturday

Latent SpaceApr 25, 13:00

DeepSeek V4 Pro and Flash released, runnable on Huawei Ascend chips

DeepSeek released V4 Pro and V4 Flash, with 1.6T/49B active and 284B/13B active parameters. Both support 1M-token context, Base/Instruct variants, and an MIT license; the report claims 27% FLOPs and 10% KV cache versus V3.2 at 1M tokens. The key point is Huawei CANN compatibility, not just benchmarks, because it reduces CUDA dependence.

Why it matters: HKR-H/K/R all pass: a major DeepSeek release adds concrete specs, 1M context, MIT licensing, and Huawei Ascend support. This sits in the 85–94 must-write band, with hardware independence pushing it upward.

MIT Technology Review · AIApr 25, 05:40

Three reasons why DeepSeek’s new model matters

DeepSeek released a V4 preview with two versions: V4-Pro and V4-Flash. V4-Pro costs $1.74/M input tokens and $3.48/M output tokens; V4-Flash is about $0.14/$0.28, and both support 1M-token context. The key point is attention efficiency and open weights pressuring agentic coding costs.

Why it matters: HKR-H/K/R all pass: DeepSeek V4 is a domestic flagship release with 1M context, two price tiers, and open-weight cost pressure. The preview status keeps it below a full GPT/Claude major release, but it is same-day material.

Take

DeepSeek released a V4 preview with Pro and Flash tiers. My read is simple: this will not hit like R1, but it will move the cost floor for agentic coding. V4-Pro costs $1.74 per million input tokens and $3.48 per million output tokens. V4-Flash is about $0.14 and $0.28. Both support a 1M-token context window. That package matters more than another benchmark table, because coding agents burn tokens on repos, logs, tool traces, tests, and patch iterations.

MIT Technology Review frames the release around open weights, long-context efficiency, and Chinese chips. The article discloses pricing, API access, web and app availability, and the split between V4-Pro for coding and complex agent tasks and V4-Flash for speed and price. The body we have cuts off during the benchmark section. It does not give complete scores, test sets, comparison models, or degradation curves at long context. So I would not buy the “rivals the best models” line yet. DeepSeek earned attention with R1, but company-run benchmarks are still company-run benchmarks. SWE-bench, Aider polyglot, LiveCodeBench, long-context retrieval, and repo-level bug fixing need independent reruns.

The pricing is the hard part already on the table. I remember Anthropic Claude Sonnet 4.5 landing around $3 per million input tokens and $15 per million output tokens, though I have not rechecked that exact figure. OpenAI’s higher-end lines have also kept long context and tool use in premium territory. V4-Pro at $1.74 and $3.48 is aggressive, especially on output. Coding agents produce a lot of output: plans, diffs, test logs, explanations, retries. Dropping output from the $15 range to $3.48 changes the economics of batch repo work. Flash at $0.14 and $0.28 reads like a sub-agent model for summarization, retrieval compression, test explanation, and first-pass review. That pattern already shows up in Cursor-style and Devin-style stacks: a stronger model handles hard decisions, cheaper models chew through scaffolding.

The 1M-token context window also needs a colder read. The hard part is not accepting 1M tokens. The hard part is using them. Gemini 1.5 Pro made million-token context a public product story long before this, and OpenAI and Anthropic have pushed high-context tiers too. Developers pay for effective context, not advertised context. If V4 lowers attention cost but loses cross-file constraints after 600K tokens, its coding-agent value drops fast. The article says DeepSeek uses a new design for efficient large-text handling. It does not disclose whether that means MLA, sparse attention, block memory, or another mechanism. That missing detail matters because open weights become much more valuable when the community can optimize the inference stack around the architecture.

I am also careful with the “open source” wording. MIT says the model is open source and available to download, use, and modify. In AI, that phrase often blurs four separate things: open weights, open training code, open data, and permissive commercial licensing. R1’s impact came from weight availability and method diffusion, not a fully open training pipeline. If V4 only ships weights and a technical report, enterprises still need to inspect the license, compliance posture, data provenance, and distillation restrictions. The article mentions scrutiny from both the US and Chinese governments. Regulated buyers will not move sensitive workflows because input tokens cost fourteen cents per million.

The Chinese-chip angle needs even more caution. The headline says V4 is a win for Chinese chipmakers. The visible body only says R1 was trained with limited compute and that V4 is more efficient. It does not disclose V4’s training hardware, inference hardware, cluster size, HBM configuration, or domestic accelerator share. If the gain comes from architecture and inference engineering, it does help Huawei Ascend, Cambricon, Moore Threads, and similar ecosystems. Lower attention cost matters more when bandwidth and interconnect are constrained. But “helps the ecosystem” is not the same as “runs production 1M-context workloads on domestic chips today.” We are missing reproducible conditions: batch size, KV-cache strategy, throughput, latency, memory footprint. None of those are in the article body we received.

The part I care about is that DeepSeek is shifting the open-model fight from “can it reason?” to “can it remember a lot cheaply?” R1 pressured the reasoning premium. V4, if independent tests hold up, pressures the default use of closed APIs inside agent workflows. Internal codebases are the obvious wedge. Plenty of teams would rather self-host open weights than send entire repos, tickets, logs, and design docs to an external API.

Still, I would not declare another DeepSeek shock yet. R1 landed because two things were true at once: capability was close enough, and cost was dramatically lower. V4 has clearly shown the second condition. The first still depends on third-party evals and real agent traces. My test would be brutal but fair: give V4-Pro a million-token monorepo, a bug spanning 20 files, failing tests, and noisy logs. Make it patch, rerun, diagnose failures, and preserve style. If it gets near Claude Sonnet 4.5 while costing under one-third as much, closed coding-agent pricing has a real problem.

Bloomberg TechnologyApr 25, 00:18

China’s DeepSeek Unveils New Model a Year After Shock Launch

DeepSeek unveiled a new flagship AI model about one year after its open-source release jolted Silicon Valley. The title and RSS snippet confirm that timing; the post does not disclose the model name, size, pricing, benchmarks, or release terms. The key thing to watch is the missing launch detail, not the comeback framing.

Why it matters: A new DeepSeek flagship is newsworthy: HKR-H comes from the 'one year after the shock launch' hook, and HKR-R from the open-source and pricing rivalry it triggers. HKR-K fails because no model name, params, pricing, or benchmarks are disclosed, so this sits at the low end of the

Take

DeepSeek unveiled a new flagship model about one year after its breakout open release, and the article discloses almost nothing else. My read is simple: this is not yet evidence of a capability jump. It is only a product signal waiting for verification. The headline wants the “DeepSeek is back” story. I care far more about what exactly is back: stronger reasoning, lower token pricing, looser release terms, or just another round of attention.

Look, the force of DeepSeek’s last breakout was never benchmark score alone. It hit because the package was unusual: open weights, aggressive cost claims, deployability, and a Chinese lab forcing Silicon Valley to respond on efficiency instead of sheer spend. That wave also fed into a broader open-model reset. Qwen kept gaining ground, Meta had to keep defending Llama’s practical value, and every frontier lab got dragged back into the question of whether “closed but better” was still enough. If DeepSeek is launching another flagship, the missing details are the whole story. We still do not have the model name, parameter count, architecture, context window, API pricing, benchmark table, or license terms. Without those, nobody serious can tell whether this is aimed at OpenAI and Anthropic on frontier quality or aimed at everyone else on cost-performance.

I also have some pushback on Bloomberg’s framing. Centering the “shock launch” narrative is good TV, but it risks turning this into nostalgia. New models earn relevance through reproducible conditions, not vibes. If DeepSeek is claiming coding gains, show SWE-bench or LiveCodeBench and the test setup. If it is a price attack, publish input and output rates plus throughput. If it is another open release, say whether weights are actually downloadable and what commercial restrictions apply. Over the last year we have seen plenty of launches that looked huge on day one and then faded once deployment details showed up. I treat any first report that skips those details with caution.

I have not found primary launch materials yet, so I would keep this marked as incomplete. DeepSeek did ship something. That much is clear. What is still unclear is whether this resets the open-model frontier again or just fills a product gap while the market waits for hard numbers.

Apr 24Friday

TechCrunch · AIApr 24, 21:30

DeepSeek previews new AI model that ‘closes the gap’ with frontier models

DeepSeek previewed two new models and said architectural changes make them more efficient and higher-performing than DeepSeek V3.2, while nearly closing the gap with leading models on reasoning benchmarks. The RSS snippet discloses only that there are two models and that they outperform V3.2; model names, parameter counts, benchmark scores, test sets, and release timing are not disclosed. The key question is reproducible evals, because “closes the gap” comes without numbers.

Why it matters: A new-model preview from DeepSeek, a flagship Chinese lab, clears HKR-H and HKR-R on competitive relevance alone. HKR-K is weak because the story gives only 'two models' and 'better than V3.2' while model names, benchmark scores, test sets, and release timing are not disclosed,so

Take

DeepSeek disclosed 2 upcoming models and attached one loaded phrase: they “almost close the gap” with frontier systems on reasoning. I read that as a narrative grab, not a result drop. The body gives only two facts: architectural changes made both models more efficient and better-performing than DeepSeek V3.2, and they are near current leaders on reasoning benchmarks. It does not disclose model names, parameter counts, active parameters, context length, benchmark names, evaluation setup, or release timing. Without that, nobody can tell whether this is a real step-function or just careful wording around a narrow eval slice.

My prior on DeepSeek is that its importance has never been just “good scores.” It has been cost-adjusted capability. The last time DeepSeek broke through, the story was not that reasoning suddenly existed outside US labs. The story was that an open or semi-open stack pushed the performance-per-dollar curve hard enough to force everyone else to defend pricing. If these new architectural changes mostly translate into lower inference cost, higher throughput, or better test-time compute efficiency, that matters more than the vague frontier claim. But TechCrunch’s snippet gives none of the numbers that would prove that: no tokens per second, no serving footprint, no API pricing, no hardware assumptions.

I’m also skeptical of the phrase “closed the gap” on reasoning benchmarks. Reasoning evals are easy to dress up now. Which benchmark? Was there majority voting? Tool use? Long deliberation budgets? Self-consistency? Frontier labs spent the last year showing how much results move when you change inference-time compute. So “near leading open and closed models” is not a stable statement unless DeepSeek names the comparison set. Near GPT-5 or near a smaller frontier SKU? Near on math, code, or long-horizon agent tasks? Only the headline-level claim is disclosed so far.

The outside context here is simple: DeepSeek has already trained the market to expect aggressive efficiency moves, not just benchmark theater. That is why this teaser matters at all. If this turns into reproducible evals plus aggressive API pricing, it pressures every vendor selling “good enough reasoning” at a premium. If it stays at teaser level, then it was just a reminder shot to keep DeepSeek in the same sentence as OpenAI, Anthropic, and Google.

Honestly, I want two artifacts before taking the claim seriously: a benchmark table with conditions, and a cost/performance story that survives independent testing. Until then, this is a positioning move with upside, not evidence.

The Verge · AIApr 24, 17:45

China’s DeepSeek previews new AI model a year after jolling US rivals

DeepSeek released a preview of its open-source V4 model on Friday and said it can compete with closed systems from Anthropic, Google, and OpenAI. The RSS snippet says V4 improves coding and highlights compatibility with Huawei tech; parameter count, benchmark scores, and rollout details are not disclosed. The part to watch is the pairing of agent-focused coding gains with tighter alignment to China’s domestic chip stack.

Why it matters: This is a flagship Chinese model update with HKR-H/K/R: a new open-source V4 preview, coding gains, and Huawei compatibility. It stays below the 85 band because the story withholds params, benchmark scores, and launch timing.

Take

DeepSeek released a V4 preview on Friday and explicitly framed it against Anthropic, Google, and OpenAI. My read is pretty direct: the heavier signal here is not “open source is catching closed source,” but that DeepSeek is now publicly tying its model roadmap to China’s domestic compute stack, with Huawei compatibility elevated into the first-wave narrative.

The actual information is thin. Parameter count is undisclosed. Benchmarks are undisclosed. Commercial timing is undisclosed. Even the coding improvement claim lacks a metric: no HumanEval, no SWE-bench, no internal task details. So I don’t buy the competitiveness claim on faith. What we can say from the snippet is narrower: DeepSeek sees coding as the front door for agents, and it wants the market to read V4 together with Huawei Ascend.

That context matters. Over the last year, OpenAI pushed Codex back into the workflow conversation, Anthropic turned Claude Code into a serious developer wedge, and Google kept steering Gemini toward code-centric agent use cases. Coding is no longer a prestige benchmark. It is the shortest path to an agent that touches an IDE, edits a repo, runs tests, and loops on tools. DeepSeek leading with coding tells me it is aiming at a practical insertion point: win developer workflow first, then argue broader capability parity later. I think that is the right battlefield. Plenty of teams learned that “better at code” monetizes faster than “better at chat.”

The Huawei line is the more strategic piece. A lot of Chinese model vendors spent the past year talking about domestic chip adaptation, but much of that language stayed at the engineering layer: portable, deployable, some operators adapted, partial stack support. DeepSeek putting compatibility near the center of a V4 preview says something stronger. It suggests the company wants to show that next-gen model progress no longer depends on Nvidia as the only credible substrate, at least not in public positioning. For the China market, that matters a lot. If your best model only runs well on H100, H200, or B200-class Nvidia infrastructure, open weights alone do not solve supply or policy constraints.

I do have a pushback here: “compatible with Huawei” can mean almost nothing, or it can mean a lot. There is a huge gap between a model that runs and a model that runs efficiently enough for real deployment. Throughput, memory efficiency, long-context stability, MoE routing overhead, compiler maturity, inference serving quality, and toolchain reliability decide whether enterprises scale it. The article gives none of that. No tokens per second. No cluster size. No cost curve. No deployment references. Without those numbers, I would not read this as proof that the Chinese stack has closed the gap. It reads as a declaration of direction.

I also think the headline framing risks overstating the wrong part. DeepSeek’s earlier shock effect was never just about raw model quality. It came from the combination of cost claims, open distribution, engineering credibility, and pressure on pricing assumptions. If V4 wants to repeat that, “we can compete with closed models” is not enough. It needs reproducible evidence, release timing, and deployment economics. Meta’s Llama waves spread because developers could get their hands on them quickly and test the claims. If DeepSeek delays weights or benchmark detail for too long, attention will outrun trust.

There is also a domestic comparison that matters more than the US rivalry framing. Alibaba’s Qwen line has been aggressive on open-source distribution, multilingual support, coding, and tool use, and its ecosystem reach is hard to ignore. So if DeepSeek wants V4 to become the default Chinese open model base, the competition is not only OpenAI and Anthropic at the frontier. It is also Qwen and other local stacks with better deployment familiarity and wider integrations.

So I would file this as a strategic positioning update, not confirmed model leadership. The clearest thing V4 has shown so far is not benchmark superiority. It is that DeepSeek is packaging code agents and domestic chips into one story. That story becomes credible only when three missing pieces show up: coding evals, real Ascend-side performance numbers, and a concrete open release schedule. Until then, this is a smart preview, not a settled result.

r/LocalLLaMAApr 24, 13:34

DeepSeek releases V4: 1.6T Pro, 284B Flash, MIT license, 1M context

DeepSeek released two open-weight V4 models: Pro at 1.6T total with 49B active, and Flash at 284B total with 13B active; both use an MIT license and support 1M context. The RSS snippet points to a Hugging Face collection and a tech report, but the post does not disclose benchmark scores, pricing, training data size, or real inference throughput. The key thing to watch is the 1M context plus low active-parameter ratio; if evals hold, self-hosted long-context and routing economics change materially.

Why it matters: HKR-H/K/R all pass: this is a flagship DeepSeek open release with two huge MIT-licensed weights and 1M context, strong enough for same-day coverage. The score stops at 86 because the provided text does not disclose benchmarks, throughput, training data, or pricing.

Take

DeepSeek’s release matters because it combines three levers that usually refuse to line up: 1M context, low active-parameter counts, and an MIT license. My read is that this is less about headline scale and more about taking long-context work out of the premium API bucket and moving it back into downloadable infrastructure. If that holds in real workloads, budget math changes before benchmark leaderboards do.

The information gap is still large. The post gives us Pro at 1.6T total parameters with 49B active, Flash at 284B with 13B active, and both models at 1M context under MIT. It does not give benchmark tables, training token counts, post-training details, inference throughput, KV-cache strategy, or long-context quality curves. The Reddit body says a tech report exists in the Hugging Face repo, but this material does not surface those details. So no, this is not enough to declare a clean win yet.

What stands out to me is not the 1.6T total parameter number. Total params are headline bait in MoE land. The sharper signal is 49B active for Pro and 13B active for Flash while claiming 1M context. Open-weight model builders have spent the last year trying to make “huge” models look economically normal at serving time. DeepSeek has been good at that framing before. If V4 keeps quality intact at those active sizes, it hits two practical use cases hard: private deployments over giant internal corpora, and routing stacks that currently hand off long prompts to Claude or Gemini because open models lose coherence or become too expensive when sequence length explodes.

I’m still wary of the “1M context” label. In this market, paper context and usable context are often different products. Plenty of models stretch RoPE scaling, interpolation, or related tricks and suddenly advertise 256K, 512K, or 1M. The problem is that retrieval accuracy, constraint tracking, and cross-document consistency often degrade badly long before the stated ceiling. We saw this pattern repeatedly over the last year: fine on synthetic needle tests, shaky on real codebases, legal archives, or long agent traces. Until I see a curve that shows where performance starts to break, I treat 1M as a capability claim, not an operating fact.

The same caution applies to the “49B active means cheap inference” story. That is only half true. MoE absolutely reduces per-token dense compute, and 49B or 13B active is an aggressive ratio. But at 1M context, cost is not just about FLOPs. KV cache can dominate memory pressure. Multi-GPU communication can erase theoretical efficiency. Prefill latency becomes painful. Expert routing and all-to-all traffic can get ugly in production. So low active params do not automatically mean low serving cost for long-context jobs. Whether this is actually economical depends on the attention implementation, cache management, quantization behavior, and parallelism strategy. None of that is disclosed here.

The MIT license is the part I take very seriously. A lot of people will stare at the parameter counts and miss the legal layer. Open weights under research-only or restrictive commercial terms stay stuck in evaluation purgatory. MIT removes a big chunk of that friction. Llama’s adoption was always stronger than its license comfort level; legal teams kept asking for escape hatches. If DeepSeek is now putting a top-tier long-context candidate under MIT, that is not just good community optics. It gives private-cloud vendors, integrators, and vertical SaaS teams permission to build default offerings around it. That tends to matter longer than a single benchmark spike.

A bit of outside context helps here. Over roughly the last year, long-context mindshare has mostly lived with Gemini and Claude. Gemini 1.5 made the “million-token” framing commercially legible. Anthropic stayed a common choice for enterprise document-heavy workflows, even when the exact window specs shifted by model tier. Open models tried to chase that territory, but the usual tradeoff was brutal: long window with weak quality, decent quality with license baggage, or acceptable performance with ugly deployment costs. DeepSeek is trying to collapse those tradeoffs into one package. If it succeeds, hosted long-context APIs lose some of their pricing power.

I do have a pushback on the launch framing. “Biggest open-weight release of the year” sounds premature. Biggest by which measure: total parameters, practical utility, enterprise adoption, inference economics, or benchmark lead? We don’t know. I’ve seen too many open releases post giant architecture numbers, win a week of hype, and then survive in production only through smaller distilled variants. Without reproducible evals, throughput numbers, and real hardware guidance, this remains a strong claim attached to incomplete evidence.

So the short version is: DeepSeek may have shipped the most commercially consequential open-weight long-context package we’ve seen in a while. That is a stronger statement than saying it shipped the strongest model. Those are different things. If Flash can run fast enough on modest clusters, and if Pro keeps quality stable deep into long sequences, a lot of self-hosted retrieval, coding, and agent setups will get repriced. If the 1M claim turns out to be mostly a spec-sheet ceiling, this becomes another launch where architecture ambition outran operational reality.

Bloomberg TechnologyApr 24, 11:15

DeepSeek unveils flagship AI model a year after breakthrough

DeepSeek released preview versions of a new flagship AI model one year after its breakout. The RSS snippet calls it its most powerful open-source platform and frames it against OpenAI and Anthropic; the post does not disclose parameters, context length, benchmarks, or rollout timing. The actionable facts so far are limited to its preview status and open-source positioning.

Why it matters: A new DeepSeek flagship preview deserves real weight under the domestic-flagship rule, and Bloomberg adds source authority. HKR-H and HKR-R pass, but HKR-K fails because the story discloses no specs, context window, benchmarks, or release schedule, so this stays at the low end of

Take

DeepSeek released a new flagship preview, and the article discloses none of the numbers that would let anyone serious evaluate it: parameters, context length, benchmarks, pricing, or a release timeline. That is enough for a clear read from me: this looks like a bid to seize narrative space first, not a technical result the field can verify yet.

I’ve always thought open model launches live or die on reproducibility. If a company says “most powerful open-source platform,” it needs to answer a few basic questions immediately: are weights available, under what license, which evals were run, what inference stack is supported, and what part is actually open. This snippet answers none of that. It only confirms two facts: preview status and open-source positioning. For practitioners, that is nowhere near enough to assess deployment value or research significance.

The comparison set makes the gap obvious. When Meta launched major Llama releases, it usually paired the announcement with model sizes, benchmark tables, and licensing terms. Qwen updates have also tended to specify dense vs. MoE, base vs. instruct, and at least some evaluation detail. Even when vendors cherry-pick benchmarks, they still give you something to audit. Here, “most powerful” arrives with no test conditions at all. I don’t buy that as a product claim. It is branding until the company publishes reproducible evidence.

I also think the timing frame matters. The headline leans on “a year after breakthrough,” which is a way of telling the market DeepSeek still belongs at the center of the conversation. Fair enough. But the competitive bar has moved over that year. The field now cares less about one-shot leaderboard spikes and more about sustained agent performance, long-context reliability, inference economics, distillation value, and how fast the community can build on top of the release. A flagship open model without transparent cost and availability details loses momentum fast.

There’s one more pushback here. “Open-source platform” can mean several very different things: downloadable weights, a partially open model with closed data and training recipe, or simply an API wrapped in open rhetoric. I haven’t verified which one this is, and the article doesn’t say. That distinction matters more than the headline. If weights and permissive licensing are absent, many developers will not treat this as meaningfully open, no matter how strong the preview sounds.

So my take is simple. DeepSeek is still trying to claim the flagship open frontier lane, and maybe it has the model to back that up. But this article does not provide the evidence. Until benchmarks, licensing, context window, and release details show up, this is a positioning move first and a technical story second.