#编码

10 today

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.

Synced · WeChatMay 3, 13:35

Why CTOs at Billion-Dollar Companies Are Joining Anthropic as Engineers

Jiqizhixin lists at least six CTOs who joined Anthropic as individual contributors. Cases include Workday, You.com, Box, Super.com, and Adept AI from Jan 2025 to Apr 2026. The key issue is career leverage, not just AGI mission talk.

Why it matters: HKR-H/K/R all pass: the career-status reversal is clickable, the post gives 6 cases, and it touches AI talent competition. No hard exclusion, but it is commentary, not a model or product release.

Take

Anthropic pulling six CTOs into individual-contributor roles says the leverage in AI has moved from managing teams to touching the model factory. The reported list spans Workday, You.com, Box, Super.com, and Adept AI, with moves from Jan 2025 to Apr 2026. That is not one founder chasing vibes; it is a cluster across SaaS, search, collaboration, and agent companies.

I don’t buy the clean “AGI mission” framing. A CTO title at a normal software company gives budget and roadmap control. An IC seat at Anthropic can put you closer to Claude’s agent, code, or infra path. OpenAI, Anthropic, and DeepMind have spent the last year turning model access into a recruiting weapon. The WeChat body is blocked here, so compensation and exact roles are not disclosed; without those, “executives gave up power for purpose” is too neat.

Xinzhiyuan · WeChatMay 3, 13:06

Claude Code helps Anthropic double revenue pace in two months

Semi Analysis says Anthropic’s ARR reached $44B, adding $35B over 12 months. Claude Code hit $2.5B annualized revenue by Feb 2026, while inference gross margin rose from 38% to over 70%. The key test is keeping enterprise usage, coding-agent revenue, and inference margin together.

Why it matters: HKR-H/K/R all pass: SemiAnalysis gives hard ARR, Claude Code revenue, and inference-margin numbers. Not a model launch, but it materially shifts the view of Claude Code monetization.

r/LocalLLaMAMay 3, 02:11

Built a C++17 transformer from scratch with 0.83M params and CPU training

Reddit user Suspicious_Gap1121 released Quadtrix.cpp, a C++17 GPT-style model with 0.83M parameters. It uses 4 layers, 4 heads, 200d width, and a 128-character context; one CPU core trained on 31.4M characters for 76.2 minutes to 1.6371 nats val loss. The key detail is handwritten backprop for LayerNorm, attention, Q/K/V, dropout, and AdamW without PyTorch, BLAS, or autograd.

Why it matters: HKR-H/K/R all pass: the no-framework C++17 build is clickable, the training setup is specific, and local-LLM builders care about dependency-free control. It stays in the 72–77 band because it is a small personal project.

May 2Saturday

QbitAI · WeChatMay 2, 10:42

Apple Support App Accidentally Shipped Claude.md, Revealing Internal Claude Code Use

Apple Support v5.13 shipped a Claude.md file on May 1 and was pulled within 24 hours. The file describes Juno AI and Live Agents switching through a Protocol layer, with client, agent, and assistant messages handled in one flow. The key issue is release review; the post does not disclose how the file entered production.

Why it matters: HKR-H/K/R all pass, but this is still an app-packaging incident, not a model or platform release. Apple scale and Claude.md details clear the featured bar; the review-chain failure is not disclosed.

Take

Apple’s miss here is release governance, not the fact that its teams use Claude. The hard facts are narrow but ugly: Apple Support v5.13 shipped on May 1 with a Claude.md file, then was pulled within 24 hours. The file reportedly names Juno AI and Live Agents switching through a Protocol layer, with client, agent, and assistant messages sharing one flow.

I don’t buy the cheap “Apple is vibe coding” dunk. Everyone serious is using coding agents inside product teams now. The stranger part is that an internal Claude.md made it into a production app from a company that markets operational taste. A shared protocol for AI support and human agents is sensible; OpenAI and Anthropic have spent the last year pushing agent workflows in the same direction. The article body is only a CAPTCHA page here, so the missing piece is the path through packaging, review, and App Store release.

TechCrunch · AIMay 2, 07:06

Replit's Amjad Masad on the Cursor deal, fighting Apple, and why he'd rather not sell

Replit grew from $2.8M in 2024 revenue to a billion-dollar annualized target. The excerpt says Cursor is reportedly discussing a $60B SpaceX acquisition; the post does not disclose Masad's full Apple or sale comments.

