Agents

All topics

Models that plan, call tools and finish multi-step tasks on their own — from Claude Code and Manus to agent frameworks and benchmarks.

1,465 picksRelated topicsMCP & tool use AI coding Reasoning

Latest picks

1181–1200 of 1,465

Apr 28Tuesday

QbitAI · WeChatApr 28, 20:56

NTU REI-Bench Tests Vague Human Instructions, With Success Rates Dropping Up to 36.9%

NTU MARS Lab released REI-Bench, a benchmark with 9 ambiguity levels for vague human instructions. Tests used 4 robot planning frameworks and 6 small LLMs; LLaMA3.1-8B+SayCan fell from 57.7% to 46.9% in standard multi-turn context. The key issue is implicit reference resolution, where baseline success dropped 7.4% to 36.9%.

Why it matters: HKR-H/K/R all pass: the 36.9% drop is a strong hook, and the setup gives 9 ambiguity levels, 4 frameworks, and 6 models. This is a solid embodied-AI benchmark, not a major model release, so it fits the 78–84 band.

Take

REI-Bench quantifies the robotics failure mode vendors prefer to hide: the robot can plan, then collapses on human vagueness. The disclosed setup uses 9 ambiguity levels, 4 planning frameworks, and 6 small LLMs. LLaMA3.1-8B+SayCan drops from 57.7% to 46.9% in standard multi-turn context, while implicit reference resolution cuts baseline success by 7.4% to 36.9%.

I trust this kind of ugly benchmark more than another polished kitchen VLA demo. SayCan-style systems already depend on the language model ranking affordances; commands like “put that over there” force vision, memory, and dialogue context to line up. The WeChat body is blocked by verification, so task scale and annotation protocol are not disclosed. If the suite is small, the 36.9% number can look louder than it is. The failure mode still matches what robotics teams hit once demos leave scripted prompts.

QbitAI · WeChatApr 28, 20:56

Xiaomi open-sources MiMo-V2.5 series; Pro builds a macOS-like desktop in 4 hours

Xiaomi open-sourced MiMo-V2.5 weights, covering Pro Agent, multimodal base, TTS, and ASR models. MiMo-V2.5-Pro built a 54-app macOS-like desktop in 4 hours without human takeover; it scored 233/233 on SysY with 672 tool calls in 4.3 hours. Key details for practitioners are the 1M context, 100T-token program, and free Agent-framework access.

Why it matters: HKR-H/K/R all pass: Xiaomi open-sourced MiMo-V2.5 weights with concrete agent and coding-task numbers. Domestic flagship model release bump puts it in the must-write same-day band.

Take

Xiaomi open-sourced MiMo-V2.5 weights with 1M context, a 100T-token program, and a 4.3-hour SysY run. My read is split: the engineering demos are stronger than a routine Chinese model launch, but the article jumps from demos to “top global model table” far too quickly.

The concrete claims are not small. MiMo-V2.5 includes MiMo-V2.5-Pro, a multimodal base model, TTS, and ASR. MiMo-V2.5-Pro reportedly built a macOS-like desktop in 4 hours without human takeover. The demo had 54 apps, 68 components, React 18, TypeScript, Zustand, Tailwind CSS, and Vite. It also completed the Peking University SysY compiler task in 4.3 hours, using 672 tool calls, and scored 233/233. The article says ClawEval used about 70K tokens per trajectory for a 64% Pass³ rate, while Claude Opus 4.6, Gemini 3.1 Pro, and GPT-5.4 used 120K to 180K tokens. If that holds under outside replication, it matters. Agent cost is not just model pricing; it is tool loops, retries, context growth, and failed trajectories.

The gaps are equally large. The article does not disclose parameter count, MoE layout, training-token count, RL recipe, tool sandbox, sampling settings, failed runs, average pass@k, or repository history for the macOS demo. A 54-app desktop sounds flashy, but static app shells and maintainable software are different artifacts. The claim that the XcodeApp includes a “real browsable web engine” needs inspection. Is that an iframe wrapper, a browser API simulation, or an actual browser implementation? The body does not say. For practitioners, that difference moves the demo from a weekend build to a serious systems result.

