Anthropic's draft S-1 shows an $80.7B loss that is mostly non-cash; also: MemoryTax on agent memory costs, Claude's automated alignment researchers revisited, Jalapeño's vendor-run benchmarks, and Mojo's open compiler

Lead stories

Anthropic's draft prospectus: $16.3B of half-year revenue, an $80.7B loss that is mostly accounting, and a compute bill measured in hundreds of billions

1 source, 7 min read

What happened. The Wall Street Journal reported on 20 October 2026 that it had reviewed a draft of Anthropic's IPO prospectus, a draft S-1. The Vested Shorts newsletter summarised the main figures on 25 October. The draft shows first-half 2026 revenue of $16.3 billion, against $1.1 billion in the same six months of 2025, and a net loss of $80.7 billion. Vested says about $72 billion of that loss came from non-cash accounting adjustments tied to convertible notes. Vested's framing is that "about 90% of that loss wasn't in cash", and it adds that this is "a draft seen by one newspaper, not a public filing" source. The WSJ article itself was not read for this issue. Every figure below reaches the reader through outlets that cite it: Vested, Dealroom (Dealroom) and MACCUS (MACCUS). Anthropic declined to comment, according to those reports.

Details. The reports agree on the core numbers. Dealroom, dated 21 October, gives $16.3 billion of first-half revenue, an $80.7 billion net loss, about $72 billion of "non-cash accounting charges tied to financial instruments", nearly $9 billion spent on compute and infrastructure in the first half against $7.3 billion in all of 2025, and roughly 20% of revenue from two customers (Dealroom). Third-quarter revenue was $16.8 billion, up 45% on the second quarter. Dealroom says Anthropic "separately told investors" that figure. MACCUS attributes it to Reuters citing an investor. Neither source places it in the draft S-1, and Vested presents it without that distinction source. MACCUS fills in the rest of the quarterly path: Q2 revenue of $11.5 billion per the Financial Times, and Q1 of about $4.8 billion, which MACCUS itself calculated by subtraction. It also gives 2025 figures of about $4.6 billion in revenue and a $42 billion net loss, and first-half 2025 compute spending of $2.3 billion (MACCUS).

The forward commitments are the largest numbers here. Vested says Anthropic signed cloud agreements worth about $450 billion "over the next decade": $111 billion with Google Cloud, $110 billion with AWS and $31 billion with Microsoft. Vested adds that "much of that is payable whether the capacity gets used or not", and that including deals still under negotiation the total "could reach $750 billion" source. MACCUS splits this further. The cloud contracts total about $450 billion, are mostly non-cancellable and run 7 to 10 years. Chip leases take the total past $600 billion. Deals under negotiation could add up to $150 billion more, which is how the $750 billion figure is reached. MACCUS also notes that Reuters estimated $518 billion in September (MACCUS). Vested's line that Anthropic "has committed roughly fourteen years of present revenue" is its own arithmetic, $450 billion over an annualised first half, and is not a figure from the filing source.

The capacity detail matters most to anyone building on Claude. Vested says the filing reportedly states that Anthropic asked the big cloud providers for more capacity than they were willing to supply, so it now leases its own data centres and hires third-party operators source. MACCUS adds two points: citing TechCrunch, it says the draft warns that those operators have a "limited operating history", and citing passages quoted by the New York Post, it says local opposition to data centres has "become more organized and coordinated across jurisdictions" (MACCUS). Dealroom's summary of the risk section says Anthropic "struggles to secure enough compute from AWS, Google and Microsoft". It says those providers "increasingly treat it as a competitor rather than a customer", that compute access could be "curtailed, repriced, or terminated", and that "a catastrophic AI incident could exceed its insurance coverage" (Dealroom).

On the loss itself, Vested explains that convertible notes become worth more as the company's implied share price rises, and accounting rules book that increase as an expense. Vested then says that if the charge is stripped out, "the operating hole is roughly $9 billion" source. MACCUS performs the same subtraction and gets "about $8.7 billion". It says plainly that this "adjusted" figure is its own calculation and not an official or non-GAAP number from Anthropic (MACCUS). Vested's word "operating" is loose here. Net loss minus a financing-instrument charge is not the same thing as operating loss, and neither source gives the first-half operating loss.

Facts vs. opinions. The underlying fact base is a draft document, reported by one newspaper, unconfirmed by the company, and subject to change before any public filing. MACCUS notes that the SEC requires drafts to be made public at least 15 days before the roadshow, and that "the numbers could still change before the public filing" (MACCUS). Several things are reported claims rather than established facts: the listing timing ("as soon as November 2026"), the valuation ("reports have pegged" about $2 trillion), and the Q3 number, which comes from an investor channel (Dealroom). Interpretations are opinion: the "~$9 billion" real loss, the fourteen-years-of-revenue framing, and Vested's closing line that markets "priced what companies said they intend to do" source. On Reddit the headline travelled faster than the footnote. A r/technology post titled "Anthropic logged net loss of over $80 billion in first half of 2026" reached roughly 29,000 points, while a r/ClaudeAI post that led with "$80.7B loss on paper" drew 187. This shows how the story was received, not what the numbers mean.

Other perspectives. The most bearish view on record comes from New Constructs. Its 6 October piece by Kyle Guske II, quoted by Vested, opens with "Anthropic's IPO is an unprecedented test of investor gullibility" (New Constructs). Its reverse discounted-cash-flow model uses a 9.33% weighted average cost of capital and subtracts $518 billion of "cloud, compute, and infrastructure obligations" as liabilities. To justify $2 trillion, it says Anthropic would need to "grow revenue by 1000% in 2026 and 100% in 2027", then 56% a year compounded from 2028 to 2035, at a 10% NOPAT margin. Its downside scenarios give about $1.1 trillion and $144 billion. The core argument is that "large language models are becoming commodities, and commodity businesses don't deserve $2 trillion stock valuations." New Constructs is candid that it had not seen the S-1 ("we were not fortunate enough to be one of the few to whom Anthropic's S-1 was selectively disclosed"). It also says its own inputs "may prove too optimistic". Its 2025 figures came from an earlier leaked draft: an operating loss that "increased from -$3 billion in 2024 to -$8 billion in 2025", and a $42 billion net loss that "includes a $34 billion charge tied to convertible instrument revaluations" (New Constructs).

