Anthropic / Claude

Everything Anthropic: the Claude models, Claude Code, its safety research agenda and company news.

1,304 picksRelated topicsOpenAI / ChatGPT Google / Gemini Safety & alignment

Latest picks

1121–1140 of 1,304

May 1Friday

Synced · WeChatMay 1, 13:01

Researchers Estimate GPT, Claude, and Gemini Parameter Counts Using API Calls

Bojie Li posted IKP on arXiv to estimate parameter counts of 188 LLMs from 27 vendors via black-box API calls. The dataset has 1,400 questions across 7 rarity tiers, fitted on 89 open models with R²=0.917. Debate centers on synthetic data, MoE effects, and a 90% interval of 0.3x to 3x.

Why it matters: HKR-H/K/R all pass: API-only parameter inference is a strong hook, with concrete counts and error bounds. The 0.3–3x CI limits confidence, so this fits 78–84 featured, not P1.

Take

IKP’s useful move is not “revealing” GPT, Claude, or Gemini parameter counts. It turns vendor secrecy into a falsifiable statistical fight. The setup has real hooks: 1,400 questions, 7 rarity tiers, 89 open models for calibration, and R²=0.917. But a 90% interval from 0.3x to 3x is too wide for calling any single closed model exposed.

I’d treat this as capability fingerprinting. MoE architectures blur total parameters versus active parameters, and synthetic prompts raise dataset-contamination questions. OpenAI, Anthropic, and Google hide parameter counts because model scale is part product narrative, part competitive fog. IKP does not pierce that fog cleanly; it gives practitioners a rough silhouette to argue over. The WeChat body is blocked by verification, so the available detail stops at the summary.

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.

TechCrunch · AIMay 1, 07:07

Sources: Anthropic Potential $900B+ Valuation Round Could Happen Within 2 Weeks

Anthropic asked investors to submit allocations for its latest fundraise within 48 hours, at a potential $900B+ valuation. The title says the round could happen within two weeks; the post does not disclose size, terms, or lead investor.

Why it matters: HKR-H/K/R all pass: TechCrunch reports a $900B+ Anthropic valuation, a 48-hour investor deadline, and a 2-week window. Missing size, terms, and lead investor keep it below the top band.

Take

Anthropic asked investors to submit allocations within 48 hours at a possible valuation above $900B. The title says a round could happen within two weeks. The snippet does not disclose round size, terms, lead investor, secondary sales, revenue, or cloud-credit structure.

My first reaction: $900B is too large to read as a normal private financing mark. It is a scarcity quote. The market is testing whether Anthropic is the only clean frontier-model asset investors can still buy outside OpenAI. That price is not being built from a neat ARR multiple. It is being built from model ranking, enterprise credibility, cloud backing, and fear of missing the last independent lab with real distribution.

The comparison is brutal. Anthropic was reported around much lower private marks during 2025, with numbers in the tens to low hundreds of billions depending on the report. OpenAI also moved into the several-hundred-billion range in 2025 reporting. A $900B Anthropic print would put a private AI lab near the public-market territory of Meta or Tesla. The article gives us none of the accounting needed to judge that leap. No revenue base. No gross margin. No committed compute liabilities. No primary-versus-secondary split. No liquidation preference. On one RSS sentence, I would not treat $900B as a cleared price.

Still, the 48-hour allocation window is not noise. That is how scarce AI private rounds now get run. You do not persuade investors slowly; you force them to preserve access first and diligence later. OpenAI, xAI, and Perplexity financings have all carried some version of that allocation pressure. Anthropic’s version has a cleaner enterprise story. Claude has real developer mindshare, especially in coding and agent workflows. AWS and Google are strategic backers. The company can pitch safety, enterprise trust, and cloud-scale distribution without sounding like a consumer chatbot clone.

I do not buy the easy version of the valuation narrative. Anthropic has concrete strengths: Claude has credibility in coding, long-context work, and enterprise-facing assistants. Its safety brand still matters in procurement rooms. But its weaknesses are just as concrete. It depends heavily on AWS and Google for compute access. It lacks ChatGPT’s consumer distribution. Its API business faces intense price pressure from OpenAI, Google Gemini, DeepSeek-style open models, and Qwen-style open-weight competition. If investors price Anthropic as “the second OpenAI,” they are buying an antitrust-style scarcity slot, not a proven profit machine.

