AI coding

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

1,196 picksRelated topicsAgents Cursor Tutorials

Latest picks

961–980 of 1,196

May 7Thursday

Synced · WeChatMay 7, 10:05

TACO Lets CLI Agents Drop Useless Context Through Self-Evolving Compression

TACO proposes a training-free terminal-observation compression framework, improving success rate and token efficiency on TerminalBench 1.0/2.0 and related benchmarks. It evolves rules within tasks, writes validated rules to a global pool, and finds 24.6%–44.1% low-value redundancy in TerminalBench 2.0 raw prompts. The key signal is stability: Top-30 rule retention exceeds 90% after multiple evolution rounds.

Why it matters: HKR-H/K/R all pass: the paper targets CLI-agent context bloat with a no-training rule-pool mechanism and concrete TerminalBench numbers. It is strong agent research, not a major model or product launch, so it sits in the 78–84 featured band.

Synced · WeChatMay 7, 10:05

Claude, GPT and Gemini score 0% completion on ProgramBench

ProgramBench tested Claude Opus 4.7, GPT-5.4 and Gemini 3.1 Pro, with 0% full completion on rebuilding software projects. It gives only executables and usage docs, removes source/tests, and grades behavioral equivalence via agent-driven fuzzing. The key signal is system-level engineering, not function-level code generation.

Why it matters: HKR-H/K/R all pass: the 0% result is clickable, the setup is concrete, and the coding-agent gap matters to practitioners. Still, it is a single benchmark report, below a major model or product release.

Synced · WeChatMay 7, 10:05

Musk Announces xAI Dissolution, Leasing 220,000 GPUs to Anthropic

Musk confirmed xAI will dissolve, with Grok and X-related operations folded into SpaceXAI. SpaceX and Anthropic signed a deal giving Claude access to Colossus 1’s 220,000+ Nvidia GPUs and 300 MW of compute. The key change is quota: Claude Code’s five-hour rate limit doubles, and Pro/Max peak-hour cuts are removed.

Why it matters: HKR all pass: xAI dissolution plus 220k GPUs for Anthropic is a top-tier twist; 300 MW and Claude Code quota changes add testable detail; it hits compute, competition, and developer limits. Single-source status keeps it at 96.

AI HOT (Curated Pool)May 7, 09:45

Open Slide lets AI write PPT code

Open Slide builds PPTs with React, using a workflow designed for AI agents. It integrates SVGL with 1,500+ brand logos, supports manual edits, and lets AI read user comments for revisions.

Why it matters: HKR-H/K/R pass: the programmable-slide angle is clickable, with concrete React and 1500+ logo details, and deck work is a real practitioner pain. No usage metrics or hands-on test keeps it at the featured threshold.

Take

Open Slide picked the right fight: slide generation breaks after the first draft, not before it. React as the slide substrate gives agents an actual edit surface, and the key hook is AI reading user comments, then changing components. The 1,500+ SVGL logos are useful garnish; component-level charts and style edits are the workhorse.

I don’t buy the generic “productivity” framing. Gamma, Canva, and Google Slides AI already produce decent first passes, then struggle when feedback targets layout objects through vague language. Open Slide takes the code path: higher user friction, but versionable diffs, reviewable changes, and repeatable edits. The missing facts matter: export fidelity, multiplayer review, and PowerPoint round-trip are not disclosed. Without those, this stays a strong developer demo rather than a serious deck workflow.

r/LocalLLaMAMay 7, 04:36

GB10 inference engine Atlas is open source, with Qwen3.6-35B-FP8 over 100 tok/s

Avarok open-sourced Atlas, an inference engine running Qwen3.5-35B at ~111 tok/s sustained on one DGX Spark. It uses Rust+CUDA, a ~2.5GB image, and sub-2-minute cold start; the author claims 3.0–3.3x vLLM in tests. The key details are Blackwell SM120/121 kernels, NVFP4/FP8, and MTP decoding.

