AI coding

Everything about AI writing code: coding assistants, vibe coding, code model evals and new developer workflows.

1,195 picksRelated topicsAgents Cursor Tutorials

Latest picks

1001–1020 of 1,195

Apr 29Wednesday

X · @doteyApr 29, 01:30

AI terminal tool Warp open-sources client code with OpenAI as founding sponsor

Warp open-sourced its client code under AGPL; only the client is open, while server code stays closed. The Rust terminal has 700,000+ developers, and its Oz cloud AI handles coding, planning, and tests. The key signal is its AI-first contribution workflow.

Why it matters: HKR-H/K/R all pass: the OpenAI sponsorship hook, AGPL/client-only detail, and 700K-developer signal are concrete. This is a strong dev-tool open-source update, not a major model or capability release.

Take

Warp open-sourced its client under AGPL, kept the server closed, and disclosed 700,000 developers plus OpenAI as founding sponsor. My read: this is less an open-source conversion than a trust repair job for an AI terminal. A terminal sits next to shell history, secrets, repos, deploy commands, containers, and cloud credentials. Once an agent starts acting inside that surface, a closed client becomes a harder sell.

The AGPL choice is the first tell. If Warp had picked MIT or Apache 2.0, it would be inviting broad commercial reuse. AGPL keeps more pressure on derivative networked services. But Warp only opened the client, while Oz, its cloud AI platform, stays behind the curtain. That boundary matters. Users can inspect the interface, local terminal behavior, and some client logic. They cannot inspect the routing stack, cloud execution path, telemetry handling, account system, or model-call chain. The article does not disclose how much agent code is actually in the repo. It also does not disclose Oz sandboxing, log retention, permissioning, or data isolation. For an AI terminal, those are not footnotes; they are the product’s risk surface.

The closest comparison is VS Code’s split between open-source core and Microsoft-controlled distribution pieces. Cursor sits on the other side as a closed IDE that sells speed and model integration. Warp is trying a middle position: open client, controlled cloud layer, commercial AI workflow. That is a valid model. I just do not buy any framing that treats this as full openness. A forked Warp client without Oz, automatic routing, team sync, and hosted agent execution is not the same product. The article does not show whether those cloud pieces have a reproducible local path.

OpenAI’s sponsorship is the sharpest part. OpenAI has been fighting for the coding surface through Codex, ChatGPT coding workflows, IDE integrations, and CLI usage. Warp is not just another devtool logo in that fight. It sits at the command layer, where builds, tests, git operations, package managers, Docker, Kubernetes, and cloud CLIs already happen. If agentic coding moves from editor chat into shell execution, the terminal becomes a control point. OpenAI sponsoring Warp’s open-source repo gives it a seat in that experiment without needing to own the terminal outright.

Warp also supports Claude Code, Codex, Gemini CLI, and open models including Kimi, MiniMax, and Qwen. The automatic routing mode tells me Warp does not want to be a model company. It wants to be the console between models and command-line work. That makes sense. Continue, Aider, and OpenHands attack the coding loop from different angles: repo-native pair programming, autonomous dev environments, or IDE-adjacent flows. Warp starts from an existing daily habit. The migration cost is low. The ceiling is messy. Once an agent edits files, runs tests, explains failures, and rolls back patches, a plain terminal is not enough. The article says Warp now has diff views and a file tree, which is basically an admission that serious agent work drags the terminal toward IDE territory.

I am skeptical of the “humans set direction, AI does the work” contribution story. Open-source maintenance has never been limited by raw patch generation. The hard parts are architecture taste, saying no, cross-platform bugs, release hygiene, regression control, and review load. AI can increase pull request volume while making maintainer work more painful. The article gives no merge rate, test pass rate, rollback rate, review staffing, or percentage of Oz-authored contributions accepted. Without those numbers, this is a workflow proposal, not proof of a better open-source model.

AGPL also creates enterprise friction. Many company legal teams treat AGPL as higher-risk than permissive licenses because network-use clauses trigger review. Warp’s users often work on corporate machines. Opening the client reduces security anxiety, but AGPL can slow procurement. If Warp wants individual developer adoption and enterprise revenue, it needs crisp rules around binaries, plugins, internal modifications, cloud sync, and commercial licensing. The article does not disclose those terms.