Why it matters: HKR-H/K/R pass: TechCrunch has the Cursor $60B hook, Replit revenue target, and coding-tool exit tension. The excerpt lacks Masad’s full Apple and sale comments, so this stays in the 72–77 band.

May 1Friday

r/LocalLLaMAMay 1, 22:53

PFlash: 10x prefill speedup over llama.cpp at 128K on an RTX 3090

PFlash cuts Qwen3.6-27B Q4_K_M 128K TTFT to 24.8s on an RTX 3090, versus 248.4s cold for llama.cpp. It uses a Qwen3-0.6B drafter to score token importance, keeps 5% of spans, and runs C++/CUDA without Python, Triton, or PyTorch. The quality caveat is clear: only NIAH single-needle passes from 32K to 128K; RULER and multi-needle results are not disclosed.

Why it matters: HKR-H/K/R all pass, but this is a single Reddit claim with quality evidence limited to single-needle NIAH 32K–128K. RULER and multi-needle results are not disclosed, so it stays at featured threshold.

Xinzhiyuan · WeChatMay 1, 13:29

Claude Code's Real Story: 98.4% of What Works Is Engineering, Not AI

VILA-Lab analyzed 512,000 lines of Claude Code v2.1.88 and found 1.6% tied to AI decision logic. The other 98.4% is deterministic infrastructure: permissions, context, tool routing, and error recovery. The key shift is harness design, not longer prompts.

Why it matters: Strong HKR: the Claude Code teardown has a sharp counter-narrative and concrete 512k LOC plus 1.6%/98.4% split. It is not an official Anthropic release and lacks full reproduction details, so it stays in the 78–84 band.

Take

Claude Code’s exposed number is the knife here: 1.6% of 512,000 lines is described as AI decision logic, while the rest is permissions, context management, tool routing, and error recovery. The WeChat body is blocked by verification, so the methodology, file classification, and dependency boundaries are not verifiable. Treat 98.4% as a directional claim, not a clean audit result.

I buy the direction. The gap between coding agents over the last year has come less from mystical prompts and more from whether the product can run shell commands, edit a repo, recover from failure, and keep context under control. OpenAI Codex, Cursor, and Claude Code are all fighting in that wrapper layer. A stronger model gets you in the room; a safer harness decides whether an engineering team lets it touch production code.

Xinzhiyuan · WeChatMay 1, 13:29

OpenAI upgrades Codex to control Macs and run cross-app tasks

OpenAI upgraded Codex with Slack, Google Workspace, and Microsoft 365 integrations. Mike Russell tested Codex on a Mac across Adobe Audition, Photoshop, and Firefly, finishing in about 8 minutes with an 85–90 score. The key shift is OS-level computer control, not code completion.

Why it matters: All HKR axes pass: OpenAI Codex moves from coding into Mac-level control, with Slack, Google Workspace, and Microsoft 365 integrations. Single-source sourcing caps the score, but the 8-minute test and OS-agent angle justify P1.

Latent SpaceMay 1, 12:53

[AINews] Agents for Everything Else: Codex for Knowledge Work, Claude for Creative Work

OpenAI expanded Codex to non-coding work, with CUA reported 42% faster. The update connects Microsoft, Google, and Salesforce, covering docs, slides, spreadsheets, research, and planning. The key signal is GUI-agent productization, not one benchmark score.

Why it matters: HKR-H/K/R all pass: Codex moves into non-code GUI work, with a 42% speed claim and named integrations. Price, rollout scope, and reproduction details are not disclosed, so it stays below P1.

Hacker News front pageMay 1, 04:55

Show HN: Pu.sh – a full coding-agent harness in 400 lines of shell

Pu.sh ships a coding-agent harness in about 400 lines of shell, using only sh, curl, and awk. It supports Anthropic and OpenAI, 7 tools, REPL, auto-compaction, checkpoint/resume, pipe mode, and 90 no-API tests. It excludes TUI, streaming, images, OAuth, and Windows.

Why it matters: HKR-H/K/R all pass, but this is a small Show HN open-source tool, not a model or platform release. HN frontpage plus a reproducible 400-line implementation clears the featured bar.

r/LocalLLaMAMay 1, 04:19

Long-context coding on RTX 5080 16GB: Qwen3.6-35B-A3B holds 30 t/s at 128K

A Reddit user tested a local coding-agent setup on RTX 5080 16GB; the title says Qwen3.6-35B-A3B reaches 30 t/s at 128K. The post lists Ryzen 9700X, 96GB DDR5, Windows 11, and CUDA 12.9.1 as required. Qwen3.6-27B dense hit only 3.2 t/s at 128K, so the key path is KV quantization plus MoE offload.