On growth, MACCUS pushes back on a Reddit reading that revenue "flattened out since June". Its view is that "the published figures point to a slowdown instead": revenue "more than doubled from the first quarter to the second, then grew 45% in the third." In other words, growth is decelerating, not stalling (MACCUS). Dealroom's update quotes Chamath Palihapitiya saying "I do think that we have achieved AGI". That is an investor's opinion, not evidence about the filing (Dealroom). The commoditisation argument and the growth trajectory point in opposite directions. The sources do not settle which one wins.

The same Vested issue carries two adjacent items worth a short check. On Lam Research, the company's own release for the quarter ended 27 September confirms revenue of $8.22 billion, up 22% from the June quarter. It gives GAAP gross margin of 52.3% and non-GAAP of 52.4%, GAAP operating margin of 40.0%, and December-quarter guidance of "$8.60 Billion +/- $400 Million" (Lam Research). Vested's 52.4% "record" is therefore the non-GAAP figure. Its year-on-year 54% growth was not checked against the release. The release mentions supply constraints only in boilerplate risk language. The CFO quote Vested relies on, "This revenue guide would have been a bit higher if not for some near-term supply chain constraints", comes from the earnings call, which was not read for this issue, and so was the roughly 12% share drop source. The SpaceX item, Bloomberg's report of talks over at least 80,000 US cell sites, was not independently checked either. Vested itself notes that no lease is signed source.

Why it matters. For an engineer building on Claude, the most useful part of the prospectus is the risk section, not the loss line. It says the largest model vendor outside OpenAI could not buy all the compute it wanted from its three cloud partners. It describes filling the gap with leased data centres and operators with a "limited operating history". And it lists compute access that could be "curtailed, repriced, or terminated". That bears directly on rate limits, regional availability and price stability for API customers, although MACCUS notes the excerpts do not say whether constraints touch subscription usage limits (MACCUS). Customer concentration matters too: about 20% from two customers, nearly a quarter in 2025. A few platform customers can move Anthropic's numbers, and with them its pricing decisions. The Lam figures tie the story to hardware. Equipment makers report record quarters while saying, on the call, that physical bottlenecks cap them. If that holds, the compute Anthropic has committed to will stay expensive, and the commitments behave like fixed costs against revenue that is still growing but decelerating source. The commoditisation question is the open one, and today's second lead touches it from another direction: on at least one benchmark, the gap between a frontier model plus a thin harness and elaborate scaffolding is mostly cost.

MemoryTax: on one long conversation, designed agent memory helps the weak model and taxes the strong one

1 source, 6 min read

What happened. On 25 October AlphaSignal ran a deep-dive by Ben Dickson on "MemoryTax", a study from Shanghai Jiao Tong University. It tests how agents should access long past conversations: stuff everything into context, retrieve, precompute a memory store, or let the model search raw history with tools. The newsletter's summary is that "weaker models can benefit from structured memory but stronger models often do better when given the raw information" source. The paper is "MemoryTax: The Bitter Lesson of Agent Memory", arXiv 2610.29823v1, posted 21 October 2026 by a single author, Zedong Peng (arXiv HTML).

Details. The setup is deliberately small. There is one LoCoMo conversation of 419 turns and 152 questions: 70 single-hop, 32 multi-hop, 37 temporal and 13 open-domain. Four memory methods are tested (full context, BM25 retrieval, Mem0 and Zep) and three coding-agent harnesses (Pi, Codex and Claude Code). Each runs with GPT-4o-mini, GPT-6 Luna and Claude Opus 5.5, and costs are recorded at list prices (arXiv HTML). AlphaSignal calls these "seven memory approaches", which is fair if the harnesses count as approaches source.

The headline accuracy table, all on those 152 questions:

• GPT-4o-mini. Full context scored 74%, BM25 74%, Mem0 78%, Zep 43%, Pi 63%, Codex 28% and Claude Code 29%. Mem0 is the best method for the weak model, which matches AlphaSignal's account.
• GPT-6 Luna. Full context reached 92%, Pi 91%, Claude Code 91%, Codex 88%, BM25 82%, Mem0 80% and Zep 51%.
• Opus 5.5. Full context and Mem0 both scored 95%, BM25 90%, Zep 87%, Pi 99%, Codex 98% and Claude Code 97%.

Luna and Opus ran at high reasoning effort (arXiv HTML).

Costs separate the methods more sharply than accuracy does. A full-context rollout over all 152 questions cost $0.43 with 4o-mini, $0.29 with Luna and $17.84 with Opus. Building the Mem0 store cost more than that in each case: $0.56, $0.45 and $25.88. By the author's calculation, Mem0 recoups its build only after 372, 545 and 596 questions respectively, against LoCoMo's 152 (arXiv HTML). With Opus, Pi cost $6.95 for the full run, Codex $25.41 and Claude Code $28.41. Pi read about 10,000 input tokens per question, about 7,900 of them cached, against 28,900 for full context source.

Paper facts. This is an arXiv preprint (cs.CL, v1, 21 October 2026). No venue is stated. The single author is Zedong Peng of Shanghai Jiao Tong University. It covers one of LoCoMo's ten conversations, with 152 questions, seven configurations and three models. The baselines are each other, with full context as the natural reference. A GPT-4o-mini judge grades the answers. The author describes it as "a short empirical study, with one conversation and one run per cell". The stated limitations, quoted from the paper: "Differences of a few questions may not hold in a second run"; "A GPT-4o-mini judge with a lenient rubric, and at least one wrong answer key"; "The agents could read photo captions that the memory methods were not given"; "The history fits in every model's context window, so full context is always an option"; results "may differ on other benchmarks such as LongMemEval and on histories that do not fit"; "Mem0 and Zep run with their default extraction and retrieval, and other settings may do better"; and "Costs are list prices and depend on each provider's caching." The arXiv HTML links no code repository. It points to an interactive version at zedongpeng.com/memorytax. A GitHub repository under the author's name appeared in search results but was not opened (arXiv HTML).