Why it matters: HKR-H/K/R pass: open-source inference engine, 35B FP8 at 111 tok/s, and a direct vLLM comparison. Single Reddit sourcing and unreproduced benchmarks keep it at the lower featured band.

May 6Wednesday

r/LocalLLaMAMay 6, 17:35

2.5x Faster Inference with Qwen 3.6 27B Using MTP on 48GB

A llama.cpp PR adds MTP support for Qwen 3.6 27B, with a reported 2.5x inference speedup. The author measured 28 tok/s on a Mac M2 Max 96GB and shared GGUF builds, compile steps, and a 262144-context server command. The key detail is turbo4 4.25-bit KV cache: a 48GB Mac runs Q5_K_M at 262K context.

Why it matters: HKR-H/K/R all pass: the hook is concrete, the post names mechanisms and numbers, and local coding-agent cost resonates. Single Reddit source and setup complexity keep it in the low featured band.

Latent SpaceMay 6, 13:40

AINews: Silicon Valley Gets Serious About Services

Anthropic and OpenAI announced enterprise services companies: Anthropic’s unnamed JV is funded with $1.5 billion, while OpenAI’s The Deployment Company has raised about $4 billion at a $10 billion pre-money valuation.

Why it matters: HKR-H/K/R all pass: the hook is labs turning into services operators, with $1.5B and ~$4B figures. The scale and OpenAI/Anthropic names put it in must-write territory.

Take

OpenAI and Anthropic are moving straight into Accenture territory. OpenAI’s The Deployment Company has raised about $4B at a $10B pre-money valuation, while Anthropic’s JV with Blackstone, Hellman & Friedman, and Goldman Sachs has $1.5B behind it, with $300M from each main participant. That is not startup SI money; it is PE-backed channel capture for model labs.

I don’t buy the clean story that agents just flow into knowledge work. The described engagement is old-school consulting: a small team embeds with the customer, identifies where Claude matters, then builds tailored systems with Anthropic Applied AI. Aaron Levie’s list—IT upgrades, context plumbing, workflow redesign, human-agent boundaries, adoption, change management—is the services playbook with better models attached. Tessera raising a Series A for system integration the same day is the tell. The labs want the services margin before integrators turn them into dumb model suppliers.

Synced · WeChatMay 6, 12:07

DeepSeek Version of Claude Code Tops Trending Chart With 8,700 Stars

DeepSeek TUI topped GitHub trending with over 8,700 stars. Hunter Bown built it in Rust for local terminal use with DeepSeek V4, supporting chat, file edits, shell commands, and task management. The key detail is RLM mode: up to 16 V4 Flash subtasks, plus a 1M-token context window and approval gates.

Why it matters: HKR-H/K/R all pass: the 8,700-star hook is strong, RLM adds concrete mechanisms, and coding-agent competition resonates. It is a third-party open-source tool, not an official DeepSeek model release, so it stays in the 78–84 band.

Take

DeepSeek TUI crossed 8,700 GitHub stars because it hits a very specific gap: Claude Code’s terminal workflow is loved, but its closed product surface and API cost annoy developers.

My read is simple. This does not prove a DeepSeek-powered clone has matched Claude Code. It proves the interaction pattern is now portable. The article lists local TUI usage, file edits, shell execution, task management, approval gates, and Plan / Agent / YOLO modes. That bundle is familiar after Claude Code, Aider, OpenCode, Cline, and Cursor-style agent loops. DeepSeek TUI is getting attention because developers want the Claude Code shape without being tied to Anthropic’s product cadence or pricing.

The strongest technical detail is RLM mode. The article says it can run up to 16 DeepSeek V4 Flash subtasks in parallel, use a 1M-token V4 context window, and route fan-out work to the cheaper Flash model. That architecture makes sense. A lot of coding-agent work is not “one genius model solves everything.” It is search, call-graph reading, test candidate generation, risk listing, duplicate pattern scanning, and local summarization. Those are batchable. If Flash output costs roughly one-third of Pro, as the article says, parallel cheap subtasks can lower the cost of large refactors.