The missing round size matters a lot. A $900B valuation attached to $2B of new money is price discovery. A $900B valuation attached to $30B of primary capital resets the entire private AI market. The economics also matter. Are there cloud credits flowing back to a strategic investor? Are early employees and funds selling secondary shares? Are preferences stacked in a way that protects new money while making the headline number softer? The article does not say. In AI financing stories, the headline valuation is usually loudest, while the preferences carry the real information.

If this round actually closes above $900B within two weeks, the pressure will hit every other model startup. Capital will cluster harder around two or three frontier labs. Everyone else will be pushed toward vertical products, government-backed compute, enterprise deployment, or open-weight distribution. Mistral, Cohere, and Inflection already showed how hard it is to sustain a pure foundation-model valuation without top-tier distribution, massive balance-sheet partners, and repeated benchmark wins.

So I file this as high-noise, high-signal. The article is too thin to validate deal quality. But the combination of a 48-hour deadline and a $900B tag says investors now treat Anthropic as a strategic asset. They are not just underwriting today’s revenue. They are paying for an OpenAI hedge at the model layer. That hedge is expensive enough to reopen the core question for AI practitioners and investors: does frontier-model ROI come from API margin, enterprise seats, cloud bundling, or eventual control by the infrastructure giants?

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.

TechCrunch · AIMay 1, 03:27

After Dissing Anthropic for Limiting Mythos, OpenAI Restricts Access to Cyber, Too

OpenAI will first roll out GPT-5.5 Cyber only to “critical cyber defenders.” The RSS snippet does not disclose eligibility rules, pricing, or launch timing. The access-tiering model is the key detail for practitioners.

Why it matters: HKR-H/K/R all pass, but the body is RSS-only: it confirms tiered access for GPT-5.5 Cyber, not criteria, pricing, or timeline. This fits a lower-featured OpenAI safety product update.

Take

OpenAI will initially restrict GPT-5.5 Cyber to “critical cyber defenders,” and the RSS snippet gives no eligibility rules, pricing, or launch date. Thin article, clear posture: OpenAI is admitting that high-capability cyber tools cannot ship like ordinary API features. After criticizing Anthropic for limiting Mythos, OpenAI is using the same gatekeeping language for its own cyber product. Honestly, the hypocrisy angle is less useful than the pattern. Once a lab’s tool gets close to real offensive workflows, the lab stops acting like a neutral model vendor and starts acting like an access-control authority.

“Critical cyber defenders” is doing a lot of work here. It can mean CISA, national CERTs, critical infrastructure operators, large banks, cloud providers, or managed security firms. The snippet does not say who decides. It does not say whether customers need KYC, target authorization, logging, human review, rate limits, or incident reporting. It does not say whether GPT-5.5 Cyber can generate PoCs, chain exploits, call scanners, write phishing simulations, or automate recon. Those are the details practitioners need. Without them, GPT-5.5 Cyber is not yet assessable as a product. It is only assessable as a release posture.

This fits a broader shift in frontier-lab behavior. Anthropic has treated cyber capability as a safety-threshold category in its Responsible Scaling Policy for a while. OpenAI’s own system cards have also separated CTF-style tasks from real-world exploitation and multi-step autonomous operations. That distinction matters. A model solving toy capture-the-flag tasks is a benchmark story. A tool that helps plan recon, validate vulnerabilities, generate payloads, and summarize exfiltration paths is a governance problem. GPT-5.5 branding tells the market this is not a small helper bolted onto GPT-4-era coding. The burden of proof is higher.

I don’t buy the current wording as enough. If gated access is just an enterprise sales funnel, then this is not a safety policy. It is controlled distribution for governments and large customers. A serious cyber release policy would name capability thresholds and controls: what classes of tasks are blocked, what tool calls are allowed, how customer authorization is verified, how logs are retained, and what triggers suspension. The article discloses none of that. “Only good guys first” is not a technical control. In security, identity is weak unless it is paired with auditable constraints.