Why it matters: HKR-H/K/R all pass: 30 t/s at 128K on a 16GB RTX 5080 is a strong hook, with hardware/CUDA details and a dense baseline. Single Reddit run lacks multi-source reproduction, so featured not P1.

Apr 30Thursday

r/LocalLLaMAApr 30, 22:49

My calculator is a transformer

radarsat1 shows an RPN interpreter compiled into Transformer weights; “2 3 + 2 *” returns 10. The residual stream acts as registers, attention weights are compiler-calculated, while nonlinear MLP logic is still trained. The prototype is 1.1 GB; the key point is calculable attention weights, not a practical calculator.

Why it matters: HKR-H comes from the counterintuitive title; HKR-K has a reproducible input, weight-construction mechanism, and 1.1GB figure. HKR-R is real but niche, so this stays just above featured threshold, below 78.

The Verge · AIApr 30, 21:42

OpenAI talks about not talking about goblins

OpenAI explained instructions telling its coding model to avoid goblins and similar creatures after Wired reported them. OpenAI says GPT-5.1’s “Nerdy” personality began using creature metaphors; the post does not disclose the full fix.

Why it matters: HKR-H/K/R all pass: the goblins prompt is unusual, OpenAI names the GPT-5.1 Nerdy persona behavior, and coders care about hidden prompt reliability. No full fix mechanism is disclosed, so it stays in the low featured band.

Take

OpenAI says GPT-5.1’s Nerdy personality began producing goblin metaphors, and later models made it worse.

I don’t read this as a funny model anecdote. I read it as a control failure leaking through a joke-shaped crack. A coding model apparently needed an internal instruction to “never talk about goblins, gremlins, raccoons, trolls, ogres, pigeons, or other animals or creatures.” That is not just quirky tone. It says OpenAI still has an unresolved boundary problem between persona, explanation style, task strategy, and tool behavior. The body only gives the RSS-level version: GPT-5.1’s Nerdy personality started the creature metaphors, later models worsened it, and Wired surfaced the internal prompt. It does not disclose the full system prompt, trigger rate, eval setup, product surface, or final fix.

For coding models, the bad outcome is not one weird sentence. The bad outcome is style becoming task policy. If a model repeatedly frames bugs as goblins, it starts steering the debugging interaction around a metaphor. In casual chat, that is cringe. In a code review, terminal agent, PR comment, or incident thread, it becomes noise in the work artifact. The disclosed instruction also smells like a negative prompt patch. Anyone who has maintained system prompts knows the failure mode: “never mention goblins” blocks the literal token class, then the model slides into “sprites,” “critters,” “little monsters,” or some adjacent metaphor. The article does not disclose the repair mechanism, so I won’t claim OpenAI only used prompt patching. But if the main fix is a ban list, it is a brittle fix.

This sits on the same line as OpenAI’s sycophancy incident. OpenAI previously acknowledged that a ChatGPT update became too eager to flatter users, then rolled it back and adjusted behavior. That failure lived in the social layer. This one lives in the work layer. The difference matters. Coding outputs get pasted into pull requests, issue comments, CI logs, commit messages, and internal docs. Once tone pollution enters those surfaces, it stops being a consumer UX quirk. Enterprise buyers then ask an ugly but fair question: how many undisclosed behavior bans exist inside this model, and do any of them conflict with my company policy?

I have always been skeptical of heavy persona tuning inside developer tools. ChatGPT needs personality because consumer retention depends on tone, memory, and affect. Codex should have low personality density by default. Claude Code’s developer goodwill has not come from being cute. It has come from feeling closer to a tool in a terminal, with less theatrical residue. Anthropic has its own style issues; Claude still over-apologizes and over-explains in some workflows. But in coding, low drama is a capability. If OpenAI carried a Nerdy persona experiment from GPT-5.1 into later coding behavior, then let that habit amplify, that suggests the training, preference, and product-persona layers were not isolated enough.

There is also a more technical possibility here: this may be synthetic-data feedback. The last year of model training has leaned heavily on model-generated traces, especially for code and reasoning. If a high-rated answer used “debugging goblin” as a charming explanatory device, a preference model can learn the wrong feature. It may score the answer as helpful, vivid, or user-friendly, then preserve the metaphor in distilled data. Another training pass turns the joke into a stable behavioral groove. The article says GPT-5.1 started it and later models worsened it, which fits that kind of amplification loop. OpenAI does not disclose the data mix or RL details here, so this is a hypothesis, not a claim.