So I would not file this as “Warp finally went open source.” I would file it as: Warp is turning the terminal into an agent workbench, using an open client to lower the trust barrier, and keeping the server closed to preserve leverage. OpenAI’s role makes this a platform experiment. If the May-June roadmap shows external ideas flowing through Oz planning, code generation, test execution, and merged PRs, then the collaboration claim gets stronger. For now, Warp has opened the door far enough to ask developers for shell-level trust.

Apr 28Tuesday

Ben's BitesApr 28, 21:54

Builders

Ben’s Bites published one newsletter on AI builders. It says OpenAI released GPT-5.5 at 2x GPT-5.4 pricing, with a claimed 40% token-efficiency gain. Claude Managed Agents memory entered public beta, and Cursor’s SpaceX/xAI deal includes a $60B 2026 purchase option.

Why it matters: HKR-H/K/R all pass: GPT-5.5 cost/efficiency figures, Claude Managed Agents Memory beta, and a Cursor deal term. It stays in 85–94 because this is a newsletter roundup, not a primary release.

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.

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

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.

Hacker News front pageApr 28, 06:13

Claude Pro: Opus Requires Extra Usage in Claude Code

Anthropic lists 6 Claude Code models, and Pro users need extra usage enabled and purchased to use Opus. The guide gives 3 configuration paths: /model, --model, and ANTHROPIC_MODEL in zsh or bash. The post does not disclose extra usage pricing or quotas.

Why it matters: HKR-H/K/R all pass, but the facts come from a help doc and cover Claude Code access/configuration, not a new model or major capability. Anthropic relevance lifts it to the lower featured band.

X · @doteyApr 28, 04:43

The West forgot how to build things, and may forget how to write code

Denis Stetskov compares Western defense production gaps with AI coding, citing Stinger orders placed in 2022 for 2026 delivery. He says Europe’s 1M-shell target was 9 months late, and METR found senior developers 19% slower with AI. The key risk is the junior-engineer pipeline, not code generation speed.

Why it matters: HKR-H/K/R all pass: the analogy is clickable, the post gives concrete defense and METR numbers, and the junior-engineer pipeline resonates. X translation/commentary limits authority, so it sits just above the featured threshold.

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.

Hacker News front pageApr 28, 00:03

GitHub Copilot is moving to usage-based billing

GitHub said on 2026-04-27 that GitHub Copilot will move to usage-based billing. The captured post only shows the title, time, and navigation. It does not disclose the launch date, usage metric, prices, or overage rules.

Why it matters: GitHub Copilot billing affects a large developer base. HKR-H and HKR-R are strong, while HKR-K is limited to the usage-based mechanism with no date, metering unit, or price details disclosed.

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.

Hacker News front pageApr 27, 21:05

Running Local LLMs Offline on a Ten-Hour Flight

Dmitri Lerko ran Gemma 4 31B and Qwen 4.6 36B locally during a 10-hour flight with no Wi‑Fi. The MacBook Pro M5 Max had 128GB unified memory and a 40-core GPU; sustained load used about 1% battery per minute, and performance degraded past 100k tokens. The sharp finding is instrumentation: an iPhone cable delivered 60W, while a MacBook cable delivered 94W under the same load.

Why it matters: HKR-H/K/R all pass: this is a named first-person local-inference test with concrete hardware, model, battery, and power numbers. Scope stays practical rather than industry-shaking, so it lands in the 72–77 band.

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.

Hacker News front pageApr 27, 13:28

AI can cost more than human workers now

Axios says some firms now spend more on AI than salaries; Nvidia's Bryan Catanzaro says compute costs exceed employee costs. Gartner forecasts 2026 IT spending at $6.31T, up 13.5%, driven by AI infrastructure, software, and cloud. Watch token costs: Uber's CTO has already exhausted the 2026 AI budget.

Why it matters: HKR-H/K/R all pass: the piece turns AI cost anxiety into budget facts, including Nvidia compute costs and Uber’s token-budget issue. It stays in the 72–77 band because this is trend reporting, not a launch or hard news event.

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

Synced · WeChatApr 27, 08:03

ACL 2026: Sending AI “~” May Cause It to Delete Your Home Directory

ACL 2026 accepted an LLM safety paper on emoticon semantic confusion. The team tested 6 models with 3,757 cases; average confusion was 38.6%, with over 90% silent failures. The key risk is agent execution, where “ignore emoticons” prompts had limited effect.

Why it matters: ACL 2026 safety research clears HKR-H/K/R: a sharp file-deletion hook, concrete test numbers, and direct agent-execution risk. It is strong research, not a model launch or platform incident, so it stays in the 78–84 band.