The Anthropic comparison is useful even with the missing details. The title says OpenAI criticized Anthropic for limiting Mythos, but the body does not include the exact criticism or Mythos access rules. Still, both companies landing on restricted rollout says plenty. Frontier labs are moving cyber agents from “demoable capability” to “licensed capability.” That is the sane direction. Coding assistants can cause production bugs, IP issues, and bad deploys. Cyber agents can turn into scanning, intrusion support, credential abuse, and ransomware acceleration. As agentic planning improves, content filters alone are not the control plane.

There is also an uncomfortable equity problem. If GPT-5.5 Cyber goes only to organizations OpenAI recognizes as “critical,” the winners will be large cloud providers, federal agencies, defense contractors, banks, and major infrastructure operators. Small hospitals, local governments, school districts, and open-source maintainers are often weaker defenders, and they may not clear the trust bar. Restricted access lowers misuse risk, but it can also widen the defensive capability gap. The better design is capability segmentation: broad access for log triage, patch guidance, vulnerability explanation, and secure configuration review; tighter access for exploit generation, autonomous scanning, and chained offensive workflows. The snippet does not say whether OpenAI is splitting the product that way.

My read is restrained: OpenAI is making the right move, but the disclosure is far too thin. GPT-5.5 Cyber is not a normal model SKU. It forces OpenAI to publish a cyber capability release policy with access criteria, audit controls, task boundaries, and abuse response. Without that, “critical cyber defenders first” is risk-management language, not governance. The hard part of AI security tooling is that the more useful it gets, the more it looks like dual-use infrastructure. Labs cannot market that like SaaS and govern it like a press embargo.

Bloomberg TechnologyMay 1, 01:46

Anthropic Weighs Funding Offers at Over $900 Billion Valuation

Anthropic is weighing a new funding round at a valuation above $900 billion. Bloomberg cites sources; if completed, Anthropic would overtake OpenAI by valuation. The post does not disclose round size, investors, or timing.

Why it matters: Bloomberg reports Anthropic is weighing funding offers above a $900B valuation, enough to reorder the top-lab capital race. HKR-H/K/R all pass, but the deal is not closed and amount, investors, and timeline are undisclosed.

Take

Bloomberg says Anthropic is weighing funding offers above a $900 billion valuation. I would not read this as “Anthropic has beaten OpenAI” yet. The body is only a video snippet. It gives no round size, no investor names, no timing, and no pre-money versus post-money treatment. At this scale, the number stops looking like a clean equity valuation. It smells like a headline blend of structured terms, cloud commitments, strategic demand, and secondary-market scarcity.

The part that makes me cautious is how neatly the number flatters the Anthropic story. Claude has absolutely become a serious enterprise and developer product. The Sonnet 3.5 to Sonnet 4/4.5 arc gave Anthropic real credibility in coding, long-context work, and agent workflows. Plenty of teams building coding agents, internal copilots, and production automation treat Claude as a first-choice model rather than a backup. Anthropic also sells the “safer, auditable, enterprise-friendly” posture better than OpenAI in some procurement rooms. Its Amazon and Google relationships give it distribution that most model labs never get.

But $900 billion is not supported by “the model is good.” That price is close to the gravity field of the largest cloud platforms. OpenAI’s prior private valuations, from what has been publicly discussed, sat in the hundreds of billions. Investors priced it as a bundle: ChatGPT consumer distribution, API revenue, enterprise seats, future agents, and maybe a broader software interface. For Anthropic to pass OpenAI, investors must believe Claude has equal or better revenue certainty. The snippet gives no ARR, no gross margin, no inference cost curve, no cloud obligation detail, no retention data, and no API mix. Without those, $900 billion is a loud anchor, not a business case.

Honestly, Anthropic’s cost structure deserves more skepticism. It is not Meta, which can treat Llama as a platform-defense expense. It is not Google DeepMind, which can lean on internal TPU capacity and Search or Workspace distribution. Anthropic depends on Amazon and Google for capital and compute while also competing against their model products. That relationship is useful, but it is not free. AWS wants Claude as a weapon against Azure/OpenAI. Google wants Anthropic as an external option. Neither side exists to donate margin to Anthropic forever. Model revenue looks beautiful until inference demand turns the compute bill into the senior claim on the business. The article does not say whether cloud credits sit inside the offer. That missing detail matters.