But the substitution claim is too strong. The article says DeepSeek TUI can fully replace Claude Code. It does not disclose SWE-bench results, real-repo bug-fix pass rates, human acceptance rates, median API cost, failure classes, or same-task comparisons against Claude Code. GitHub stars measure curiosity and social heat. They do not measure production retention. Aider, Continue, and Open Interpreter all had versions of this curve: fast developer excitement first, then the hard part starts when dirty repos, broken tests, permission boundaries, rollback, and long dependency chains show up.

The hard comparison with Claude Code is model consistency. Claude Sonnet has been strong in coding-agent settings because it tends to use tools conservatively, read before editing, and keep task state across long loops. I am not claiming it never fails; it fails plenty. But Anthropic has clearly tuned the model, approval mechanics, and terminal-native workflow together. DeepSeek TUI’s disclosed surface is mostly product scaffolding. The article does not show system-level evaluation.

I also have doubts about the “transparent chain of thought” pitch. For developers, observability is useful. Seeing intermediate reasoning in the terminal can help debug the agent’s direction. But selling visible thought as control is risky. Real control comes from auditable diffs, command allowlists, sandboxing, rollback paths, test gates, and clear approval scopes. A scrolling reasoning stream can make users feel safer than they are. In coding agents, the dangerous failure is not usually a bad paragraph; it is a shell command, a bad migration, or a plausible patch that breaks an edge case.

The 1M-token context window has the same trap. Big context is attractive for repo work, but “use it all by default” is not automatically smart. Large context introduces retrieval noise, attention dilution, and cost creep. The article mentions context compression, but it does not disclose the compression policy, trigger conditions, symbol preservation, path handling, or how it resolves conflicts between old context and fresh diffs. Anyone who has worked with repo agents knows the hard skill is reading less but reading the right files. Cursor, Cline, and Aider-style tools have all exposed this problem in different ways. Once users believe the agent has “the whole repo,” they stop checking the context boundary. That is where subtle bugs enter.

The founder angle is genuinely useful, even if the article over-romanticizes it. Hunter Bown is described as a SMU patent-law student who built this in Rust with AI-assisted programming under Shannon Labs. I would not call that “AI self-iteration.” That phrase is doing too much work. The practical point is sharper: AI coding tools are lowering the entry barrier to building more AI coding tools. A non-traditional software founder can assemble a Rust TUI, model routing, agent loops, approval gates, and repo operations into a project that tops GitHub trending. That says something about where the tooling layer is going. The outer shell is getting cheaper to build; the durable edge moves to evaluation, safety defaults, task routing, model behavior, and workflow taste.

So I would file DeepSeek TUI under “open-source agent shell pressure,” not “Claude Code killer.” The demand signal is real. The RLM idea is credible. DeepSeek V4’s low-cost stack gives it room to experiment. But the article does not disclose active installs, daily usage, task success, cost distribution, or controlled comparisons. Without those numbers, the replacement narrative is premature. Still, this belongs on the radar. If DeepSeek TUI turns RLM scheduling, permission isolation, and repo-level evals into a repeatable system, commercial coding agents will have to justify their price with measured reliability instead of vibes.

Xinzhiyuan · WeChatMay 6, 09:48

Coding at 12, Building a $2B Google Business at 28: He Tells Young People to Stop Chasing Coding

Xinzhiyuan says Alon Chen coded at 12 and managed a $2B Google business at 28. He argues Gen Z should stop chasing coding, citing 30% AI-written Microsoft code and 25%+ at Google. The sharper signal is execution, problem framing, and communication, not coding as a sole moat.

Why it matters: HKR-H/K/R all pass, but this is a career commentary piece, not a model or product release. The two AI-code-share numbers lift it above generic advice, placing it at the featured threshold.

Take