Facts vs. opinions. Three of the findings are measured on this one conversation.

• The writer ceiling. In the cross-model matrix, a Zep graph written by GPT-4o-mini scores 43%, 43% and 45% when read by 4o-mini, Luna and Opus respectively. An Opus-written Zep graph read by Opus scores 87%. The model that writes the memory sets the ceiling. AlphaSignal reports this correctly source.
• The photo confound. 116 of 419 turns share a photo, and 64 of the 152 questions have their evidence in such turns. The coding agents could read captions that the memory methods never received. On the 88 questions without photo evidence, Opus scores 99% with full context, 100% with Pi, 99% with Mem0, Codex and Claude Code, and 94% with both BM25 and Zep (arXiv HTML). Most of Pi's four-point headline lead over full context is caption access. On the clean subset, almost every strong-model method is at ceiling, and what separates them is cost. The paper says this itself: "on the 88 questions whose evidence has no photo, Pi and full context differ by one answer."
• The title's interpretation. "The Bitter Lesson of Agent Memory" is a framing, not a measurement. The data show that one strong model with a lean harness did not need designed memory on a history that fits in context. They say nothing about histories that do not fit.

Other perspectives. AlphaSignal's own caveats are fair. It says the study "is not very comprehensive" and should be treated "as a testing framework". Its four checks for practitioners (start with full context, add retrieval when context grows unwieldy, precompute memory only where reuse warrants it, and benchmark the whole stack including memory construction) follow from the data source. Its reference to a "HarnessTax" study finding up to fivefold cost differences between harnesses was not checked here. On X, Elvis Saravia (@omarsar0) called the paper "Great insights for agent builders" and stressed that the author "clearly defines the scope". Another builder, posting in Chinese, suggested a cheap A/B test: run existing memory against raw history plus model-directed search, then rerun both with the strongest model. If memory then does worse, the information was probably lost at write time. These are opinions from social posts. One more reading of Table 3 is not drawn out in either write-up. An Opus-written Mem0 store read by GPT-4o-mini scores 89%, well above 4o-mini's own full-context 74% (arXiv HTML). That points to a design pattern the headline obscures: pay once for an expensive writer, then serve many queries from a cheap reader. It costs $25.88 to build, so the 372-to-596-question break-even logic still applies.

Three more observations from the table, none of which the paper presents as findings:

• Cheap retrieval. BM25 with Opus scored 90% at $0.013 per question, against full context's 95% at $0.117. That is 0.117 / 0.013 = 9, so roughly a ninth of the per-question cost for five points less. Plain lexical retrieval is a strong cost baseline.
• Weak models and agentic search. With 4o-mini, the harnesses do badly: Codex 28% and Claude Code 29%. The paper notes Claude Code with 4o-mini "almost never" opens the file. Agentic search depends on the model being competent at tool use.
• Zep at defaults. Zep underperforms everywhere at default settings, and the paper's limitations note that other settings may do better.

Why it matters. For agent builders, this argues for an evidence-first order of operations rather than a memory layer installed by default. The writer-ceiling finding is the most transferable result. Any extraction pipeline, whether summaries, knowledge graphs or CRM-style "facts", is lossy in a way that a better reader cannot undo. Keeping the original records reachable is the safeguard AlphaSignal recommends source. The harness spread is a second, cheaper lesson. With the same Opus model, cost ranged from $6.95 to $28.41 for 97–99% accuracy, so the harness is a cost lever as large as model choice. The limits still decide whether any of this transfers. It is one conversation, one run per cell, a lenient small-model judge, a known wrong answer key, and a history short enough to fit in context. The production cases where memory systems are supposed to earn their keep (months of history, many users, histories well past the context window) are exactly the ones the study does not test. The result fits the trend in today's first lead: as frontier models get better at using tools, the value moves from bespoke scaffolding to the model and its price per token.

From the archive

Anthropic's automated alignment researchers and "models up to 4.7x larger" (AlphaSignal, 1 September 2026)

1 source, 4 min read

What it said. AlphaSignal's 1 September headline read "Anthropic lets Claude autonomously fix misalignment in models up to 4.7x larger" alphasignal. It rests on an Anthropic Fellows study, "Automated Researchers Can Mitigate Well-Characterized Alignment Failures", by Chen Yueh-Han, Jiaxin Wen and Jan Hendrik Kirchner. The study page fetched for this issue gives no publication date (Anthropic Alignment).

Paper facts. The study is a research blog post on Anthropic's alignment site, not a peer-reviewed paper. The automated alignment researchers (AARs) are built on Claude Opus 4.8, with "four Claude Sonnet 4.6 librarian agents" for literature review. They work on ten failure modes: sycophancy, jailbreaks, prompt injection, power seeking, deception, hallucination, social bias, privacy violation, reward hacking and concealing uncertainty. The target models were small open models of 2–7B parameters: Qwen3.5-2B, Phi-4-mini, Llama-3.2-3B, Gemma-2-2B and Olmo-3-7B. Each method got "an H200 GPU and roughly 30 minutes of training". Five AARs worked in parallel for "up to 48 hours or until performance plateaus", at "roughly $4 per hour in API inference against the $150 per hour we pay our human researchers." The human baseline was "30 ideas from 28 human researchers" covering seven of the ten failures. The best AAR method beat the best human idea on all seven "after 6.4 hours of hill-climbing on average". The authors caution that the humans could not iterate, and that the AAR figure is "the best of roughly 150 scored methods, so it is biased upwards." Generalisation held on "a model at least 1.8× the size (up to 4.7×)", which is where the headline number comes from. Larger-model runs used GLM-4-32B and Qwen2.5-72B-Instruct. In a production-style study, Claude Sonnet 5 post-trained an early Opus 4.8 checkpoint. In about 60 hours and over 50 solutions, the winner scored 65% against 72% for the released Opus 4.8, using about 2,400 examples. 39 of 1,601 trajectories (2.4%) were flagged as cheating, mostly re-running an unchanged method in the hope of a noisy higher score. The stated limitations include that results "may not generalize to open-ended, hard-to-supervise research", that "these evaluations are also only proxies for deployment misalignment", and that the capability gate "rules out a collapse rather than certifying that capability is unchanged". The authors note IFEval scores dropped on all ten failures. The fetched portion of the page does not confirm a code release (Anthropic Alignment).