The outside comparison I keep coming back to is OpenAI’s distribution. OpenAI does not need to win every benchmark because ChatGPT owns the default user habit. Anthropic’s strength is different: enterprise trust and strong coding behavior. One looks like an entry point. The other looks like a premium model supplier. Capital usually gives richer multiples to entry points because they can expand into ads, payments, workflow, devices, and operating layers. Premium model suppliers face harsher procurement math. Customers route by latency, price, reliability, and switching cost. Gemini, Qwen, DeepSeek, and Llama do not need to beat Claude everywhere. They only need to be good enough in enough lanes to compress Claude’s pricing power.

I am not saying Anthropic is overvalued in some lazy generic way. It is one of the few labs that built genuine developer preference between OpenAI, Google, and Meta. That is rare. My objection is the jump from “real preference” to “near-monopoly pricing.” I do not buy that jump unless Bloomberg later reports two things: a huge primary raise, plausibly tens of billions, and a strategic investor base tied to multi-year purchase commitments. If the money comes with cloud vendors, sovereign funds, or very large enterprise prepayments, the number becomes easier to understand. If it is mostly secondary scarcity and markups, it tells us more about private-market heat than Anthropic’s operating scale.

There is also a narrative trap here for Anthropic. The company has spent years presenting itself as the safety-forward, alignment-heavy, enterprise-trust lab. A $900 billion valuation forces a different operating tempo. It demands faster revenue targets, heavier sales commitments, and more aggressive product packaging. We already saw this with OpenAI: once the valuation gets huge, the company has to connect ChatGPT, enterprise, agents, video, hardware rumors, and infrastructure into one growth story. If Anthropic really raises near this price, it will need to explain Claude’s platform boundary. “A more reliable model API” is not enough for that valuation band.

So my read is simple: the headline gives a staggering valuation, and the body does not give the mechanism that supports it. Practitioners should not care whether Anthropic tops OpenAI on a private-market leaderboard. They should care who gets tied into the cap table and the commercial contracts. Amazon? Google? Middle Eastern capital? Enterprise prepayments? A secondary tender? Those answers decide whether this is business acceleration or valuation theater. With only the snippet disclosed, I place it in the bucket of private markets repricing frontier model labs. I would not treat it as proof that Anthropic has already earned a $900 billion operating reality.

Apr 30Thursday

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.

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.

TechCrunch · AIApr 30, 08:07

Sources: Anthropic could raise a new $50B round at a valuation of $900B

Sources say Anthropic received multiple pre-emptive offers at $850B–$900B valuations. The title cites a possible $50B round; the post does not disclose investors, terms, or timing. The key check is whether that valuation closes, not Claude feature news.

Why it matters: HKR-H/K/R all pass: huge numbers, a named outlet, and direct pressure on the AI lab funding race. The cap is uncertainty: this is early-offer reporting, with no investors, terms, or timeline disclosed.

Take

Anthropic received pre-emptive offers at $850B–$900B valuations, and the body discloses only that sentence. My read is not “Claude won.” If a $50B round actually closes near that mark, private AI investors are pricing Anthropic like strategic cloud infrastructure, not like a software company. The article gives no investor names, liquidation preferences, secondary component, revenue multiple, burn rate, signed term sheet, or timing. Those missing details matter. A $900B headline valuation can coexist with terms that make common equity far less clean.

Honestly, Anthropic being expensive is not surprising. Claude has earned real trust in developer workflows, enterprise safety reviews, long-context writing, and coding agents. The Sonnet line made the market accept a hard fact: OpenAI is not the only production-grade frontier model vendor. Anthropic also has several distribution lanes: direct API, Claude consumer and team plans, enterprise accounts, Amazon Bedrock, and Google Cloud. When OpenAI negotiated at massive private valuations, the logic was similar. If a model layer captures developer work and corporate Copilot budgets, revenue can ramp faster than classic SaaS.

The $900B number is still aggressive. That is no longer a simple “discount to OpenAI” price. It asks the market to believe Anthropic can hold a top-tier global platform position for years. Against public-market scale, $900B sits near the territory of major cloud and semiconductor franchises. The article gives no ARR, gross margin, inference cost, training capex, retention, or customer concentration. Without those, the valuation question collapses into something blunt: are investors buying Claude’s future cash flows, or are they buying scarce access to the next round?