The SysY result is the strongest number in the piece. Compiler tasks test long-horizon consistency better than front-end demos. Lexing, parsing, IR generation, RISC-V backend work, and optimization all interfere with each other. A model surviving 672 tool calls without derailing suggests Xiaomi trained or engineered around state management and error recovery. I would compare this to SWE-bench Verified-style agent runs: plenty of models write a good patch for one issue, then start overwriting themselves after 20 to 50 steps when tools, files, and context stack up. If MiMo-V2.5-Pro is reliably stable past 600 turns, that is not copywriting. That is model policy plus agent runtime doing real work.

I care even more about the 70K-token efficiency claim. Agent token reduction usually comes from one of three places: better compressed planning, more aggressive context trimming, or a tool-result summarizer. The first is genuinely valuable. The second hides failure modes. The third depends heavily on the surrounding framework. The article only says “token efficiency.” It does not say whether this comes from MiMo-V2.5-Pro itself or from Xiaomi’s agent framework compressing trajectories. Xiaomi also announced free access for emerging agent frameworks, which makes benchmarking messier. Are we measuring the open model, or a product stack with policy, memory, and tool routing layered around it?

Externally, Xiaomi’s move feels closer to Qwen and DeepSeek distribution playbooks than a pure Claude/GPT benchmark chase. Qwen gained developer mindshare through open weights, many model sizes, and tool coverage. DeepSeek won trust with cheap API economics and reproducible inference cost. Moonshot, Zhipu, and MiniMax have leaned more on products and APIs. Xiaomi has a different asset base: phones, cars, IoT, voice, and OS-level distribution. Shipping TTS, ASR, a multimodal base, and an agent model together makes sense for Xiaomi. The company wants models that can sit inside phones, vehicles, home devices, and developer workflows, not just collect GitHub stars.

The audio claims need caution. The article says MiMo-V2.5-TTS supports text-described voices and zero-shot cloning without reference audio. It says ASR reaches Chinese-English SOTA and handles Cantonese, Sichuanese, Wu, and Minnan. But the “99.999%” recognition number comes from one Cantonese test, with no disclosed duration, noise condition, accent spread, labeling standard, or dataset. ASR is already crowded: Whisper, SenseVoice, Paraformer, and FunASR have made clean speech less impressive. The hard cases are overlapping speakers, far-field audio, music beds, mixed dialects, and low-bitrate telephone speech. The article gives experience notes, not a proper evaluation.

The 100T-token giveaway is the sharpest commercial move. It gives agent builders a reason to test a new base. OpenAI and Anthropic have strong developer habits. Qwen already owns a lot of open-source inertia. A later entrant needs three things at once: good enough quality, low enough cost, and low migration friction. Xiaomi cut Pro credits from 4x to 2x, standard from 2x to 1x, priced 1M and 256K context at the same credit multiplier, and added a 20% night discount from 00:00 to 08:00 Beijing time. Those details matter more than the “global top-tier” language. Agent developers follow invoices faster than slogans.

My biggest problem is the source layer. This is a media experience piece, not a system card and not an independent benchmark report. It mentions Claude Opus 4.6, GPT-5.4, and Gemini 3.1 Pro, but gives no table, benchmark version, evaluator, confidence interval, or reproduction package. The title says the weights are open-sourced, but the body does not disclose the license. Commercial use, acceptable-use limits, redistribution terms, and training-data posture matter more for enterprise adoption than a demo video. Open weights with a restrictive license are downloadable, not freely deployable.

So my stance is simple. MiMo-V2.5 is Xiaomi’s first AI release that looks like a complete platform bet: agent, long context, voice, open weights, and developer subsidy in one package. The article pushes every claim to maximum volume, which makes me wait for third-party replication. I need three things before upgrading my view: public SysY and ClawEval scripts, the full macOS-demo repository trajectory, and clear license terms. If those hold up, Xiaomi becomes a serious player in the Chinese open agent stack. For now, I accept the release has force. I do not yet seat it beside Claude and GPT.