I don’t buy the leap from “30% of Microsoft code and 25%+ of Google code is AI-written” to “young people should stop chasing coding.” That metric mostly captures completion, boilerplate, and assisted edits. It does not show AI owning requirement decomposition, service boundaries, incident analysis, or production accountability. The summary cites Alon Chen managing a $2B Google business at 28, but the body is inaccessible, so we don’t get the accounting basis: revenue, budget, GMV, or something looser.

AI coding tools have clearly flattened junior CRUD work. Cursor, Copilot, and Claude Code are all eating that layer. But the moat was never typing syntax fast. It is turning messy business intent into testable systems. Using generated-code share as career advice smells too much like management turning cost pressure into a moral lesson.

r/LocalLLaMAMay 6, 04:55

DeepSeek V4 at 17x lower cost prompted a local-vs-cloud coding workflow test

Reddit user spencer_kw logged a 10-day coding workflow and retested 150 tasks on local Qwen 3.6 27B versus cloud models. Local was equivalent for 65% of tasks, acceptable for 20%, and cloud was needed for 15%; the API bill fell from $85/month to about $22. The useful signal is task-based routing, not headline model pricing alone.

Why it matters: HKR-H/K/R all pass: this is a quantified practitioner cost test, not a model launch. The single Reddit sample limits generality, so it lands at the featured threshold rather than P1.

Take

This reads like a personal FinOps audit, not evidence that local coding models beat cloud models. spencer_kw logged 10 days of coding work and retested 150 tasks: local Qwen 3.6 27B was equivalent on 65%, acceptable on 20%, and cloud-only on 15%. The monthly API bill dropped from $85 to about $22. That is a real signal for teams sending log triage, small refactors, and script generation to premium APIs by default.

I don’t buy the “local replaces cloud” framing. The Reddit body is blocked by 403, so task mix, grading method, hardware, electricity, latency, and retry cost are not visible. DeepSeek V4 being 17x cheaper is the hook; the durable win is having task labels and automatic fallback. Without that routing layer, humans become the router, and the savings get eaten by judgment overhead.

May 5Tuesday

r/LocalLLaMAMay 5, 23:40

ProgramBench: Can We Really Rebuild Huge Binaries from Scratch?

ProgramBench released 200 tasks for agents rebuilding programs from target executables and usage files. The team spent about $50k generating 6M lines of black-box behavioral tests, with no internet or decompilation. GitHub, Hugging Face, and Docker images are open-sourced, with pip-based evaluation available.

Why it matters: HKR-H/K/R all pass: a provocative coding-agent failure angle plus concrete benchmark scale and rules. Reddit sourcing and no cross-source cluster keep it in the 78–84 band, not P1.

Take

ProgramBench lands in the right sore spot: it tests whole-program reconstruction, not patch repair. The setup gives agents a target executable plus README-style usage files, then blocks internet access, decompilation, and cheating. The benchmark has 200 tasks and roughly $50k of generated black-box behavioral tests, filtered from 6M lines. That is a cleaner stress test than another curated “agent built an app” thread.

I buy the mechanism more than the headline pessimism. A model must choose a language, design abstractions, and build architecture from observed behavior. That breaks a lot of SWE-bench-shaped muscle memory. The authors also say open models have behaved worse so far, partly from overfitting to SWE-bench-like tasks. Harsh, but plausible: train on patch leaderboards long enough, and you get patch machines.

Synced · WeChatMay 5, 11:59

Anthropic cofounder says AI self-improvement has a 60% chance by 2028

Anthropic cofounder Jack Clark says human-free AI R&D has over a 60% chance by end-2028. He cites SWE-Bench, CORE-Bench, MLE-Bench, and PostTrainBench: Claude Mythos Preview reaches 93.9% on SWE-Bench, and Opus 4.5 reaches 95.5% on CORE-Bench. The key signal is longer task horizons and post-training capability, not the “singularity” framing.