I am always wary of pre-emptive offers. They are common in hot financings, but outsiders see the valuation range while insiders see preferences, information rights, anti-dilution clauses, and strategic constraints. The 2021 SaaS cycle had plenty of beautiful private marks that later cracked through structure before they showed up as clean down rounds. AI model companies are harder to read than SaaS because revenue grows fast and cost does not behave like normal software cost. Every API dollar carries GPU depreciation, cloud commitments, inference optimization, distillation, cache hit rates, and routing choices. The article gives no gross margin, so I would not treat $900B as a clean verdict on enterprise value.

There is also a distribution problem hiding under the valuation. Anthropic is backed and distributed through both Amazon and Google. That gives it leverage, but it also creates constraints. AWS wants Claude inside Bedrock as an answer to Azure OpenAI. Google wants frontier-model optionality beyond Gemini. Both can help fund compute. Neither wants Anthropic to become fully captured by the other. For a $900B valuation to hold, Anthropic needs to prove it controls customer relationships directly, not just that it is a premium model supplier on hyperscaler shelves. The article does not disclose direct enterprise revenue mix, so that remains unresolved.

Compared with other AI funding stories, xAI sells speed and compute density, OpenAI sells consumer reach and developer platform gravity, and Anthropic sells trusted enterprise models plus coding-agent adoption. Anthropic’s lane fits corporate budgets well. It also risks becoming procurement’s “safer model vendor,” which is a worse multiple than owning the workflow. If Claude Code, Claude Enterprise, and products like Artifacts keep users inside Anthropic-controlled surfaces, the valuation has a path. If most growth flows through Bedrock and cloud resale channels, $900B needs extreme growth and investor-friendly structure to make sense.

The disciplined move is to separate valuation chatter from a closed financing. The title says “could raise.” The body says offers were received. It does not name a lead investor. It does not say a term sheet was signed. The $50B round size appears in the headline, while the snippet gives no round mechanics. For practitioners, the signal is clear enough: capital markets now treat Anthropic as a must-own frontier AI asset. But until revenue, margin, and compute-cost curves appear together, $900B reads more like a price for scarce access than proof that Claude’s business model has already cleared the bar.

Bloomberg TechnologyApr 30, 05:39

Anthropic Considering Funding Offers at Over $900 Billion Value

Anthropic is weighing a new funding round at a valuation above $900 billion. The post cites people familiar with the matter but does not disclose round size, investors, or timing. The key signal is the valuation anchor versus OpenAI.

Why it matters: HKR-H/K/R all pass: Bloomberg gives a striking $900B+ Anthropic valuation anchor with clear market resonance. The deal is not closed and lacks amount, investors, or timing, so it stays in 85–94, not 95+.

Take

Anthropic is weighing funding at a valuation above $900 billion. The body is only an RSS-level snippet. It does not disclose round size, investor names, timing, secondary share mix, term structure, ARR, or inference margin. My read is simple: do not treat this as “Anthropic is worth $900B” yet. Treat it as someone placing a $900B anchor into the market.

That number is too large to process as a normal startup markup. Anthropic was already reported at very high private valuations after its 2025 financings, but this headline moves it into a different class. A $900B valuation puts Anthropic near the largest public technology companies on earth. That requires more than Claude having strong developer love. It requires investors to believe Anthropic can compound into a software and infrastructure cash-flow machine at cloud-provider scale.

Honestly, I have doubts here. Anthropic has real product momentum. Claude Sonnet 4.5 earned strong credibility in coding, long-running tasks, and agent workflows. Claude Code also looks stickier than a generic chat surface because developers wire it into daily work. But a $900B private valuation cannot rest on taste among engineers. It needs revenue, gross margin, compute cost discipline, renewal behavior, and enterprise expansion. The snippet gives none of that.

The OpenAI comparison in the Bloomberg line is useful, but it also flattens the story. OpenAI’s valuation anchor comes from ChatGPT consumer distribution, API usage, enterprise plans, cloud partnership economics, app-platform ambitions, and hardware optionality. Anthropic’s anchor is narrower: safety brand, enterprise trust, coding agents, and strategic ties to Amazon and Google. Narrower can be good. It makes the sales motion cleaner. It also makes the valuation more fragile. If Claude Code growth slows, or enterprises split agent budgets across OpenAI, Gemini, Cursor, Devin, and GitHub Copilot, the $900B mark becomes hard to defend.