QbitAI · WeChatApr 28, 20:56

Open-source SenseNova-U1 unifies image understanding and generation

SenseTime open-sourced two SenseNova-U1 models: an 8B version and a 38B-total MoE version using NEO-unify. The architecture removes VE and VAE, processes pixels directly, and generates 2048×2048 images in about 9 seconds on one H100/H200 node. The key item is interleaved text-image reasoning; 32K context, long-text rendering, and beta interleaved creation remain limits.

Why it matters: HKR-H/K/R all pass: the architecture hook is concrete, the post gives model sizes and latency, and open multimodal work matters to builders. It stays in 78–84 because it is not a top-tier general-model launch.

Take

SenseNova-U1’s useful bet is not the open-sourced 8B and 38B-total MoE weights; it is the removal of VE/VAE and the attempt to force understanding and generation through one pixel path. The hard hooks are specific: NEO-unify takes pixels in and emits pixels out, one H100/H200 node produces a 2048×2048 image in about 9 seconds, and context is 32K. The WeChat body is blocked by verification, so training data, license terms, and benchmark setup are not available.

I like the direction, but I don’t buy the victory lap yet. Janus-Pro already showed that “unified multimodal” makes a clean headline; the pain lives in text rendering, localized edits, and long interleaved image-text chains. U1 labels long-text rendering and continuous interleaved creation as beta, which is the tell: this is a research-shaped release, not a clean replacement for separate diffusion pipelines.

Hacker News front pageApr 28, 20:16

Xiaomi releases MiMo-v2.5 weights with strong coding and agent benchmarks

Xiaomi released MiMo-v2.5 family weights; the title cites strong coding and agent benchmarks. The RSS body only lists URLs, 13 HN points and 2 comments; the post does not disclose size, license, or scores.

Why it matters: HKR-H/K/R pass because a Xiaomi coding/agent weights release is concrete and practitioner-relevant. Sparse sourcing holds it near the featured floor: no parameters, license, or benchmark numbers are disclosed.

Take

MiMo-V2.5-Pro has the right headline and a thin evidence trail. The article confirms an April 23, 2026 release, open weights, and a coding focus; the feed shows only 13 Hacker News points and 2 comments. It gives no parameter count, license, context length, SWE-bench score, agent benchmark setup, or evaluation harness. Using “right next to Claude Opus 4.6” as the hook borrows frontier-model credibility without reproducible conditions.

Xiaomi does have a plausible reason to ship this: phones, IoT, and cars all need local coding-ish agents and tool use. But the open-model bar is now set by DeepSeek, Qwen, and Llama releases with weights plus usable evals and commercial terms. A weight drop alone is a teaser; the missing license and benchmark recipe decide whether practitioners can use it.

The Verge · AIApr 28, 19:00

Attack of the Killer Script Kiddies

The Verge discusses Claude Mythos and AI bug finding, citing DARPA AIxCC scans over 54 million code lines. Teams found most seeded flaws plus over a dozen unseeded bugs; the RSS snippet does not disclose Mythos benchmarks, pricing, or access terms.

Why it matters: HKR-H/K/R all pass: the hook is strong, DARPA AIxCC supplies concrete numbers, and the security angle resonates. No Claude Mythos benchmark, pricing, or access terms are disclosed, so it stays in the featured-threshold band.

Hacker News front pageApr 28, 17:01

GitHub Copilot code review will start consuming GitHub Actions minutes

GitHub will make Copilot code reviews consume GitHub Actions minutes starting June 1, 2026. Private-repo reviews use plan entitlements, with overages billed at standard Actions rates; public repos stay free. The change covers Copilot Pro, Pro+, Business, and Enterprise, including direct org billing for unlicensed users.

Why it matters: Official GitHub billing change for Copilot code review hits CI quotas and org invoices; HKR-H/K/R all pass, but it is a pricing rule, not a capability release, so it sits low in 72–77.

Xinzhiyuan · WeChatApr 28, 13:41

NUS and NTU Release Pask with Streaming Intent Detection and Persistent Memory