The part I do not buy is calling this a “strange habit.” That phrase is too soft. For users, model habits are product behavior. For enterprise customers, product behavior is risk surface. A coding model needing an internal goblin ban tells me OpenAI is maintaining a layer of tiny, embarrassing behavior patches. Anyone who has shipped LLM products knows these patches never come alone. Today it is goblins. Tomorrow it is emoji spam, fake test names, haunted-stacktrace language, roleplay phrasing in security audits, or cutesy summaries in serious incident work. Each item looks small. Together they become system-prompt debt.

The Verge item is thin because it is an RSS snippet. It does not include before-and-after evals, a reproduction condition, the final mitigation, or whether Wired saw a full instruction stack or one fragment. So the hard conclusion is product-governance, not benchmark-level. OpenAI should stop treating persona as a shared asset across ChatGPT and coding agents. Codex-like tools should default to minimal persona, with workspace-level style only when a team explicitly opts in. Developers do not need goblins. They need repeatable, auditable, low-noise model behavior.

Ben's BitesApr 30, 21:03

Building Gets Easier

Ben’s Bites lists agent tooling updates from Cloudflare, Stripe, Cursor SDK and others, with over 10 product leads. Cloudflare lets agents create accounts, buy domains, get API tokens and deploy; Stripe adds Agentic Commerce Suite, Link CLI and agent-ready Treasury accounts. The key shift is external permissions becoming agent-readable interfaces.

Why it matters: HKR-H/K/R pass, but this is a roundup rather than one major launch. Concrete Cloudflare and Stripe agent-permission details keep it in the featured-low band.

r/LocalLLaMAApr 30, 20:51

Actual comparison between locally run Qwen-3.6-27B and proprietary models

The author compared 5 model setups on an autoresearch-loop task; only Qwen-3.6-27B via OpenRouter nearly solved it. The local q4_k_m run took about 8 hours and used 39k/45k tokens; full-quality Qwen used 4.4M tokens and cost $0.939. The useful signal is failure quality: both Qwen runs needed small fixes, while Gemma, Codex-Spark, and Claude Haiku 4.5 missed tests or key logic.

Why it matters: HKR-H/K/R all pass: the post has a concrete agent-test surprise, token and cost data, and local-vs-proprietary tension. Single Reddit run limits source authority, so it stays in the lower featured band.

r/LocalLLaMAApr 30, 18:39

Notes on what actually breaks when you run a coding agent on small local models

A Reddit user tested small local and free-tier cloud models for weeks on multi-file coding tasks. Sub-7B structured output was unreliable; failures included markdown fences, wrong-file edits, and read/write misclassification, with post-processing and validation as fixes.

Why it matters: HKR-H/K/R pass: the post names real local coding-agent failure points, a sub-7B threshold, four failure classes, and mitigations. Reddit single-post scope keeps it below release-tier news, so 75.

Take

Sub-7B models break first at the tool contract, not at code syntax. The summary names four failure modes: markdown fences, unstable structured output, wrong-file edits, and read/write misclassification. The fixes are boring but telling: JSON validation, path checks, post-processing, and read-only routing. Reddit blocks the body with a 403, so model names, task set, and failure rates are not disclosed.

I buy the direction because it matches local-agent pain this year. Qwen and Gemma-class small models can look fine in single-turn code completion, then leak constraints once a multi-file state machine is involved. Don’t read this as “small models can’t code.” The sharper read is that small models work as local operators, but they still need a hard harness for format, permissions, and file state.

Xinzhiyuan · WeChatApr 30, 13:00

AI Raw Proofs Pile Up on GitHub as Terence Tao Says Solving Alone Is Not Enough

Terence Tao says math is shifting from proof scarcity to proof abundance, with 20-plus AI solutions pending assessment on an Erdős problems GitHub page. The post says GPT-5.4 Pro generated an Erdős #1196 approach in 80 minutes, and Tao verified the core within 24 hours. The key issue is verification and digestion workflow, not raw proof count.

Why it matters: All HKR axes pass: Tao plus GitHub proof backlog gives HKR-H, while 20+ pending AI solutions and an 80-minute GPT-5.4 Pro claim give HKR-K. This is not a model release, so it stays below 85.

Synced · WeChatApr 30, 12:50