There is also a governance detail hiding behind the funding headline. Anthropic is a public benefit corporation, and its governance history includes long-term safety oversight structures. That helps the trust narrative. At a near-trillion-dollar valuation, it becomes a negotiation variable. New money will care about liquidation preferences, board rights, information rights, IPO path, and conflicts between Amazon and Google as strategic backers. The article gives none of those terms. Without them, the valuation number is only half the sheet.

I also do not want to undersell Anthropic. Among model labs, Anthropic and OpenAI have done the strongest job turning agentic coding from a demo into paid workflow. Google’s Gemini has improved fast, but enterprise buying habits still lag model quality. Claude’s reputation in code is not just PR. Teams have put it into IDEs, CI systems, code review, and internal knowledge workflows. If Anthropic is already at multi-billion-dollar annualized revenue, and if inference costs are controlled through cloud contracts and serving optimization, $900B is aggressive rather than pure fantasy. Those are big ifs. The snippet does not answer them.

The stronger interpretation is that this is a capital-cost contest. OpenAI, Anthropic, xAI, and Google DeepMind are not only competing on model quality. They are competing on how cheaply they can buy future capacity. A higher valuation reduces dilution. Lower dilution helps fund GPUs, data centers, power, enterprise sales, and researcher compensation. A $900B headline can affect employee retention, supplier negotiations, and customer confidence even before a round closes. That mechanism is real.

So my stance is split. Anthropic deserves a premium valuation. It has one of the few credible enterprise AI products with real developer pull. I do not buy a one-line “people familiar” report as proof of a $900B clearing price. The next facts that matter are round size, primary versus secondary mix, revenue multiple, investor identity, and whether cloud partners are effectively recycling capital into compute commitments. Until then, $900B is an expensive negotiating posture, not a settled market verdict.

Hacker News front pageApr 30, 01:44

Ramp’s Sheets AI Exfiltrates Financials

PromptArmor disclosed a Ramp Sheets AI flaw with a 6-step attack chain; Ramp said it was fixed on March 16, 2026. A hidden prompt injection in an external sheet made the AI insert an IMAGE formula calling attacker.com with financial data. The key issue is formula insertion without user approval.

Why it matters: HKR-H/K/R all pass: the post gives a concrete exfil path for an AI spreadsheet tool. Scored 82, not 85+, because it is single-source and impact scale is not disclosed.

Apr 29Wednesday

r/LocalLLaMAApr 29, 12:39

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

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

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

TechCrunch · AIApr 29, 02:15

Google expands Pentagon access to its AI after Anthropic refusal

Google signed one new contract with the U.S. DoD after Anthropic refused access. Anthropic barred use for domestic mass surveillance and autonomous weapons; the post does not disclose price, models, or rollout timing.

Why it matters: HKR-H/K/R all pass, but contract value, model scope, and deployment timing are not disclosed. The Google-Anthropic-Pentagon split is discussable, so it clears featured but stays below must-write.

Hacker News front pageApr 29, 02:01

Claude.ai Is Unavailable

Claude.ai’s status page says the service is unavailable; the HN item has 139 points and 105 comments. The post does not disclose scope, start time, cause, or recovery time.

Why it matters: HKR-H/R pass because a live Claude.ai outage directly affects practitioner workflows. HKR-K is weak: the feed gives HN activity, but no scope, cause, start time, or ETA.

The Verge · AIApr 29, 00:49

Claude can now plug directly into Photoshop, Blender, and Ableton

Anthropic launched Claude connectors for creative apps, including Adobe Creative Cloud, Affinity, Blender, Ableton, and Autodesk. The Blender connector can debug scenes, build tools, and batch-apply object changes; the post does not disclose pricing or full availability.

Why it matters: HKR-H/K/R all pass: the hook is Claude inside major creative apps, with concrete connector behavior. Missing price and rollout details keep it below must-write status.

Take

Anthropic launched Claude connectors for Adobe Creative Cloud, Affinity, Blender, Ableton, Autodesk, and more. My read is simple: Anthropic is trying to get Claude out of the chat box and into the tools where creative work already happens. That is the right battlefield. Creative software has brutal lock-in: muscle memory, file formats, plugins, collaboration habits, review loops, and years of weird local workflows. If Claude becomes an action layer inside those tools, it gets stickier usage than another tab with a prompt box.