NUS and NTU released Pask, with paper arXiv:2604.08000. Pask uses DD, MM, and PAS, with IntentFlow detecting intent in 1.5 seconds. The key bet is real-time intent detection, not longer execution chains.

Why it matters: HKR-H/K/R all pass: Pask offers a concrete real-time intent layer for proactive agents. No open-source status, benchmark table, or production deployment is disclosed, so it stays at 78 rather than P1.

Xinzhiyuan · WeChatApr 28, 13:41

Claude bans hit 110-person firm; Cursor incident deletes database in 9 seconds

Anthropic allegedly suspended 110 Claude accounts at a US agtech firm, while API billing continued. The post says appeals went unanswered for 36 hours, and PocketOS says Claude Opus 4.6 via Cursor deleted production data and volume backups in 9 seconds. The key issue is access control: no RBAC, no environment isolation, and no delete confirmation.

Why it matters: HKR-H/K/R all pass: the incident has a strong hook and concrete details: 110 accounts, 36 hours, 9 seconds, and no RBAC. Kept at 82 because it is still a single-source allegation without an Anthropic postmortem.

Take

I wouldn’t share this as “Claude went rogue.” It reads like a permissioning failure wearing an AI panic mask. The hard detail in the summary is ugly: Claude Opus 4.6 through Cursor allegedly deleted the production database and volume-level backups in 9 seconds, with no RBAC, no environment isolation, and no delete confirmation. Any sane CI/CD or cloud console would split those actions across roles, environments, confirmations, and logs.

Anthropic suspending 110 accounts, leaving appeals unanswered for 36 hours, and still billing API usage is a separate platform-governance mess. The article body is inaccessible, so suspension grounds, billing terms, and support records are not disclosed. Collapsing both into “the model deleted the company” is catchy, but it teaches the wrong lesson: before agents touch prod, treat permissions like explosives, not prompts like seatbelts.

X · @op7418Apr 28, 10:42

Xiaomi open-sources the MiMo-V2.5 model series

Xiaomi open-sourced the MiMo-V2.5 model series under the MIT license for commercial use, retraining, and fine-tuning. It also launched Orbit 100T Token, offering approved AI builders up to 1.6B credits worth 659 yuan. Agent framework teams can apply for free MiMo token access; the post does not disclose model size or benchmark results.

Why it matters: HKR-H/K/R all pass: Xiaomi MiMo-V2.5 open source, MIT terms, and Orbit 100T credits matter to builders. Missing params and benchmarks keep it in the 78–84 band, below P1.

Take

Xiaomi open-sourced the full MiMo-V2.5 series under the MIT license. That is the clearest fact here. MIT allows commercial use, retraining, and fine-tuning without extra permission. For a phone, EV, and IoT company, this reads less like a pure model launch and more like a developer funnel. The post does not disclose parameter counts, context length, API pricing, SWE-bench, Aider, LiveCodeBench, or Chinese evals. The title says the full series is open-sourced; the body does not show the technical receipts.

My read is blunt: Xiaomi is not proving that MiMo-V2.5 beats DeepSeek, Qwen, or Kimi on capability. It is lowering adoption friction first. The Orbit 100T Token plan offers approved AI builders up to 1.6B credits, listed at 659 yuan. That number is catchy, but the body does not define the credit-to-token conversion, input-output split, rate limits, eligible models, or expiry rules. Without those conditions, 1.6B credits only tells us Xiaomi is willing to subsidize usage. It does not tell us whether the serving economics work.

Qwen is the obvious comparison. Alibaba’s open model strategy worked because it paired permissive licensing with parameter tiers, quantized variants, inference integrations, public benchmarks, and a steady community loop. DeepSeek-R1 hit because reasoning behavior, low API pricing, open weights, and distilled models arrived together. Xiaomi’s disclosed package is thinner. It gives the ecosystem an opening, but not enough evidence for a serious team to route production traffic. Agent framework teams care about latency stability, function-calling reliability, long-context cost, concurrency limits, and failure modes. A large token pool does not answer those questions.