Alec Radford tests Hassabis’s AGI challenge with a model trained on pre-1931 data

Alec Radford’s team trained 13B talkie on 260B English tokens dated before 1931. They tested surprise on nearly 5,000 historical events and used HumanEval for lower-contamination code evaluation. The key issue is time leakage: the 13B model still has vague post-WWII knowledge.

Why it matters: HKR-H/K/R all pass: the 1930 cutoff is a sharp hook, the post gives 260B tokens and ~5,000 event tests, and the finding targets data leakage. This is strong research, not a model or platform release, so 78–84 fits.

Take

Radford’s experiment lands hardest on data cleanliness, not model nostalgia. The setup is unusually clean on paper: a 13B talkie trained only on pre-1931 English text, with 260B tokens, surprise testing across nearly 5,000 historical events, and HumanEval used as a lower-contamination code probe. Yet the 13B model still showed vague awareness of post-WWII events.

That is a bad look for a lot of benchmark hygiene claims. I can only see the title and summary, not the full paper details, so the leak examples, dedup rules, and provenance filters are not disclosed here. But the direction is clear: timestamping text is a weaker filter than people pretend. Citations, later edits, OCR artifacts, and document metadata all carry future signals. Hassabis’s “model frozen in time” challenge is not about picking a cutoff year; it is about proving the cutoff survived contact with the corpus.

Latent SpaceApr 30, 09:42

[AINews] The Inference Inflection

Latent Space argues inference demand has hit an inflection point, citing its Apr 28-29, 2026 AINews roundup. Jensen Huang is quoted saying per-task compute rose about 10,000x in two years, with usage up about 100x. The key watchpoints are CPU sandboxes, agent harnesses, and split inference workloads.

Why it matters: HKR-H/K/R all pass, but this is a Latent Space AINews roundup and trend read, not a model launch or major product release. It fits the upper featured-threshold band for insightful commentary.

Take

The useful claim here is that agent economics are moving beyond token pricing into runtime infrastructure. Jensen Huang gives the loud numbers: roughly 10,000x more compute per task in two years, plus about 100x more usage. Intel CEO Lip-Bu Tan then pulls CPU demand into the Q1 earnings story. That matters because Claude Code, RL gyms, browser agents, test runners, and file-system sandboxes burn CPU outside the model call.

I still don’t fully buy Intel’s framing. A CEO has every reason to sell a five-to-six-year server refresh as AI demand. But the SemiAnalysis point is hard to dismiss: 2020-2021 saw roughly $100B of CPU buying, and that fleet is hitting replacement age just as production agents need cheap sandboxes. GPUs set model ceilings; CPUs decide whether agents can work without blowing the margin.

r/LocalLLaMAApr 30, 01:19

inclusionAI/Ling-2.6-1T · Hugging Face

inclusionAI open-sourced Ling-2.6-1T on Hugging Face, with 1 trillion parameters. It uses MLA plus Linear Attention and Contextual Process Redundancy Suppression to reduce CoT overhead. The post cites AIME26 and SWE-bench Verified but does not disclose scores.

Why it matters: HKR-H/K/R all pass, but benchmark scores for AIME26 and SWE-bench Verified are not disclosed. A 1T open model with a named architecture mechanism fits featured, not P1.

Apr 29Wednesday

X · @doteyApr 29, 07:11

OpenAI Expands AWS Partnership, Bringing GPT-5.5, Codex, and Managed Agents to Bedrock

OpenAI expanded its AWS partnership, bringing GPT-5.5, Codex, and Managed Agents to Amazon Bedrock in limited preview. Codex supports Bedrock across CLI, desktop, and VS Code, with over 4M weekly active users. The key detail is reuse of AWS compliance, billing, and cloud commitments.

Why it matters: HKR-H/K/R all pass: this is more than a routine cloud listing, with OpenAI bringing GPT-5.5, Codex, and Managed Agents to AWS Bedrock. Limited preview, 4M weekly Codex users, and IDE/CLI entry points justify same-day coverage.

Take

OpenAI put GPT-5.5, Codex, and Managed Agents on Amazon Bedrock, with access limited to preview for now. I read this as OpenAI conceding a hard enterprise distribution fact: model quality does not bypass cloud contracts, compliance reviews, IAM, billing, and procurement. OpenAI’s commercial path has been tied tightly to Microsoft, with Azure OpenAI Service as the default enterprise door. Putting the latest GPT-5.5 on Bedrock, rather than only an older or constrained model, tells me OpenAI does not want AWS-heavy customers drifting toward Claude, Llama, Mistral, or Cohere by default.