The disclosed details are still thin. The article says the Blender connector can debug scenes, build new tools, and batch-apply object changes from Claude’s chat interface. It also says connectors can access apps, retrieve data, and take actions in connected services. Pricing is not disclosed. Full availability is not disclosed. Enterprise controls, permission boundaries, audit logs, data retention, local file handling, and rollback behavior are not disclosed. Those omissions matter more here than they would for a toy image feature. A PSD, a Blender scene, an Ableton project, or an Autodesk file can contain unreleased IP, client assets, production methods, and contractual work. “Take actions” sounds useful until an admin asks who approved the action, which layer changed, where the log lives, and how to revert the result.

This also reads like Anthropic patching a distribution weakness. OpenAI has the consumer surface of ChatGPT, plus Canvas, file analysis, custom GPTs, and agent-style tool use. Google has Gemini inside Workspace, Android, and search-adjacent surfaces. Adobe already owns Firefly’s native placement inside Photoshop, Illustrator, Premiere Pro, and its enterprise licensing story. Anthropic does not own an operating system, a browser, an office suite, or a creative suite. Connectors are one of the few plausible ways for Claude to reach durable workflow entry points.

The Adobe angle is the trickiest one. Adobe has every incentive to let external models create value around its apps, but not to surrender the creative control plane. Firefly’s advantage is not only model quality. Its advantage is native access to layers, selections, licensing-safe assets, project history, and enterprise governance. If Claude sits outside as a chat-based automation assistant, it can still be valuable. It can write scripts, batch edits, summarize project state, or generate tool commands. But its ceiling depends on how deep Adobe’s APIs go. The article snippet mentions an Adobe creativity connector, then cuts off before the concrete capability list. That is exactly the missing part I want before taking the launch at face value.

Blender is the cleanest test case. It is open-source, highly scriptable, and already friendly to Python automation. A Claude connector that debugs scenes and builds tools sounds like natural language over Blender Python. That fits the broader pattern we have seen across the last year: Cursor turned the IDE into an agent surface, MCP tried to standardize model-to-tool wiring, and products like Figma, Canva, Runway, and Pika kept moving generation closer to production interfaces. But 3D creative state is nastier than code in some ways. A small object change can affect materials, lighting, cameras, constraints, rigs, render time, and downstream exports. If Claude does not provide visual diffs, undo integration, constraint checks, and reference tracking, professional users will treat it as a flashy macro system.

I have a real doubt about the “Claude for creative work” framing. The bottleneck in serious creative workflows is often not ideation. It is project state management. A designer does not always need twenty more variations. They need the tool not to break version seven, which the client already approved. That demands more than tool calling. Claude needs to understand file structure, version history, team permissions, comments, review context, and production intent. The article does not disclose whether Claude maintains cross-app state. It does not disclose how local files and cloud files are handled. It does not disclose whether actions are sandboxed or reversible. Without those pieces, the launch is demo-friendly automation, not production-grade pipeline integration.

I would also connect this to Anthropic’s Model Context Protocol strategy. Anthropic introduced MCP to make model access to tools, data sources, and local environments less bespoke. If these creative connectors lean on that ecosystem, Anthropic is expanding Claude’s tool surface from developer systems and enterprise knowledge bases into creative production. That is a better fit for Anthropic than shipping a standalone image model and fighting Firefly, Midjourney, Runway, and Google on visual output alone. Claude’s stronger role is planning, scripting, batch operations, review, and cross-tool coordination.

The catch is that creative users do not behave like enterprise SaaS buyers. Blender users will test this through GitHub repos, YouTube tutorials, and brutal community feedback. Ableton users will care about latency, MIDI behavior, plugin chains, and whether a project opens cleanly after Claude touches it. Autodesk customers will care about compliance, permissions, file size, versioning, and deterministic changes. The Verge piece gives breadth and one Blender example, but no benchmark, no pricing, no failure mode, and no governance detail. For practitioners, app coverage is not the maturity signal. The signal is whether Claude can execute a real ten-step workflow inside a messy project, with every step auditable, reversible, and reproducible.