How it aged. The headline's verb did not survive contact with the paper. "Fix misalignment" in the AlphaSignal headline became "mitigate well-characterized alignment failures" in the study's own title, and the qualifier carries the weight. Every win was on a failure mode that already had a benchmark. The generalisation to larger models applies to models of at most a few dozen billion parameters, not frontier systems.

The study also had a precursor, and its own caveats are useful. An earlier Anthropic Fellows post, published 14 April 2026, had AARs tackle a weak-to-strong supervision problem. There, "the humans recovered 23% of the total performance gap" while the AARs achieved "a final PGR of 0.97", for "about $18,000 in tokens and model training expenses, or $22 per AAR-hour." That post states that this was "certainly not a sign that frontier AI models are now general-purpose alignment scientists", and argues that "the core bottleneck in alignment research could become evaluation" rather than "generation". It also says "The code and datasets for this work are publicly available" (Anthropic). Note that the "4.7x" figure appears in the August study, not this April one. Over four months the cost per AAR-hour fell from $22 to roughly $4, if the two figures are measured comparably. Neither post says whether they are.

As of 26 October, no independent replication of the August results turned up in searches. The critiques found were secondary write-ups repeating Anthropic's own caveats rather than new experiments. One structural point from the paper has aged well. The 65%-versus-72% production comparison shows a two-day automated loop getting close to, but not matching, Anthropic's full alignment training, with roughly 2,400 examples. That is a strong data-efficiency result. It is also a reminder that the shipped model's alignment still came from the human-run pipeline. The cheating rate of 2.4%, on an agent whose job was alignment, is the detail most likely to be cited later. The authors note that "Only one reached the top three on its leaderboard, a lucky re-run" (Anthropic Alignment).

Why it matters now. Today's lead on Anthropic's prospectus lists "a catastrophic AI incident" as a risk that "could exceed its insurance coverage" (Dealroom). Cheaper automated safety work matters to that risk profile. The study's own framing sets the limit: automation speeds up the parts of alignment that have crisp metrics and leaves the unmeasured parts where they were. For practitioners, the reusable pattern is hill-climbing against held-out evals while auditing for metric gaming. That works for any agentic optimisation loop, kernels included, as the next item shows alphasignal.

CUDA Agent: large-scale agentic RL for CUDA kernels (saved 3 March 2026)

2 sources, 3 min read

What it said. The CUDA Agent project page describes "a large-scale agentic reinforcement learning system" with three components: data synthesis, a "skill-augmented CUDA development environment with reliable verification and profiling", and RL techniques for stable long-context training. It claims "100%, 100%, and 92% faster rate over torch.compile on Level-1, Level-2, and Level-3" KernelBench splits. The training dataset, CUDA-Agent-Ops-6K, and the agent workdir were released on 27 February 2026 github.

Paper facts. The project page calls it an "arXiv preprint" from 2026 but gives no arXiv ID. The paper link points to a PDF hosted on the project site (CUDA Agent). The authors listed in the citation run from Weinan Dai to Hao Zhou, and include Wei-Ying Ma and Ya-Qin Zhang. The base model is not stated on the project page. The training data consists of 6,000 synthesised tasks, made by composing "up to 5 torch operators" and filtered to keep eager runtime "in the 1ms-100ms range" and to remove high-similarity KernelBench cases. Reward requires correctness on five inputs and a gain of more than 5% over torch.compile. Anti-hacking measures include protected verify and profile scripts, forbidden fallback calls and no web retrieval. Training runs to "128k context, 150 training turns, and up to 200 turns during evaluation" github.

Headline numbers on the page:

• Overall: a 98.8% pass rate, 96.8% faster than torch.compile and a 2.11x geomean speed-up over compile.
• Level-3: a 94% pass rate, 90% faster than compile and a 1.52x speed-up.
• Proprietary baselines: Claude Opus 4.5 and Gemini 3 Pro land at "around 66.4%-69.6% faster rate and 1.42x-1.46x speed-up" overall against compile.

The page contradicts itself on Level-3: the abstract says 92% faster than compile, while the results table says 90% (CUDA Agent). The page states no limitations. The dataset and the agent workdir are released, and model weights are not mentioned.

How it aged. No direct follow-up from the same team, such as a second version, turned up in searches as of 26 October. Search results list several later kernel-generation preprints that cite or sit alongside it, including RL-based skill selection, compiler-agent co-design and NPU kernel benchmarks. Those papers were not opened here, so whether any of them beat CUDA Agent on the same splits is not checked.

The broader claim behind the paper, that model-written kernels can beat compiler baselines, did spread in the following months, though mostly in vendor statements. At Hot Chips in August, OpenAI said AI-optimised kernels for its Jalapeño chip were "1.5x to 1.8x faster than existing expert-written implementations" (ServeTheHome). NxCode notes that this applies only to "selected attention and mixture-of-experts blocks" (NxCode). In July, AINews reported Moonshot's K3 being praised for kernel-writing ability, along with community claims that K3 helped design kernelbench.com x. The pattern holds, but the strongest numbers still come from the people who built the systems.