The first-order impact is procurement, not API routing. The article says Codex spend can count toward AWS cloud commitments. That detail matters more than another endpoint. Large companies often have three-year or five-year AWS enterprise agreements, with tens or hundreds of millions of dollars in committed spend. Asking a CIO to open a new OpenAI vendor path, restart security review, negotiate fresh legal terms, and wire new billing creates friction. Bedrock turns GPT-5.5 and Codex into an expansion of existing AWS consumption. Internally, the customer sees the same vendor, VPC patterns, KMS, CloudTrail, IAM, GuardDuty, and billing center.

This weakens Azure’s scarcity story. Microsoft has had a very comfortable enterprise AI stack: Azure OpenAI Service for controlled model access, GitHub Copilot for developers, and Microsoft 365 Copilot for office workflows. AWS has never lacked enterprise customers. Its problem was that its frontier closed-model story did not carry the same brand weight. Anthropic is deeply integrated into Bedrock, and Amazon has invested billions of dollars in Anthropic. Still, many executives treat “OpenAI” as the default brand for generative AI. GPT-5.5 entering Bedrock gives AWS sales a cleaner pitch: Claude, Llama, and OpenAI are all in one AWS control plane, so the customer does not need to change clouds for the model.

Codex’s 4 million weekly active users is the number I would not ignore. The article names CLI, desktop, and VS Code extension support. That is broader than an IDE plugin strategy. OpenAI is pushing Codex from code completion toward a general enterprise work agent. The article says usage has expanded into research, document handling, and presentations. I have some doubts here because the body does not disclose usage mix, retention, paid conversion, or enterprise seat count. Four million WAU means very different things if most activity is free developer usage. Still, once Bedrock billing can absorb Codex into committed AWS spend, CFO resistance drops.

I am more cautious on Managed Agents. The article says enterprises can deploy OpenAI-powered agents on AWS, with context persistence, multi-step task execution, tool use, and AWS-managed orchestration, governance, and compliance. That sounds clean, but several critical facts are missing. The body does not disclose context window, tool-call retry behavior, state storage, audit-log granularity, human approval controls, regional availability, or data-retention terms. Enterprise agents do not fail because demos cannot run three steps. They fail on permissions, rollback, cost caps, and accountability. Bedrock already had agent tooling, while OpenAI has been pushing its own Agents SDK and Responses API path. Without the docs, this can easily become cloud-hosted workflow management plus model calls under a new label.

There is also a strategic tension OpenAI is not spelling out. If GPT-5.5 is the latest model, why is Bedrock access only in limited preview rather than general availability? One explanation is AWS-side readiness: capacity, safety gating, regional controls, or enterprise support are not fully baked. Another explanation is partner politics. OpenAI still has a deep Microsoft relationship across compute and commercialization. A broad Bedrock launch would dilute part of Azure’s OpenAI advantage. This kind of deal never moves only on product logic. GPT-5.5 on Bedrock helps AWS, but it does not erase Azure OpenAI’s installed base. Customers already standardized on Azure compliance, Power Platform, GitHub Enterprise, and Microsoft 365 Copilot will not migrate because Bedrock gained GPT-5.5.

The larger change is that multi-cloud model procurement is becoming normal. Enterprises have already been assembling stacks like Claude on Bedrock, OpenAI on Azure, open or custom models on SageMaker, Vertex AI, Databricks, or Snowflake. The problem has been fragmented governance. If Bedrock absorbs OpenAI, AWS gets to pitch itself as a neutral model control plane. I do not fully buy the neutrality claim. Cloud providers always bias toward their own billing, networking, security, and observability layers. But procurement teams do not need perfect neutrality. They need fewer reviews, fewer invoices, and cleaner audit trails.

So the weight of this news is not that GPT-5.5 is better. The article gives no benchmark, pricing, context length, rate limits, region list, or retention policy, so those cannot be inferred. The weight is that OpenAI is letting AWS enterprises buy current OpenAI products without leaving AWS. For Anthropic, that pressures Claude’s default position inside Bedrock. For Microsoft, it is not a disaster, but Azure OpenAI’s scarcity got cut. For developer tools, Codex entering the AWS bill matters more than another VS Code integration. Enterprise AI spending often gets decided inside procurement systems, where the winning product is the one that is auditable, billable, and already covered by a cloud commitment.

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.