Why it matters: HKR-H/K/R all pass: a named Anthropic cofounder gives a 2028 timeline, backed by benchmark numbers. The headline is overheated, but the concrete claims and practitioner stakes justify P1.

Take

Clark’s end-2028 / 60%+ claim is aggressive, but the evidence still leans on benchmark extrapolation. The disclosed hooks are strong: Claude Mythos Preview at 93.9% on SWE-Bench, and Opus 4.5 at 95.5% on CORE-Bench. That says code and research agents are nearing practical utility. It does not prove human-free AI R&D. Long-horizon failures usually live outside leaderboards: drifting environments, bad decomposition, irreproducible experiments, and wrong error attribution.

I’m more skeptical of Anthropic’s positioning than of the direction of travel. Anthropic sells Claude agents while moving the 2028 risk window forward, which pulls regulation, enterprise buying, and safety budgets into its home turf. The body is only a CAPTCHA page, so Clark’s definition, confidence framing, and counterexamples are not disclosed. Without those, 60% is a narrative anchor, not a calibrated forecast.

r/LocalLLaMAMay 5, 08:31

MTPLX: 2.24x Faster TPS Native MTP Inference Engine for Apple Silicon

MTPLX raises Qwen3.6-27B on a MacBook Pro M5 Max from 28 to 63 tok/s. The test used 4-bit MLX, temperature 0.6, top_p 0.95, top_k 20, with D3 as the best depth. The key detail is native MTP heads: no external drafter and no second-model memory.

Why it matters: HKR-H/K/R all pass: a 2.24x speed hook, concrete test conditions, and a local-inference cost nerve. Reddit single-post sourcing and narrow Apple Silicon scope keep it in low featured, not P1.

r/LocalLLaMAMay 5, 05:58

Benching Local Qwen as a Codex Validator, Co-agent, and Challenger

robert896r1 tested Qwen3.6 27B GGUF beside Codex as a coding validator and released a reproducible eval suite. The runs covered Bartowski, Unsloth, 65k/128k context, and q8/f16 KV cache; three 128k profiles tied for best, with no measured q8 KV accuracy loss in this suite. The useful signal is the sidecar eval: missed directives, overbuilding, UI judgment, and long-context misses, not a universal leaderboard.

Why it matters: HKR-H/K/R all pass: a reproducible sidecar eval with concrete Qwen/Codex conditions beats a normal Reddit tip. Source authority and event scale keep it in the 72–77 band, not a same-day must-write.

Take

Local Qwen3.6 27B looks useful here because it is being used as an engineering checker, not sold as a Codex replacement. robert896r1 put GGUF builds beside Codex and tested Bartowski, Unsloth, 65k/128k context, and q8/f16 KV cache. Three 128k profiles tied for best, and q8 KV showed no accuracy loss in this suite.

I like the setup because the eval targets the failure modes teams actually feel: missed directives, overbuilding, UI judgment, and long-context omissions. SWE-bench tells you whether a model can fix benchmark issues; this is closer to a grumpy reviewer sitting next to the coding agent. The caveat is hard: the Reddit body is blocked with 403, so sample size, task source, and grading rules are not visible. Treat it as a useful sidecar-eval pattern, not a Qwen3.6 27B leaderboard.

May 4Monday

Import AI (Jack Clark)May 4, 20:32

Import AI 455: Automating AI Research

Jack Clark argues that no-human-involved AI R&D has a 60%+ chance of arriving by the end of 2028, citing SWE-Bench gains from Claude 2 at about 2% to Claude Mythos Preview at 93.9%, plus METR task horizons rising from 30 seconds in 2022 to 12 hours in 2026.

Why it matters: HKR-H/K/R all pass: Jack Clark anchors a >60% end-2028 automated-AI-R&D claim in SWE-Bench and METR numbers. This fits the 85–94 band for a notable figure’s AI-timeline essay, below model-release magnitude.

Take