Honestly, the agent ecosystem angle is the part I take more seriously. Xiaomi’s advantage is not model-lab prestige. It is distribution across phones, cars, home devices, and HyperOS. If MiMo becomes the model layer for device control, in-car assistants, household automation, and cross-device workflows, Xiaomi has a deployment surface that many standalone model companies lack. But the post leaves the key facts blank. It does not say whether MiMo-V2.5 supports tool use, structured output, multimodal inputs, on-device variants, or multiple model sizes. Without that, the agent story is a recruitment pitch, not an architecture claim.

I do not buy “fully open-source” as a sufficient signal in 2026. The bar has moved. A permissive license without a model card, reproducible evals, inference recipes, and clear API pricing will not move careful builders off their current stack. Xiaomi made a useful move, but the useful part is channel plus subsidy, not demonstrated model superiority. Once it publishes weights, evals, serving terms, and integration details, MiMo-V2.5 can be compared on the same board as Qwen and DeepSeek. Right now, Xiaomi opened the door. It has not shown what is inside.

r/LocalLLaMAApr 28, 09:32

Local coding models have reached a threshold for real work

Antigma tested 27B–32B open-weight models; Qwen 3.6-27B scored 38.2% on Terminal-Bench 2.0. The run used 89 tasks and the default per-task timeout, while verified SOTA is about 80%. The key claim is deployment lag: offline coding is about 6–8 months behind hosted frontier models.

Why it matters: HKR-H/K/R all pass: the post gives a real-work threshold claim, a 38.2%/89-task Terminal-Bench result, and a 6–8 month offline gap. Reddit single-post sourcing keeps it in the low featured band.

Computing Life · Share · YageApr 28, 08:00

Agentic Creative Tools: From Photoshop Actions to Claude for Creative Work

Anthropic released 9 creative-tool Connectors for Claude for Creative Work. The post frames agentic creative tools around programmable APIs, connector protocols, and perceptual feedback loops. The post does not disclose the Connector list.

Why it matters: HKR-H/K/R all pass: Claude creative agents have a clear hook, 9 connectors add a fact, and creator workflow pressure adds resonance. Missing connector names and access terms keep it below must-write.

X · @doteyApr 28, 03:39

GitHub Copilot switches to usage-based billing on June 1

GitHub Copilot will switch to AI Credits billing on June 1 while keeping subscription prices unchanged. Credits count input, output, and cached tokens; Pro includes $10 monthly credits and Pro+ includes $39. Watch Copilot Agent long-task costs.

Why it matters: HKR-H/K/R all pass: Copilot billing moves from subscription expectations to token/cache consumption with date and credit amounts. Single-source X context lacks enterprise details and overage rates, so it stays in the 78–84 band.

X · @doteyApr 28, 03:01

Cursor 3 feedback: users want a reliable AI development workspace

Eric Zakariasson’s Cursor 3 feedback thread summarizes 431 replies, with users asking for a stable AI development workspace. Requests center on Agent Window retaining LSP, debugging, Git, terminal and diff workflows, plus multi-agent worktrees and model-cost transparency. The key issue is workflow reliability, not a flashier IDE.

Why it matters: All HKR axes pass: 431 user replies, concrete workflow requests, and strong resonance for Cursor users. Kept in the low featured band because this is feedback synthesis, not an official Cursor release or roadmap.

Apr 27Monday

Dwarkesh Patel podcastApr 27, 21:51

What I've been Thinking About This Weekend: Open Questions, Intelligence vs Power, Verification in Science

Dwarkesh lists open AI questions, including that five hyperscalers own over 70% of global AI compute. He asks about coding agents, KV cache costs, merging training with inference, and online learning; the post gives questions, not experimental answers.

Why it matters: HKR-H/K/R all pass: Dwarkesh adds a concrete compute-concentration claim and practitioner-relevant questions. No experiment, release, or policy change, so it stays in the 72–77 commentary band.

Take

Dwarkesh’s sharpest move is dragging capability talk back to compute ownership. If five hyperscalers hold 70%+ of global AI compute, and much of it is reserved for OpenAI, Anthropic, and GDM, long-horizon coding agents are not just algorithmic progress. They are a resource allocation outcome.