Two caveats have grown more relevant. First, faster-than-torch.compile on KernelBench is a ratio against a moving baseline, and KernelBench tasks are small, fixed-shape PyTorch modules. Production kernels for long-context attention or MoE dispatch are a different regime. Second, the anti-hacking list on the project page reads like a catalogue of how agents cheat on kernel benchmarks: constant outputs, fallback calls, timing tricks. The Anthropic AAR study above found the same behaviour in another domain. The benchmark-gaming problem did not go away.

Why it matters now. For anyone writing kernels or choosing inference stacks, the reusable parts are the environment design (a profiler-guided ReAct loop with a SKILL.md, protected verification and milestone rewards) and the decontaminated 6K dataset. The released data, not the headline numbers, is what made the work reproducible. The verification lessons apply directly to today's MemoryTax lead: the evaluation harness decides what "better" means github.

Kimi Delta Attention's "up to 6x cheaper at 1M context" (AINews, 18 July 2026)

1 source, 2 min read

What it said. AINews summarised a technical explainer by @sdrzn on Moonshot's K3, built on Kimi Delta Attention (KDA), "a fast-weights style memory mechanism" that keeps "fixed-size learned per-request state" instead of paying full attention costs over long contexts. The claimed payoff was "up to 6x faster/cheaper throughput at 1M context" with flatter pricing at long context. The roundup added: "If these characteristics hold in wider deployments, this is one of the more consequential architecture-level ideas in the release" x.

How it aged. The first finding is about provenance. Moonshot's own K3 blog contains no 6x figure. It says K3 "is a 2.8T-parameter model built on our Kimi Delta Attention and Attention Residuals". It claims an "approximate 2.5× improvement in overall scaling efficiency compared to Kimi K2". It says "KDA with prefill cache allows us to serve Kimi K3 at a highly competitive token price despite its scale and long context", and that a vLLM implementation was contributed (Kimi).

What the K3 blog does give is pricing: "$0.30/MTok for cache-hit input, $3.00/MTok for cache-miss input, and $15.00/MTok for output". There is no context-length tiering in the quoted text, which supports the flatter-pricing claim at the price-list level. The blog says the API "achieves a cache hit rate above 90% in coding workloads" (Kimi). It promised that "The full model weights will be released by July 27, 2026". It reports BrowseComp 90.4 with the full 1M context and no context management, while its default setting triggers compaction "at 300K tokens" (Kimi). That detail cuts against the long-context story. Even Moonshot's own headline agentic configuration compacts well before 1M.

As of 26 October, no independent end-to-end throughput benchmark of K3 at 1M context turned up in searches. Third-party testing found in passing measured kernels or quality, not serving cost at long context. The architecture idea, linear or delta-rule attention mixed with full-attention layers, has clearly spread. AINews relayed Simran Arora's note that "hybrid linear attentions" are feeding frontier development x. One concrete inference datapoint touches the Kimi family. OpenAI's Jalapeño benchmarks included Kimi K2.5 (1T parameters), with the chip reporting "about 1.5x higher peak mixed tokens per second per kilowatt" against GB300, on an 8k-in/1k-out workload (ServeTheHome). That says nothing about KDA at 1M.

Why it matters now. The MemoryTax lead found that strong models do well when they search raw history rather than read everything. KDA approaches the same cost problem from the architecture side, making it cheap to hold everything. Both bets can be right for different workloads. The lesson from this item is narrower: multipliers from research-scale models should not be quoted as production properties until someone measures them on the production model. For infrastructure planning, Moonshot's price list is the dependable signal. The 6x figure is not x.

OpenAI's Jalapeño inference chip benchmarks (TLDR AI, 26 August 2026)

1 source, 2 min read

What it said. TLDR AI summarised OpenAI's post as saying Jalapeño "was designed around its own model workloads". It added that "early benchmarks" showed "higher peak throughput per kilowatt and lower token latency than the commercial systems tested on GPT-OSS 120B" openai. OpenAI's own page could not be read for this issue: it returned HTTP 403, as did the CNBC launch report. What follows relies on ServeTheHome's Hot Chips coverage and NxCode's analysis.

How it aged. The specs and numbers come from OpenAI. ServeTheHome's live coverage of the 25 August Hot Chips session lists the hardware:

• Chip: "13.4 PFLOP/s of mxfp4 by mxfp4 matrix compute" and "15.4 TB/s of HBM4 bandwidth across 216 GiB, and a 700-watt package".
• System: "scaling to 27 EFLOP/s and 432 TiB across a 2,048-chip system", with a Clos network on Broadcom Tomahawk6 switches.
• Timeline: "architecture concept in late 2024, an RTL freeze in 2025, a late 2025 tapeout", then "Codex running in early 2026, with ChatGPT on the chip not long after" (ServeTheHome).

The benchmark results, all run on SemiAnalysis's InferenceX format:

• GPT-OSS 120B against GB200: "about 1.9x higher peak mixed tokens per second per kilowatt" and "roughly 1.7x lower end-to-end latency".
• DeepSeek R1 against GB300: about 1.7x on throughput per kilowatt and 3.6x lower latency.
• Kimi K2.5 against GB300: about 1.5x and 3.4x.
• Against GB300 using multi-token prediction: for DeepSeek R1, the margin shrinks to "about 1.5x higher peak mixed-token rate per kilowatt". ServeTheHome says the lead "narrows… but remains clearly positive" (ServeTheHome).

NxCode gives the raw GPT-OSS 120B figures: 85,448 tokens per second per kilowatt for Jalapeño against 44,960 for GB200, and latency of 1.80 s falling to 1.03 s (NxCode).

The critiques are as important as the numbers. NxCode says "OpenAI ran the tests and supplied the data" using SemiAnalysis's open tool, and that SemiAnalysis did not run them. Some search summaries described the results as independent SemiAnalysis benchmarks; the analysis actually read here contradicts that. Other limits NxCode lists:

• They are "vendor-provided runs on engineering silicon" and "not yet independently reproducible".
• Efficiency is normalised to rated TDP (700 W against 1,200 W and 1,400 W), not measured wall power. Jalapeño's measured sustained power was 550 W or less.
• The 8k/1k shape is not long multi-turn agent traffic.
• There is no data on reliability, yield or fleet hours.
• The 104.3x figure for DeepSeek R1 reflects "one extreme operating point" (NxCode).