Clark’s 2028 call has weight, but the evidence jumps too cleanly from engineering automation to research automation. SWE-Bench moving from Claude 2 at about 2% to Claude Mythos Preview at 93.9% shows real GitHub issues are nearly saturated. METR’s horizon moving from 30 seconds in 2022 to 12 hours with Opus 4.6 in 2026 also explains why agentic coding suddenly feels usable inside labs.

I get stuck on “build its own successor.” Writing code, testing, cleaning data, and launching runs are not the same as finding a new scaling recipe or diagnosing failed frontier training. Clark admits frontier models are much costlier and involve many humans; that caveat carries the piece. A non-frontier successor proof-of-concept by 2027 or 2028 is plausible. Calling that no-human AI R&D uses a very wide definition.

r/LocalLLaMAMay 4, 19:09

Deep research report with Hermes Agent and qwen3.6-35b-a3b Q6_K

A Reddit user used Hermes Agent and qwen3.6-35b-a3b Q6_K to produce a 21-page research report. The run took 6 loops and over 5 hours on an RTX 4060, at about 28 tokens/s. The repo includes prompts, scripts, intermediate artifacts, and the final report.

Why it matters: HKR-H/K/R all pass: this is a local-agent experiment with hardware, runtime, speed, and artifacts. Reddit source limits reach, so it stays in the 72–77 featured-threshold band.

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.

Xinzhiyuan · WeChatMay 4, 12:04

Claude token rankings: Disney employee hits 460,000 calls in 9 days; Meta burns 60T monthly

Xinzhiyuan says Disney tracks Claude use via an AI Adoption Dashboard, with one employee making about 460,000 calls in 9 workdays. It also says Meta used 60 trillion tokens in 30 days, worth about $9B by public API pricing; the post does not show raw tables. The key issue is that input rankings are not outcomes.

Why it matters: HKR-H/K/R all pass: the hook is concrete usage shock, the post gives dashboard mechanics and token figures, and the nerve is enterprise Claude cost control. Kept at 74 because the data is secondhand and no raw table is disclosed.

Take

This needs cold water: Disney’s one employee making 460,000 Claude calls in 9 workdays and Meta burning 60 trillion tokens in 30 days prove low friction, not good work. The WeChat page is blocked by verification, and the summary says the figures come from media and internal-tool retellings. No raw table, model version, input/output split, or deduping rule is shown.

The $9B Meta estimate also looks shaky. A company at Meta’s scale will have enterprise deals, self-hosted inference, caching, and batch paths; multiplying public API list price by token volume turns accounting into theater. If an enterprise AI dashboard ranks usage alone, it will reward scripts and leaderboard gaming. The useful dashboard ties Claude activity to merged PRs, customer-resolution rate, asset turnaround time, or another measurable outcome.

最佳拍档 (BestPartners)May 4, 07:00

Why Claude Code Got Worse: Anthropic’s Review of Three Bugs

The title says Anthropic reviewed Claude Code regressions involving three bugs. It names reasoning-strength changes, a cache optimization error, and a system-prompt length limit; the post does not disclose repro steps, timeline, or fix status. The key point is AI reviewing AI code under engineering constraints.

Why it matters: HKR-H/K/R all pass, but the post gives three cause categories without repro steps, timeline, or fix status. Claude Code relevance is high, so this sits in the 72–77 band.

Take

Claude Code’s ugly signal is not “the model got dumber.” The named failures sit in engineering seams: reasoning-strength changes, a cache optimization bug, and a system-prompt length limit. The snippet gives no repro steps, timeline, or fix status, so the claim stays under-specified. But those failure modes are exactly where coding agents break in production: state handling, cache invalidation, prompt assembly, and tool sequencing.

Anthropic sells trust and operational discipline, not just benchmark deltas. Claude Code is also a paid, high-frequency surface where regressions are felt immediately. If AI-reviewing-AI-code missed this class of bug, the lesson is uncomfortable: agentic coding still needs boring QA, typed contracts, and rollback discipline before anyone treats it as production infrastructure.

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.