The KV-cache example is the hard hook: Llama 3 70B uses about 320KB per token in cache, versus 0.075 bits per token if weights are amortized over pretraining tokens. That 35-million-fold gap makes “context learning” look like an expensive memory trick, not magic sample efficiency. I don’t buy the post as merely a list of open questions. It has a thesis: pretraining, RL generation, and inference collapse into online learning. The weak spot is verification; the article gives no experimental result or lab evidence that anyone has made that loop reliable.

TechCrunch · AIApr 27, 21:16

China blocks Meta’s $2B Manus deal after months-long probe

China ordered Meta to unwind its $2B Manus acquisition. The title says the probe lasted months; the post does not disclose the legal mechanism, timeline, or Meta’s next steps. The deal risk directly hits Meta’s AI agents push.

Why it matters: HKR-H/K/R all pass: a $2B Meta-Manus AI-agent deal was blocked by China after a months-long probe. The article lacks the legal mechanism and Meta’s next step, so it lands at 88, not 90+.

Hacker News front pageApr 27, 20:35

Show HN: OSS Agent Dirac topped TerminalBench on Gemini-3-flash-preview

Dirac-run released Dirac and says it topped TerminalBench using Gemini-3-flash-preview. The repo claims 50-80% lower API costs via Hash Anchored edits, parallel operations, and AST manipulation; the post does not disclose full scores.

Why it matters: HKR-H/K/R all pass: an OSS coding agent claims a TerminalBench lead with cost and mechanism details. Held to 78 because the post relies on repo claims and lacks full leaderboard scores or reproduction logs.

Mistral AIApr 27, 20:00

Mistral AI opens public preview of Workflows

Mistral AI has put Workflows, its enterprise AI orchestration layer, into public preview. It offers durable execution, observability and human-in-the-loop approvals. ASML, ABANCA and CMA-CGM are already using it to automate critical processes.

Why it matters: It lays out Workflows' orchestration features, deployment model and customer cases, showing the engineering bar for enterprise AI processes.

Xinzhiyuan · WeChatApr 27, 18:11

First Spatio-Temporal Time-Series Reasoning Framework for LLMs | ACL'26

Emory University, Microsoft, and partners introduced STReasoner for spatio-temporal time-series reasoning, with ST-Bench covering four task types. It uses Network SDE plus Multi-Agent data generation, then Align, SFT+CoT, and S-GRPO training. The article claims inference cost is 0.004× closed models, with code on GitHub.

Why it matters: HKR-H and HKR-K pass: the story has a “first framework” hook plus ST-Bench, S-GRPO, 0.004× cost, and code release. HKR-R is weak because spatiotemporal reasoning is a narrower research lane.

Take

STReasoner moves spatio-temporal forecasting away from “ask a general LLM to reason over curves.” That is a useful bet for traffic, weather, and sensor networks. The summary gives concrete hooks: ST-Bench has four task types, data comes from Network SDE plus Multi-Agent generation, then training runs through Align, SFT+CoT, and S-GRPO.

I’m wary of the 0.004× inference-cost claim against closed models. The article body is inaccessible, and the summary does not give the closed baseline, token accounting, hardware, or sequence length. That number can easily be model-size arbitrage dressed up as a reasoning win. Compared with TimeGPT or Lag-Llama-style time-series models, the interesting part is the reasoning trace plus spatial graph structure, not generic chat ability. ACL’26 helps; the GitHub release matters more.

QbitAI · WeChatApr 27, 11:47

Stanford-led LLM-as-a-Verifier claims SOTA on Terminal-Bench 2.0

Stanford, Berkeley and Nvidia introduced LLM-as-a-Verifier, claiming SOTA on Terminal-Bench 2.0 and SWE-Bench Verified. It selects trajectories via score-token granularity, repeated checks and criteria decomposition; ForgeCode accuracy reached 86.4%.

Why it matters: HKR-H/K/R all pass: Stanford, Berkeley, and NVIDIA offer a concrete verifier mechanism and benchmark numbers. It is still a benchmark research release, not a major model or product launch, so it fits the 78–84 band.

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%.