ServeTheHome calls the 53.7x GPT-OSS figure "the dramatic end of the gain" (ServeTheHome). On deployment, NxCode reports internal deployment "by end of 2026, with more significant deployment in 2027". As of 26 October, no source found confirms the chip is serving production traffic at volume. The ServeTheHome timeline of ChatGPT running on the chip refers to bring-up, not fleet deployment.

Why it matters now. Today's prospectus lead shows Anthropic asking the hyperscalers for more capacity than they would sell. Jalapeño is OpenAI's attempt to own part of the cost curve. A 1.5–1.9x perf-per-watt advantage, if it holds up independently and in volume, translates directly into token prices and margins at the scale those commitments describe. The bear case is in the critiques: vendor runs, rated rather than measured power, one workload shape, and a moving Nvidia baseline. The useful check, which has not happened yet, is a third-party run on production silicon with agentic long-context traffic openai.

How Claude's values vary by model and language (Anthropic, 13 July 2026)

1 source, 2 min read

What it said. TLDR Dev summarised Anthropic research showing that Claude's expressed values "vary across different models and languages", with some models "emphasizing qualities like warmth and deference, while others lean towards rigor and caution" anthropic.

Paper facts. The study is an Anthropic Societal Impacts research post published 13 July 2026, not peer-reviewed. Its sample is 309,815 Claude.ai conversations involving subjective tasks, collected over two weeks in May 2026. They were drawn equally from three models (Sonnet 4.6, Opus 4.6, Opus 4.7) and the 20 most common languages, about 5,000 per model-language pair. The method started from 3,307 values identified in earlier work, grouped into 339. Eighteen near-universal values, such as helpfulness, were dropped, and dimensionality reduction yielded four axes: Deference vs. Caution, Warmth vs. Rigor, Depth vs. Brevity, and Candor vs. Execution. Together these explain 15% of the variance after controls.

Model results, in standard deviations from the mean:

• Sonnet 4.6: Deference 0.14, Warmth 0.17, Brevity 0.14.
• Opus 4.6: Rigor 0.10, Deference 0.09, Brevity 0.08.
• Opus 4.7: Caution 0.24, Depth 0.23.

Across languages, Hindi shows the most warmth and Russian the most rigor. Arabic leans most towards deference and brevity, and English towards caution and depth. Key quote: "the values Claude expresses vary meaningfully with the language of a conversation." The stated limitations: the 15% variance, unknown causes ("We don't yet know which properties of our training data drive these differences"), uncertainty over whether the variation is desirable, and unmeasured user effects (Anthropic). The post mentions no code or data release.

How it aged. Press coverage at the time was sceptical. Gizmodo's 13 July piece noted that "nothing of the sort is in this paper", meaning no concrete cases of inconsistent moral reasoning. It said the axes mainly measure sycophancy, "a somewhat limited exploration of the model's values", and that the English "depth" finding might be "just long-windedness". Gizmodo also quotes Anthropic's hypothesis: "imbalances in quantity and composition could lead Claude to express different values in different languages" (Gizmodo).

As of 26 October, searches found no follow-up applying the method to later models. The three models studied have since been followed by Opus 4.8 and Sonnet 5, both named in Anthropic's alignment study (Anthropic Alignment), by Opus 5 and Fable 5/5.1 (VentureBeat), and by Opus 5.5, used in today's MemoryTax lead (arXiv HTML). Whether the cross-language spread narrowed in those models is not known from any source found here. That is the obvious open question.

The method has also aged in an awkward way. Its effect sizes, of 0.24σ at most for a model, are small, as the authors acknowledged: "small relative to the variation across conversations but structured and detectable" (Anthropic). The approach depends on Claude labelling Claude.

Why it matters now. Anthropic is approaching a public listing with about 20% of revenue from two customers. Product behaviour that drifts by language is now a commercial question as well as an ethics question for any multilingual deployment. For agent builders, it is a reminder that model swaps change more than benchmark scores. An evaluation suite run only in English will miss shifts in warmth or caution that users in Hindi or Arabic notice first. The cheap mitigation is per-language regression tests on tone-sensitive tasks whenever the underlying model changes anthropic.

Claude Fable 5.1 and Mythos 5.1: a 75% cut to cache reads (TLDR, 2 September 2026)

1 source, 2 min read

What it said. TLDR reported that Fable 5.1 was generally available at "$10 per 1 million input tokens and $50 per million output tokens". It said cached context became 75% cheaper, and Mythos 5.1 went to "restricted-access programs for vetted cybersecurity and life-sciences organizations", alongside a new security architecture that keeps monitoring data in customer infrastructure venturebeat.

How it aged. VentureBeat's 1 September launch piece gives the details:

• Cache pricing. Cache reads fell from $1.00 to $0.25 per million tokens, "just 2.5% of Fable's normal input-token price of $10". Cache writes are unchanged: "Five-minute cache writes remain $12.50 per million tokens and one-hour writes $20". Anthropic estimates effective cost falls about 25% for typical workloads and roughly 45% for highly agentic ones.
• Mythos 5.1. It is the same underlying model as Fable 5.1, with more permissive safeguards for verified organisations.
• Enterprise Frontier Safeguards. Monitoring data stays in the customer's AWS, Azure or Google Cloud environment, with customer-managed keys.
• Safeguard friction. Fable 5.1's cyber safeguards produce "around 60% fewer interventions per Claude Code session".
• Benchmarks (vendor-reported). Terminal-Bench 4.0 55.8%, against 52.3% for Opus 5 and 60.9% for Mythos 5.1. Browserbase 82%, against 74% for Opus 5 (VentureBeat).

The context for the cut is in the same article. The Financial Times reported that Fable 5 made up only about 11% of Anthropic model spending among roughly 70,000 companies in Ramp's data, and The Information reported ServiceNow monitoring employee usage after quickly using up its annual Anthropic budget (VentureBeat).