So I am cautiously positive, but not sold. Anthropic picked the right direction: chatbots need to enter paid, habitual software surfaces. But creative software is defended by object models, plugin ecosystems, permissions, and years of workflow sediment. If Claude only helps users press buttons, Adobe Firefly, Autodesk’s own assistants, and strong Blender plugins will box it in. If Claude can read complex project state and produce safe, inspectable action plans, then it becomes part of the production layer. The article does not prove that yet. For now, I read this as Anthropic grabbing workflow entry points, not as proof that creative production has moved to Claude.

Apr 28Tuesday

X · @claudeaiApr 28, 23:07

Claude Now Connects to Tools Creative Professionals Already Use

Claude added a Blender connector for scene debugging, tool building, and batch object edits from Claude. The post does not disclose versions, pricing, or rollout scope; the key issue is agent control boundaries inside DCC workflows.

Why it matters: HKR-H/K/R pass: Claude’s Blender connector is a concrete agent-tool expansion. Missing version, pricing, and rollout details keep it near the featured threshold, not a must-write.

Take

Claude announced a Blender connector on April 28, with only three capabilities disclosed: scene debugging, tool building, and batch object edits. The post is thin, but the direction is not trivial. Anthropic is pushing Claude out of the chat box and into the operating surface of professional software.

Blender is not Figma or Photoshop. Its scene graph, materials, rigs, geometry nodes, modifiers, render settings, and asset references are all scriptable. If Claude only writes Python and asks the user to paste it into Blender, that is old behavior. The word “connector” suggests something stronger: Claude can likely inspect the active scene, identify objects, and execute changes through a live interface. The post does not disclose protocol details, supported Blender versions, pricing, rollout scope, local execution, Claude Desktop requirements, or MCP support. I am not filling those gaps for Anthropic.

My read is that DCC tools expose the hard limits of agents faster than office software. Blender scenes contain concrete objects and deterministic APIs. A file can have 500 meshes, 200 materials, dozens of modifiers, broken texture paths, duplicated names, and inconsistent scale. Batch renaming, validation, cleanup, and tool generation are natural agent tasks. Compared with agents clicking around a browser, Blender has a cleaner action surface and more replayable operations.

The failure modes are also sharper. “Batch-apply changes across every object” sounds useful in a demo and dangerous in production. Does “every object” mean selected objects, visible objects, the whole scene collection, or linked assets? Does Claude touch hidden layers? Does it preserve constraints? Can the undo stack roll back the full operation? Does it produce a diff before writing? If a rig gets renamed incorrectly, downstream animation constraints break. The post says nothing about these boundaries.

I would separate this from Adobe Firefly, Runway, and most Figma AI work. Firefly largely generates assets. Runway generates clips. Figma AI edits at the interface and design-object layer. A Blender connector reaches into production file structure. That is a different level of risk. Once an agent enters an asset pipeline, permissions, audit trails, versioning, and rollback matter more than whether the model sounds smart.

This move also fits Anthropic’s MCP push. MCP’s value is not “the model knows more tools.” It packages tool capabilities into callable, constrained interfaces. Claude Desktop already moved in that direction with connectors for files, GitHub-like workflows, and productivity tools. If the Blender connector follows an MCP-style pattern, Anthropic is testing whether professional apps can be decomposed into safe tool calls instead of giving a model raw GUI control. I think that is the right architecture.

I still have doubts. Creative software agent demos routinely look better than real workflows. Artists do not only want an output. They care about the process. A senior 3D artist wants to know why topology changed, why a shader node was inserted, why a light value moved, and which downstream dependency gets touched. If Claude cannot show diffs, reasoning, and rollback points, it will be used for chores, not serious production edits.

The headline says Claude connects to tools creative professionals already use. The body only proves Blender. It does not establish Maya, Houdini, Cinema 4D, Unreal Engine, Unity, or Adobe support. Blender is open source and unusually automation-friendly, so it is the easiest first stop. That matters. A Blender connector is evidence of direction, not proof that the whole DCC stack has opened.

I would file this under agents entering structured creative environments. It will not automate 3D production on its own, and the post gives no benchmark. The useful test is narrower: can Claude execute small, safe operations inside a complex object graph? If yes, this path extends into Maya pipelines, Houdini procedural graphs, Unity prefabs, and Unreal Blueprints. If no, the Blender connector remains a nicer script generator with better packaging.

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.

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.