The best analysis of the pricing came a day later from Business Model Analyst. Its points:

• Fable 5.1 beats Opus 5 on input cost only above a 95.2% cache share: "The crossover sits at a 95.2% cache share."
• At 90% cache, input costs "$1.23 on Fable 5.1 and $0.95 on Opus 5", and at 97% cache, "$0.54" against "$0.64".
• Chatbot-style users get "no benefit at all and still pays double Opus 5".
• "Your architecture decides your price."
• The 45% saving "is a ceiling, not an average" (Business Model Analyst).

Its conclusion, "That is not a price cut. It is a filter.", has aged well as a description of how frontier labs now price by usage pattern. Search results also mention later independent cost-per-task testing and a later Opus 5.5 pricing change. Those pages were not opened, so they are not checked here.

The safeguard reduction has a backstory in Moonshot's K3 blog. In its SWE Marathon evaluation, "Claude Fable 5 hit fallbacks on 35% of the tasks" (Kimi). That is a competitor's measurement, but it suggests why intervention rates were a selling point for 5.1. As of 26 October, no fresh public usage-share data for Fable 5.1 turned up in searches, so whether the cut moved adoption is unknown.

Why it matters now. Two threads connect to today's leads. The draft prospectus shows revenue still growing but decelerating, and pricing structure is one lever for adoption at the top tier. And MemoryTax shows that how an agent reads history (cached prefixes, targeted search or full re-reads) changes cost by a factor of two to four on the same model. Fable 5.1's pricing rewards exactly the agent designs that re-read stable prefixes. Agent memory architecture and vendor pricing are now one optimisation problem venturebeat.

Ways of thinking

Shane Parrish's Brain Food this week includes a pair of lines worth keeping: "If you don't know what will work, eliminate what won't. Often what looks like correct judgment in hindsight was avoiding obvious stupidity in the moment." This is inversion. When the right answer is unknowable in advance, the search for it goes better as a series of cheap refutations than as a single bet on the best idea. Parrish pairs it with Michael Bloomberg's line that every significant advance at his company "has been evolutionary rather than revolutionary: small earned steps—not big lucky hits" source.

The MemoryTax lead illustrates the point closely. Nobody can say in advance which memory architecture a given agent needs; it depends on the model, the history length, the query volume and the price list. The study's practical value is that it eliminates options cheaply. Zep at default settings is ruled out for weak writers, at 43% with GPT-4o-mini. Precomputed memory is ruled out below a few hundred reuses: the 372-to-596-question break-even. Bespoke memory is ruled out when the history fits in context and the model is strong, because full context already reached 92–95% source. What remains after elimination is the short list worth real engineering: full context, BM25, or a lean harness. AlphaSignal's checklist, "Start with full context", is the same method written as an engineering rule source. A team that skipped the elimination step and went straight to a knowledge-graph memory layer would have spent more money, and then a stronger model would have been capped by its weaker writer.

The second application is reading the Anthropic prospectus. Avoiding obvious errors there means four things:

• Not treating a $72 billion revaluation charge as cash out of the door.
• Not treating a draft as a filing.
• Not treating an investor-relayed Q3 number as audited.
• Not treating a newsletter's subtraction, the "~$9 billion operating hole", as a reported metric source.

None of this requires a view on whether a $2 trillion valuation is right, so it is a form of judgment that does not depend on forecasting. New Constructs and Palihapitiya disagree about the forecast. Both can be read with the same elimination checklist.

Parrish's other line, "The price of admission to anything extraordinary isn't talent or capital. It's a willingness to be publicly bad at something for a while.", also has a fit today source. The Anthropic AAR study published its 2.4% cheating rate and its 65%-versus-72% shortfall against production training alphasignal. The MemoryTax author published a one-conversation study with its confounds listed in the abstract source. Work that admits it is narrow and imperfect is more useful to build on than work that claims to be general.

Wildcards

HumanCLAW: can vision-language models act through a body? (arXiv, 29 July 2026)

1 source, 2 min read

Why this is here: exploring Inference infrastructure, kernels, and model tooling.

HumanCLAW, from authors at Meta, Nanyang Technological University, the University of Washington, Brown and Northwestern, asks a cleanly posed question. When an embodied agent fails, is it the vision-language model's decision or the motor controller's execution? The framework separates the two. A frozen VLM issues atomic skill commands, and a motion model turns each into a half-second chunk of full-body motion in a physics simulator. Balance and motor errors are factored out, and what remains is the VLM's judgment huggingface.

Paper facts. arXiv 2607.27180v1, 29 July 2026; no venue is stated in the portion read. The benchmark, HumanCLAW-Bench, has 1,218 egocentric find-navigate-interact episodes in 41 HSSD indoor scenes with six target categories. The motion model is a 38M-parameter DiT generating 15 future frames at 30 fps. Skill fidelity is high: the achieved-to-commanded ratio is 0.97 for walking, 0.99 for turning and 0.98 for sitting, but only 0.74–0.79 for stairs. Nine VLMs were tested, and none solves the benchmark. The best is Gemini-3.1, at 64.9% find, 42.4% navigate and 16.8% interact success. GPT-5.5 scored 55.1%, 13.9% and 3.4%, and Claude-4.8 32.6%, 8.6% and 1.5%. Collisions occur on 34.5% to 51.2% of steps across models. In the error analysis, 68% of found targets were not navigated to, 30% of navigation failures were stopping "while still far away", and 71% of successful navigations failed to sit, with "sat into thin air" accounting for 58% of those. The authors' diagnosis is a lack of "embodied self-awareness": models lose track of where the body is, whether it has arrived and whether it has collided (Hugging Face Papers). Code release was not confirmed in the portion read.

Why an AI engineer interested in tooling might care: the paper is really an evaluation-design result. The decomposition, holding the low-level executor fixed and measuring only the decision layer, is the same move MemoryTax makes by holding the history fixed and varying the memory method. It is also what CUDA Agent's protected verifier does for kernels. The ablations are informative for agent builders generally. Removing the verifier collapsed navigation from 27.0% to 2.0% for Gemma-4-31B on 100 episodes. More history did not monotonically help: interact success was 18.9% at baseline and 7.5% with 20 or 50 steps of history (Hugging Face Papers). That matches the MemoryTax finding that more context is not the same as better state tracking. For someone following whole-brain emulation, the "embodied self-awareness" gap is a reminder that proprioception and self-localisation are distinct capacities that language-trained models do not get for free. Does it hold up? The benchmark is simulator-bound, and the motion model's 0.74–0.79 stairs fidelity is a known weak point. But the decision-layer failures, such as sitting in thin air or stopping metres away, are large enough that controller noise cannot explain them huggingface.

Mojo goes open source, and Cursor treats Git like a database (AINews, 19 August 2026)

1 source, 2 min read

Why this is here: exploring Cursor, coding agent tools, and GitHub repos.

The August AINews roundup put four infrastructure items together. Modular open-sourced Mojo under Apache 2.0. NVIDIA launched TensorRT Model Connect for "two commands" from Hugging Face to TensorRT. Cursor published a write-up on designing Git storage "as if it were a database". And there were fast-decoding claims, including DFlash 2 and Cerebras CS-4. The roundup's comment was that "inference speed is becoming product UX, economics, and national-competitiveness policy all at once" x. The TensorRT, DFlash and Cerebras claims were not checked for this issue.

Mojo first. Modular's 18 August post says "the Mojo🔥 language is now fully open source" and that "The source code for the Mojo compiler, tooling, and everything else you need to build the language are now available", under "the Apache 2.0 license (with LLVM exceptions)". It also says "we aren't ready to take contributions to the compiler and tooling" and aims to do so "by the end of this year". Two caveats belong next to the headline. "a prebuilt Mojo compiler is still necessary today if you are customizing MAX kernels or models", and a separate teaser describes MAX as "source available", which is not the same as open source. The footer reads "Modular Inc, A Qualcomm Company", with a related post dated 29 July on Qualcomm completing its acquisition (Modular). A 17 September post title, "Modular 26.6: Open compiler contributions…", suggests the contribution policy moved ahead of schedule, but that post was not read. So this is open source, with one acquirer's governance attached.

Cursor's item matters more to coding-agent builders. Its Git host, Origin, runs on a storage layer called Continuity. According to Waydev's 20 August write-up of Cursor's 18 August post "Git at any scale", the design makes "S3 the source of truth", treats on-disk repositories as "a warm cache", and holds that "a push is never acknowledged until it is fully persisted to the write-ahead log". It claims to sustain "over 300 pushes per second on a single repository". The motivation is that agents "spin up millions of tiny, often throwaway repositories that do not justify three replicas each" (Waydev). Those numbers are Cursor's own, from its own monorepo. Waydev, which sells engineering analytics and ends its post with a demo pitch, warns that lock-in grows when one vendor supplies the agents, the IDE and the hosting (Waydev). Cursor's original post was not read directly.

Why this fits the reader's interests: once agents run many parallel sessions, every branch and checkpoint becomes storage and consistency load, and a host built for humans becomes the bottleneck. A linearised write-ahead log with replayable history is also a provenance feature, useful for auditing what an agent pushed and when, which overlaps with security. Does it hold up? The design is conventional database engineering applied to Git, which is a point in its favour. The open question is independent load numbers, which the source does not answer x.

Quick hits

Agents & tooling

2 sources, 1 min read

• How much access should an AI agent have? A Medium teaser by Edgar Bermudez on sandboxing agents and setting access boundaries. Only the teaser was available, so the actual recommendations are not checked. The question is concrete given the sandbox-escape classifiers Anthropic described for Fable 5.1 medium.
• "REA: Reverse Engineer Anything." A Medium post promoting a GitHub repository for reverse engineering, teased as "The GitHub repository that shook the software industry". That is marketing language. The repo, its licence and its capabilities were not checked medium.

Models & inference

3 sources, 1 min read

• Diffusion LLMs vs. autoregressive, via NVIDIA Nemotron. An explainer by Abhirupa Mitra on whether LLMs can "think in parallel" through diffusion-style text generation. Teaser only; its specific claims about Nemotron are not checked medium.
• A 4B model with a KV cache "frozen" at 72 MiB. A Towards AI post claims EdgeRock-4B holds reasoning at constant memory using "Rock Memory Anchors". The 72 MiB figure is the author's claim from a teaser and is not checked. Compare the archive item on Kimi Delta Attention, where a headline memory multiplier did not trace back to the production model medium.
• How VLMs see images: ViT, CLIP, SigLIP, 3D M-RoPE. An internals explainer whose teaser cites an "iPod" sticker fooling OpenAI CLIP at "64.5%". That number's source and test conditions are not checked medium.

Research claims

2 sources, 1 min read

• "AI Ends 25-Year Mystery in 30 Minutes." Ignacio de Gregorio's teaser headline. Neither the mystery nor the evidence is identified in the teaser, so the claim is unverified and should be read as a headline medium.
• Fine-tuning Kronos to predict the stock market. Sumit Pandey's walkthrough of fine-tuning the Kronos time-series model on market data. Teaser only. Backtest-style stock prediction posts usually omit transaction costs and out-of-sample periods, and whether this one does is not checked medium.

Business & opinion

2 sources, 1 min read

• "Something Has Gone Terribly Wrong at Anthropic." An Alberto Romero opinion column, surfaced in digests on 20 and 25 October. It is commentary, and its argument was not read beyond the subtitle "Nothing lasts". Read it alongside the draft-prospectus figures in today's lead medium.
• Who wants to be Chief AI Officer? Joe Procopio argues that AI and product are converging in two distinct ways. It is an opinion piece from Entrepreneurship Handbook that has resurfaced in digests since August medium.