Anthropic's IPO filing says its own "self-improving AI" threshold may be close; also: a $104B nine-month loss, GPT-6 Astra editing model weights, OpenAI's Pando Git backend and Claude message threads

Lead stories

Anthropic's amended S-1 says it "may imminently" meet its own RSI threshold

4 sources, 4 min read

What happened. On Monday, 2 November 2026, Anthropic filed a revised registration statement (S-1/A) with the SEC. Among the new risk factors is language saying the company may soon meet the Responsible Scaling Policy (RSP) definition that covers AI accelerating AI development. TechCrunch's Julie Bort reported it as fine print sitting under the headline financials. Gizmodo's Mike Pearl (syndicated on AOL) compared it with the 26 October version of the filing and reports that the "imminently" wording is new in this amendment (TechCrunch; Gizmodo via AOL) techcrunch.

Details. The key sentence, as quoted by TechCrunch, is that "our internal estimates and our expectations regarding future models, rather than our current models," indicate "we may imminently meet our Responsible Scaling Policy's definition" of "dramatically accelerated progress attributable to AI." The filing pairs this with an explicit denial: "We have not designated any of our current models as exceeding this threshold." The same passage adds that Anthropic continues to assess the underlying data. The filing calls this an area of the RSP that "sets out our plans to monitor and mitigate the risks as we approach what has been termed 'recursive self-improvement.'" It warns that "Using AI to help build more capable AI could also pose a considerable safety risk". It also warns that AI-assisted R&D could make "the capabilities of our models to advance more rapidly than our ability to develop, validate, and implement" matching safety measures (TechCrunch) techcrunch.

The most important sentence for anyone reading this as evidence is an admission about detection. Anthropic writes that "we have in the past not identified" such an acceleration, and "may in the future not identify, a significant acceleration in our rate of development until after it has occurred." So the company is telling investors that its measurement of the very quantity at issue lags reality. The filing also says Anthropic does not expect to "safely use Claude to fully autonomously design and build successive generations of frontier models" "without meaningful human supervision or understanding," and that "we are considering updates to our Responsible Scaling Policy to keep humans in control of frontier model development." Nothing in the reported text mentions pausing development (TechCrunch) techcrunch.

How hard is the threshold to meet? Gizmodo gives the RSP's operational definition as a goal to "double the baseline rate of improvement, with that doubling plausibly attributable to AI." The piece also describes the mitigations the RSP envisages. Anthropic would "explore ambitious and possibly unconventional ways to achieve unprecedented levels of security," and Gizmodo summarises the aim as "eyes on everything" over its internal activities (Gizmodo via AOL). The RSP text itself was not fetched for this issue, so that wording is Gizmodo's account of the policy, not checked against it. Neither article says what "baseline rate" means in practice: which metric, over what window, measured how. That gap matters, because it decides whether "imminently" is a measurement or a forecast techcrunch.

Facts vs. opinions. The facts: the language is in a securities filing, it was added between the 26 October and 2 November versions according to Gizmodo, and it rests on internal estimates about future models, not on any current model crossing the line. The rest is interpretation. Calling it "self-building AI", as the TechCrunch headline does, goes further than the filing, which talks about accelerated progress attributable to AI, not autonomous self-construction. The filing itself rules out fully autonomous generation-to-generation development without human supervision. No named outside AI-safety researcher, regulator or analyst is quoted in the coverage read for this issue techcrunch.

Other perspectives. TechCrunch points to sceptics, via an X post it links, who argue that an S-1 is a marketing document as much as a disclosure, so saying you are near self-building AI doubles as a sales pitch. Bort's own view in the same piece is that Claude's coding, math and cybersecurity skills have grown sharply, so the warning may deserve to be believed and perhaps acted on with governance. Gizmodo is sardonic. It asks whether Anthropic is disclosing to risk-averse investors or announcing to a world eager to greet its "mechanical god", and says the company had better get moving on its ambitious mitigations (TechCrunch; Gizmodo via AOL). A third reading, which neither article makes, is legal. Securities law punishes risks that are known but not disclosed far more than risks disclosed too early. Lawyers drafting a prospectus have every reason to write "may imminently" if internal forecasts point that way, whatever the marketing team thinks. That reading is an inference, not something the sources state techcrunch.

Two items in today's bundle bear on the substance. The "Sparks of Weight-Space Programming" post (next story) is a concrete case of a frontier model doing hands-on ML work on another model. A Hugging Face paper titled R²Orch, on recursive self-improvement for agent orchestration via self-play, drew 89 upvotes on the same day (quick hits). Neither shows a doubling of any lab's rate of progress. Both show that "AI doing AI research" is now concrete research activity, not just a slogan seangoedecke +1.

Why it matters. For the reader's recursive self-improvement interest, this is a frontier lab putting a forecast of its own RSI-adjacent threshold into a document with legal liability attached. The useful facts are the three admissions inside it. The threshold is defined as a rate (doubling), not an ability. Anthropic says it has missed accelerations until after they happened. And the planned response is to revise the policy to keep humans in control, not to pause. Watch for three things: the RSP revision itself; whether the "baseline rate" metric is ever published; and whether OpenAI's own filing, which CNBC says is targeting a 2027 debut, carries similar language (CNBC) techcrunch +1.

Anthropic's S-1/A financials: $33.24B nine-month revenue, $104B net loss, ~$895.4B committed

3 sources, 3 min read

What happened. The same amended prospectus added third-quarter numbers. The first prospectus, filed the previous week, covered only the first half of the year. CNBC reported the figures on 2 November 2026 (CNBC) cnbc.

Details. According to CNBC, revenue for the nine months to 30 September 2026 was $33.24 billion, about 1,200% above the same period of 2025. Third-quarter revenue alone was about $17 billion, roughly 1,127% above Q3 2025. Quarter-over-quarter growth is the trend to watch. CNBC writes that "Third-quarter revenue increased around 47%, a steep drop from 144% growth in Q2 and 132% in Q1." The nine-month net loss was $104 billion, against a $25.1 billion loss in the same 2025 period, and the Q3 net loss was $23.29 billion. CNBC adds that "most of that was due to the change in fair value of convertible notes and derivative liabilities." Compute and infrastructure expenses rose by $14.4 billion over the nine months, a 329% increase on the prior year. Total commitments across purchase agreements and leases are about $895.4 billion, "substantially all of which is related to compute and infrastructure" (CNBC) cnbc.

What CNBC does not give: gross or operating margins, cash on hand (a related headline mentions a "cash pile" but no figure), valuation, IPO date, share price or offering size. It says only that the roadshow is coming. CNBC says the S-1 has "more than 90 pages of risk factors," including political headwinds, infrastructure complexity and the tension between safety and commercial goals. It quotes the co-founders: "We consider it our personal responsibility to help the world understand these risks" (CNBC) cnbc.

Facts vs. opinions. The headline loss is real in the accounts but is mostly a non-cash mark-to-market on financing instruments, according to CNBC. Reading "$104 billion lost" as "$104 billion burned" would be wrong. CNBC's article does not split out the operating loss, so the operating picture cannot be reconstructed from it. The $895.4 billion is a total of commitments, not spending to date, and the article gives no schedule for when it falls due. The 1,200% growth compares with a much smaller 2025 base. The slowdown from 144% to 47% quarter-on-quarter is the more informative number, and CNBC itself flags it cnbc.

Other perspectives. CNBC points to market concerns: rising interest rates are straining data-centre debt, and hyperscaler capital spending is eating into their cash flows, which could slow how fast compute capacity comes online. For a company with close to $900 billion of commitments that are substantially compute, the risk runs both ways. If capacity comes online slowly, revenue is capped by supply. If it arrives on time and demand slows, the commitments become fixed costs against a shrinking growth rate. The TechCrunch RSI piece notes that coverage of the filing focused mostly on revenue soaring alongside expenses (CNBC; TechCrunch) cnbc +1.

One link between the stories is worth spelling out. The same document says revenue growth is slowing quarter on quarter and that AI-accelerated R&D may imminently cross a policy threshold. An investor could read the second as the growth engine for the first. A safety reader could read the first as the commercial pressure behind the second. The filing contains both, and the co-founders' quote about responsibility sits between them cnbc +1.

Why it matters. These are the first audited-style quarterly numbers from a frontier lab heading to public markets, and they set the frame for OpenAI's filing. CNBC says OpenAI filed confidentially in June and is targeting 2027. For an engineer choosing providers, the practical reading is that Anthropic's supply problems of 2026 have a scale: compute expense up 329%, and commitments in the hundreds of billions. That is the backdrop to this year's rate-limit, plan-restructuring and access disputes revisited in the archive below (CNBC) cnbc +1.

"Sparks of Weight-Space Programming": GPT-6 Astra reads and edits network weights, and the case that it is ordinary research

2 sources, 6 min read

What happened. On 2 November 2026, Rikiya Takehi and Jayden Teoh (equal contribution), with Alex Zhang and Omar Khattab, all at MIT CSAIL, published a blog post titled "Sparks of Weight-Space Programming: LLMs can natively read & write neural network weights." It tests OpenAI's GPT-6 Astra on eight tasks that involve reading raw weights or writing them directly. The next day Sean Goedecke published a rebuttal titled "LLMs are not superhuman at reading and writing neural network weights." Its thesis is "I think a smart human ML researcher could perform all of these tasks" (Takehi et al.; Goedecke) seangoedecke.

Details. The experiments, as the authors report them. In the first, four PPO policies for grid versions of Breakout, Pong, Pac-Man and Freeway, each an identical 500→32→32→5 tanh MLP with 17,253 weights trained for 1 billion PPO steps, were shown to Astra as raw weights with no tools. It named the correct game for 4 of 4 networks without being given a list of options. In the second, three small diffusion models (23,824 weights) generating 12×12 circles, squares and triangles were identified correctly. Astra drew them as outlines, though the models generate filled shapes. The third used character-level transformers (7.16 million weights) trained on Python, romaji or English, with input and output layers removed and up to 100 Python analysis runs allowed but no execution. Astra identified the language correctly in both attempts for every model, with confidences between 0.48 and 0.62. It also located the copying (induction) heads with no false positives against ground truth (Takehi et al.) seangoedecke.

The writing experiments are stronger claims. In experiment four, a Kinetix car-on-ramp policy (171,664 weights) that succeeded in 0 of 256 episodes was edited one-shot with no tools, changing 3.5% of weights, and then succeeded in 1,024 of 1,024. In experiment five, Astra wrote MinAtar networks from all-zero weights with no data, gradients, tools or rollouts. Over 1,000 episodes it scored 517.4 on Breakout against 25.3 for PPO at 500 million steps, 53.1 on Seaquest against PPO's 88.9, and 53.2 on Asterix against PPO's 55.2. In experiment six, it wrote a 1,480,274-weight 9×9 Go network in a single 336-line Python run with zero forward passes. That network won more than half its games against two small PPO networks over 2,000 games each, and with 50 forward passes it beat an equal-sized PPO network trained on 20 million games. In experiment seven, Astra failed 4 of 4 times to tell which of a pair of Gemma 3 270M fine-tunes was sycophantic from weights alone. Given an attention-pattern tool, it picked correctly in 3 of 3 pairs (Takehi et al.) seangoedecke.

The Qwen result that the newsletters headlined is experiment eight. The base Qwen3.5-0.8B, in thinking mode, loops: 85 of its first 96 practice answers hit the 32,768-token cap. Astra removed a single "looping" direction from the MLPs in layers 15 and 19, changing 131,072 weights, or 0.016% of the model. At the post's 50-pass setting, MATH-500 went from 7.9 to 48.1, GSM8K from 13.8 to 67.1 and IFEval from 21.0 to 62.3. The share of answers hitting the token limit fell from 93.0 to 33.1. At 10 and 25 passes, the gains were far smaller (MATH-500 12.3 and 14.1) and looping barely fell. A control on Gemma 3 270M, which rarely loops (8.5% of answers hit the limit), stayed essentially flat on MATH-500, from 6.8 at base to 7.0 at 50 passes (Takehi et al.) seangoedecke.

Paper facts. This is a blog post, not a peer-reviewed paper or arXiv preprint. Its suggested citation is a @misc blog entry, dated 2 November 2026. Authors: Rikiya Takehi and Jayden Teoh (equal contribution), Alex Zhang, Omar Khattab, all MIT CSAIL. The tested model is GPT-6 Astra; the post does not state access terms or model version details. Most networks tested are small (17k to 7.16M weights), the exceptions being the 1.48M-weight Go net and the 0.8B Qwen. Baselines are PPO at various step counts, plus the unedited base models. For the Qwen edit, AMC23, Minerva Math, OlympiadBench, GPQA Diamond and MMLU-Pro are listed as evaluated but no scores are reported. The authors' stated limitations, verbatim: "Fixing loops, however, is not the same as making a model better at math"; "Editing weights could remove an obstacle that hid an ability, but it could not add an ability the model lacked"; capabilities are "still limited, specifically due to inefficiencies in context length and harnesses". They also describe the results as very early. Full logs (prompts, responses, reasoning summaries, code, networks, evaluations) are published on GitHub. The edited Qwen is on Hugging Face. A benchmark and harness are described as still in development (Takehi et al.) seangoedecke.

Facts vs. opinions. The word "superhuman" does not appear in the MIT post. Its closest claims are that capabilities "may extend beyond what we'd expect from humans or conventional algorithms" and, of reading weights, "For almost any human, this is practically impossible." It also predicts that "our neural network weights will soon be natively optimized by LLMs that deliberately reason about their weights." The newsletter summary in today's bundle says Astra "significantly improved" Qwen's mathematical skills. That framing is contradicted by the authors' own caveat that loop removal is not a math improvement seangoedecke.

Other perspectives. Goedecke's case runs task by task. The game networks have input channels mapped directly to grid cells with labels such as "agent", so the L2 norm of first-layer weights per input gives a heatmap of the game layout, which he reproduces in three lines of Python. He calls doing this without code "superhuman mental mathematics, not superhuman AI research." He treats the Qwen edit as the most impressive result but says it closely resembles standard steering-vector and abliteration techniques (he cites the Heretic tool), and that "this is exactly what a competent human researcher could have and would have done." His conclusion is that weight editing is like patching compiled binaries, and that LLMs will advance AI research "by improving training, not by magically tweaking model weights directly." One point of disagreement in framing: Goedecke characterises the base model as already solving problems that need fewer than 32k tokens. The MIT post's numbers show only that most practice answers hit the cap, which is compatible but not the same claim (Goedecke) seangoedecke.

The Hacker News thread on Goedecke's post (137 points, 22 comments at fetch time) split. User aesthesia argued the post corrects a misreading "that seems to have been encouraged by the authors." User simias called the work "fairly standard reverse-engineering." On the other side, aaroninsf called the headline "False, in a way that genuinely matters," arguing the models are superhuman in the plain wall-clock sense. kenjackson doubted typical ML engineers could match the one-shot Kinetix edit and the zero-shot MinAtar networks. StilesCrisis disputed Goedecke's claim that humans would easily spot Pac-Man from a heatmap (Hacker News). These are commenters' opinions seangoedecke.

Why it matters. Both sides are partly right, and the useful split is between experiments. The reading tasks and the Qwen loop fix are plausibly within a skilled researcher's reach, as Goedecke argues. Writing a MinAtar Breakout policy from zeros that outscores 500-million-step PPO, with no rollouts, is a different kind of result. Goedecke handles it only in a footnote, noting that simple programs can be hand-compiled into networks. For the RSI question in the first story, the relevant observation is the post's own: editing removed an obstacle and did not add an ability. That limits the direct-weight-editing route to self-improvement and leaves training, as Goedecke argues, as the main channel. The logs are public, so this is checkable seangoedecke +1.

OpenAI's Pando: a custom Git backend for an agent-driven monorepo

2 sources, 3 min read

What happened. OpenAI published "Scaling Git at OpenAI" on 3 November 2026, describing Pando, a new server-side backend for its monorepo. OpenAI's page returned HTTP 403 to the fetcher for this issue and was not read. The account below rests on Interesting Engineering's write-up, the newsletter summary in the bundle, and a search-result lead for the @OpenAIDevs post that was not opened (Interesting Engineering) openai.

Details. The newsletter summary says Pando was built for concurrent pushes to many branches and maximum read throughput, was deployed without interrupting engineering work or changing how engineers use Git, "cut median push latency in production by nearly 5x," and "now delivers nearly a petabyte of Git data per day." Interesting Engineering reports the same latency gain as a drop of about 80% in median push latency. The two agree: an 80% cut leaves 20% of the original latency, and 1 ÷ 0.2 = 5x. The article's other figures, all attributed to OpenAI: merge reliability of 99.99%, after earlier periods that sometimes fell "below 90 percent"; more than 57 TB of packfiles served in one hour with over 99% of the data from local cache; 10 Gbps network links saturated during clone and fetch; and growth of 2,442% in quarterly monorepo commits for Q4 2026 against Q1 2024. Since Q4 2026 is still in progress, that figure is presumably a projection; the article does not say. Pando was built in Rust in 10 weeks, with one engineer designing the core architecture and teams of Codex agents implementing it, and went into production in April 2026 (Interesting Engineering) openai.

The architecture, per Interesting Engineering: "Pando takes a different approach through causal consistency." It "coordinates updates independently for individual branches instead of imposing one global sequence." "When a developer pushes code, Pando stores the incoming Git packfile in cloud object storage," and "Its metadata service then records the updated branch version and its dependencies," which "allows unrelated branches to accept updates concurrently." On reads, "Pando also reuses previously generated packfiles during downloads," an "Express delivery service stores packfiles in regional caches," and "Workers combine smaller packfiles into larger groups." The stated trade-off: a reader looking across several branches may see them at different versions, but each branch is internally consistent. The article contrasts this with replica-coordination and shared write-ahead-log designs. It does not name the product Pando replaced, describing it only as traditional Git infrastructure (Interesting Engineering) openai.

Facts vs. opinions. Every performance number is self-reported by OpenAI, and the primary page could not be read here. There is no independent benchmark, no description of the previous system's load profile, and no CPU or cost figure in the article read. A search-result lead claimed Pando serves its traffic with a handful of CPU cores, and that OpenAI is not open-sourcing Pando but upstreaming Git fixes. Neither claim was checked against a page that was read openai.

Other perspectives. Search-result leads (not opened) also mention outlets comparing Pando with an Anthropic system named Scion, and a Greg Brockman post offering Pando to others. Neither is verified here. On the engineering itself, the design is familiar to anyone who has run large Git hosting. Content-addressed packfiles in object storage, per-ref consistency rather than global ordering, and pre-computed pack reuse at the edge are how big hosts scale reads. What is new is the cause. The newsletter summary and Interesting Engineering both tie the commit surge to Codex, with humans and agents pushing in parallel. A global sequence of ref updates is the natural bottleneck when hundreds of agent branches update at once (Interesting Engineering) openai.

Why it matters. For the reader's security and infrastructure interest, this is a concrete data point that agent-driven development changes the load shape of developer infrastructure: many writers, many branches, read amplification from CI and agent sandboxes. The causal-consistency trade-off is one an agent harness has to tolerate. An agent that reads two branches may see them at different moments, which matters for merge tooling and for any security control that assumes a single global ordering of ref updates. The claim that Codex agents built most of it in 10 weeks is a vendor claim with no code to inspect. It also fits the story Karri Saarinen tells in today's Ways of thinking section: output is cheap, and the bottleneck moves to review and coordination openai +1.

Claude message threads: stop resending the transcript

4 sources, 3 min read

What happened. On 2 November 2026, Anthropic put "message threads" into public beta on the Claude Platform. Instead of sending the whole conversation on every Messages API call, an agent sends only new messages plus a reference to the previous response (Claude) claude.

Details. Per Anthropic's page, you "add the thread parameter to Messages API requests." "The first request includes the full conversation and starts a thread." "Each request after that includes only the new messages and the ID of the previous response." Anthropic holds each thread "in memory, where it's encrypted and not written to disk," and "A thread expires 5 minutes after its last request." After that, the client must resend everything to start a new thread. "Claude still reads the full conversation on every turn, so token usage stays the same," and "Standard Claude token rates and existing rate limits apply." The single performance figure: median time to first token fell by about 35% for requests of 500,000 to 1 million tokens, measured with threads on by default for most Claude Code users. The feature is available on the native Claude Platform, on Claude Platform on AWS, in Microsoft Foundry and on Google Cloud (Anthropic managed). Anthropic lists the best fits as long-running coding agents, computer-use agents whose screenshots stay in the thread instead of being re-uploaded, and document- or image-heavy workflows (Claude) claude.

The announcement page does not state a beta header, how threads interact with prompt caching, which models are supported, or limits on thread size or concurrency. It points readers to the documentation, which was not read for this issue claude.

Facts vs. opinions. The 35% is a median on Anthropic's own traffic in a specific band of very long requests. It is not a general latency claim, and the page gives no figure for shorter contexts. The page's own qualifier, "The more context an agent carries, the more message threads can reduce time to first token," implies smaller gains below that band. Since token usage and pricing are unchanged, the saving is wall-clock time, plus whatever client bandwidth and serialisation cost goes away. It is not money claude.

Other perspectives. No independent reaction was found. X searches returned nothing and Reddit search failed with a 403 during research. The engineering logic is easy to reconstruct. A 1-million-token request is several megabytes of JSON, often containing base64 images, that has to be uploaded, parsed, tokenised and matched against the prompt cache on every turn. Holding the conversation server-side removes all of that work before the first token. The trade-offs follow from the page's own terms. Threads are state held by the provider, so a 5-minute idle expiry means any agent that waits on a human, a long CI job or a rate-limit backoff falls back to full resends. The client still needs the full transcript for that fallback, so local state management does not get simpler. And "in memory, encrypted, not written to disk" is a meaningful data-handling statement, but the page does not say how it interacts with zero-data-retention agreements. That question is worth putting to an account team before turning threads on for regulated work claude.

Why it matters. This is harness plumbing, and it matches several of today's quick hits. Framer executes agent code as it streams, another item argues for collapsing tools into one exec tool, and LangChain's harness changes moved a fixed model from 53% to 67% on Terminal-Bench (all in quick hits). The common thread is that latency and overhead in the loop around the model now matter as much as the model. For anyone running Claude Code-style agents at 500,000 tokens and up, a roughly one-third cut in median time to first token compounds over hundreds of turns per session, which the page describes as typical. It also nudges the API toward stateful sessions, closer to OpenAI's Responses-style chaining. The comparison is from background knowledge, not checked for this issue claude +3.

From the archive

The Claude Mythos leak (AINews, 31 March 2026)

3 sources, 3 min read

What it said. Seven months ago, AINews summarised r/singularity threads on a Fortune report. Anthropic was testing "Claude Mythos," described in leaked draft materials as its "most powerful AI model ever developed." It sat in a new "Capybara" tier above Opus, was described as a "step change" in reasoning, coding and cybersecurity, and was to be rolled out cautiously, first to organisations able to strengthen cyber defences. The leak was attributed to a CMS misconfiguration, which Anthropic called human error. Commenters doubted the "accidental" framing and noted the irony of a cyber-capable model leaking through a security lapse reddit.

How it aged. The main checkable predictions came true, though the release took an unusual shape. According to Wikipedia's Claude Mythos article (dated sources throughout, not an Anthropic page), leaked blog drafts revealed the model on 26 March 2026. Anthropic announced Mythos Preview and Project Glasswing on 7 April and did not release the model publicly, "citing the model's ability to find software vulnerabilities." More than 40 companies got access, including Microsoft, Apple, Google, AWS, the Linux Foundation, Cisco, Nvidia and Broadcom. So the defenders-first rollout described in the leak is what happened (Wikipedia) reddit.

Then access widened step by step. On 28 May, in the Opus 4.8 announcement, Anthropic said it expected to offer "Mythos-class" models to all customers within weeks. On 2 June access expanded to "150 organizations in more than 15 countries." The same article elsewhere says Glasswing grew "from 50 to 200" organisations in May, so the article contradicts itself. On 9 June Anthropic released Claude Mythos 5 and Claude Fable 5, saying "the two models are identical apart from their safeguards." Fable 5 sends flagged cyber, bio/chem and distillation requests to Opus instead. A 12 June US government letter barring non-US nationals from either model led Anthropic to cut access for every customer. Access began returning for some US organisations on 26 June, Commerce lifted the restrictions on 30 June, and access resumed on 1 July. Mythos 5.1 and Fable 5.1 followed on 1 September (Wikipedia) reddit.

The commenters' security irony also aged well. Wikipedia cites Bloomberg reporting on 21 April that people in a private Discord got into Mythos on launch day "using details from the recent Mercor data breach." On capability, Wikipedia records Anthropic's claim of flaws in "every major operating system and every major web browser," Mozilla's 271 Firefox vulnerabilities found and patched, and more than 10,000 high or critical vulnerabilities found by the first 50 Glasswing partners. By September, according to Patrick Garrity as cited there, only about 10% had been disclosed and fewer than 1% fixed. Wikipedia also records Anthropic's own caveat on exploit tests: full code execution succeeded 72.4% of the time, but below 5% without the two most exploitable bugs, because "almost every successful run relies on the same two now-patched bugs." An AISLE test found that all 8 open-source models it tried could also find one of the headline bugs (Wikipedia) reddit.

What the leak got wrong or left out: the "Capybara" tier name does not appear in the later releases in Wikipedia's account. The public-facing brand became Fable, and Mythos stayed the restricted variant. As of 4 November, Anthropic's pricing page lists Fable access on Pro through usage credits, included in Max "up to half your weekly limit," and Fable 5.1 on the API at $10 per million input tokens and $50 per million output tokens. Mythos appears only as a navigation item (Claude pricing) reddit.

Why it matters now. Mythos is the backdrop to today's lead stories. The capability jump it represented is the kind of thing the S-1 says Anthropic has "in the past not identified" until afterwards. The vulnerability backlog (10,000-plus found, under 1% fixed by September) is the context for today's security quick hits on AI-assisted exploitation. The two-track release, with the same weights shipped under different safeguards to different customers, is now a template that other labs may copy reddit +2.

Cursor trains Composer to summarise its own context (17 March 2026)

3 sources, 2 min read

What it said. In a Cursor research post dated 17 March 2026, Federico Cassano and Sasha Rush described building context compaction into reinforcement learning. "Composer generates from a prompt until a fixed token-length trigger is reached." Then "We insert a synthetic query asking the model to summarize the current context," with scratch space to think, and it continues from the condensed context. Crucially, "the self-summaries themselves are part of what gets rewarded": the final reward applies to every token in the chain, so "poor summaries that lost critical information are downweighted" (Cursor) cursor.

Paper facts. This is a company research blog post, not peer-reviewed. On CursorBench, Cursor's internal benchmark, self-summarization cut compaction-induced error by about 50% against a tuned prompt-based baseline, at both an 80,000-token and a 40,000-token trigger. It used about one-fifth of the tokens, partly by reusing the KV cache. Baseline summaries averaged more than 5,000 tokens, produced by a prompt of thousands of tokens with about 12 sections; Composer's averaged about 1,000. A showcase run on Terminal-Bench 2.0's "make-doom-for-mips" task took 170 turns, with one summary compressing more than 100,000 tokens to about 1,000. The post gives no sample sizes or confidence intervals and releases no code or weights cursor.

How it aged. The technique shipped inside Composer 2 days later, and that launch became known for something else. VentureBeat's Sam Witteveen reported on 22 March that Composer 2, launched as "frontier-level coding intelligence," was built on Moonshot AI's open-weight Kimi K2.5, which Cursor had not disclosed. A developer, Fynn (@fynnso), found it by routing Cursor's API traffic through a debug proxy, which exposed the model ID "kimi-k2p5-rl-0317-s515-fast." Lee Robinson confirmed it and said about one-quarter of Composer 2's compute came from the Kimi base. Co-founder Aman Sanger admitted leaving it out was a mistake, and Cursor committed to naming base models in future. VentureBeat lists Composer 2 at 61.3 on CursorBench (against 44.2 for Composer 1.5), 61.7 on Terminal-Bench 2.0 and 73.7 on SWE-bench Multilingual. It repeats the self-summarization claims, which are Cursor's own (VentureBeat) cursor.

The broader idea, training models to manage their own context rather than relying on harness prompts, became standard harness thinking this year. Today's Claude message-threads release attacks a related cost, the transport overhead of resending long contexts, rather than compressing them. The RAGFlow result in quick hits finds that summary trees and outlines mainly cut tokens rather than raising accuracy. No independent replication of Cursor's 50% figure was found. Searches during research surfaced only secondhand write-ups cursor +2.

Why it matters now. Two lessons hold up. First, compaction is a learned skill, and rewarding it end to end beats hand-written summary prompts, at least by the vendor's own benchmark. Second, the Kimi episode is a provenance lesson for the reader's open-models interest. A model's identity can be read off the wire, and undisclosed base models do not stay hidden. For anyone building their own harness, the practical point is that summaries of about 1,000 tokens beat about 5,000-token ones when the model is trained to write them. Copying the shorter format without the training proves nothing cursor.

"MiniMax M2.7: 90% of Opus 4.6 at 7% of the cost" (Kilo, 22 March 2026)

3 sources, 2 min read

What it said. Kilo's Darko Gjorgjievski ran MiniMax M2.7 and Claude Opus 4.6 in Kilo Code's Code mode on three TypeScript codebases, scored out of 100 points. Test 1, building from a 7-component spec, was worth 35; test 2, investigating 6 planted bugs, 30; test 3, a security audit with 10 planted vulnerabilities, 35. Both models built all components, found all 6 bugs and found all 10 vulnerabilities with correct OWASP categories. The 4-point security gap "is entirely in fix quality". The verdict: "Detection was identical. The gap is in how thorough the fixes are." The cost was $0.27 for M2.7 against $3.67 for Opus across all three tests, at list prices of $0.30/$1.20 against $5/$25 per million input/output tokens. Hence "90% of the quality for 7% of the cost" (Kilo) kilo.

How it aged. The headline needs context before it ages at all. The test was three tasks, scored once, by the vendor of a tool in which MiniMax M2.5 already accounted for 37% of Code-mode usage, per the same post. Per-test scores existed only as images. The arithmetic does hold: $0.27 ÷ $3.67 is about 7.4%. Test 1 also shows a difference in kind that the "90%" score smooths over: Opus wrote 41 integration tests, M2.7 wrote 20 unit tests (Kilo) kilo.

The successor, MiniMax M3, arrived on 1 June 2026, according to Artificial Analysis. It is a 428B-total, 23B-active mixture-of-experts model with open weights on Hugging Face under the MiniMax Community License (commercial use "with restrictions"), 1 million tokens of context, and text, image and video input. Its first-party API price is unchanged from M2.7 at $0.30/$1.20 per million tokens. On Artificial Analysis Intelligence Index v5.0.1, M3 scores 19 and ranks 15th of 23 open-weight models of similar size, "below average" against a median of 23. A search-result lead citing an earlier index version (v4.1) placed it at 44, behind GLM-5.2 at 51. That figure comes from an unopened page and is not checked, and the version change probably explains the gap (Artificial Analysis) kilo.

So the price held and the open-weight line continued, but on the most-cited independent index the "nearly frontier" framing did not survive. The frontier moved too. The models Artificial Analysis now lists on its pages include Claude Opus 5.5 and Fable 5.1, two generations past Opus 4.6. Today's RAGFlow quick hit is a counterpoint: MiniMax M3 inside a plain BM25-plus-grep harness reportedly answered 85% of BrowseComp-Plus. On harness-heavy agentic tasks, these models can be competitive regardless of their index rank kilo +1.

Why it matters now. The lasting lesson is about method. Planted-bug tests with full detection by both models saturate, so the difference lands in fix quality, which three tasks cannot measure reliably. For the reader's own routing decisions, the pattern from Snowflake's quick hit applies: cheap models for detection and triage, expensive ones where thorough fixes matter. That is a routing argument, not a "90% as good" argument kilo +1.

MegaTrain: full-precision 100B+ training on one GPU (arXiv, 6 April 2026)

3 sources, 3 min read

What it said. MegaTrain, by Zhengqing Yuan, Hanchi Sun, Lichao Sun and Yanfang Ye, proposed keeping parameters and optimizer states in CPU memory while it "treats GPUs as transient compute engines." It streams each layer's weights onto the GPU and gradients back out. Two techniques make this work: a "pipelined double-buffered execution engine" that overlaps prefetch, compute and offload across CUDA streams, and "stateless layer templates" that replace persistent autograd graphs (arXiv) huggingface.

Paper facts. arXiv preprint 2604.05091, v1 submitted 6 April 2026, cs.CL cross-listed to cs.DC and cs.OS. The arXiv page lists no venue. A search-result lead said the first author's homepage lists acceptance at CoLM 2026; that page was not opened, so this is not checked. Headline results: training up to 120B parameters on a single H200 with 1.5 TB of host memory; 1.84x the throughput of DeepSpeed ZeRO-3 with CPU offloading on a 14B model; and a 7B model at 512,000-token context on a single GH200. The abstract does not state absolute tokens per second for the 100B-scale runs, and the full-text limitations section was not read. Code is released (arXiv; GitHub) huggingface.

How it aged. The code is real and moving. As of 4 November the repository has 708 stars and 75 forks under Apache-2.0, with no tagged releases. Two news items extend it. On 12 April it gained VERL integration, enabling GRPO training of Qwen3.5-27B on a single H100. On 17 April it gained multi-GPU data parallelism, with four H100s reported to give a "4x linear speedup over single GPU". The features list calls the same thing "super-linear," a contradiction within the repo. The repo's own single-H100 GRPO numbers on GSM8K are the honest cost signal: Qwen2.5-7B at about 120 tokens per second and about 60 seconds per step, Qwen3.5-27B at about 24 tokens per second and about 230 seconds per step. It lists support up to Qwen3.5 MoE 397B-A17B and GPT-OSS 120B, and gives about 12 GB of CPU RAM per billion parameters (GitHub) huggingface.

Microsoft's Azure HPC blog picked it up on 28 May. The post repeats that peak GPU memory stays between 35 GB and 40 GB from 30B to 175B parameters, and describes a single-A100 run at 175B with throughput at 45% of an in-memory baseline, about 2.2x the wall-clock time. These figures do not match the arXiv abstract, which reports 120B on an H200. The blog's own internal figures also conflict: it gives the slowdown as 2–2.5x, 2–5x and 2–3x in different places. Its quoted caveats are more useful than its headline. Interconnect becomes "the primary performance constraint rather than GPU compute capacity." The approach "becomes a hard bottleneck for larger models where layer transfer time exceeds computation time," and I/O amplification "accelerates SSD wear." Treat the Microsoft numbers as a vendor's secondary summary of uncertain provenance (Microsoft Tech Community) huggingface.

No evidence was found of anyone pretraining a 100B model from scratch this way. The adoption that shows up is post-training: RL and fine-tuning of 7B to 27B models on one card. That is consistent with the throughput: at about 24 tokens per second for a 27B model, pretraining at scale is not a realistic use.

Why it matters now. For the own-hardware ambition flagged by the curator, MegaTrain's practical meaning is that host RAM, not VRAM, is the capacity limit, at roughly 12 GB per billion parameters by the repo's figure. A box with 1.5 TB of RAM and one large GPU can fine-tune or RL-train very large open models slowly. Today's weight-sync quick hit (humansand's sub-0.23-second "weight teleportation") and the compute-islands piece address the opposite end, frontier-scale distributed RL. Single-node full-precision post-training now has working code huggingface +2.

Claude Context: a vector-index MCP for coding agents (Zilliz, April 2026)

2 sources, 2 min read

What it said. Zilliz's Claude Context is an MCP plugin that gives coding agents semantic search over whole codebases. It uses a vector database, hybrid search, incremental indexing and AST-based chunking, and claims large token reductions and better retrieval github.

How it aged. Adoption is solid. As of 4 November the repository shows 12.7k stars, 939 forks, 217 commits, 81 open issues and 66 open PRs under the MIT licence. Setup instructions cover Claude Code, Codex CLI, Gemini CLI, Qwen Code, Cursor, Windsurf, Cline and others. The README claims "~40% token reduction under the condition of equivalent retrieval quality." Methodology is relegated to an evaluation directory, and the README names no datasets, baselines or sample sizes. It still requires Milvus or Zilliz Cloud plus an embedding provider (OpenAI, VoyageAI, Ollama or Gemini). In other words, it is also a funnel for the vendor's own database, a conflict of interest the README does not hide (GitHub) github.

The argument against it has strengthened since April. Boris Cherny's statement, as quoted by Vadim Nicolai's March 2026 post, was that "Early versions of Claude Code used RAG + a local vector db," but "we found pretty quickly that agentic search generally works better," being "simpler" without "the same issues around security, privacy, staleness, and reliability." An unnamed Claude engineer in the same Hacker News thread said agentic search "outperformed [it] by a lot." Nicolai also reports the counter-case: grep floods results for common identifiers and misses renamed symbols, and indexing wins in large monorepos and for conceptual queries (vadim.blog) github.

Since then, two research results have pushed the same way. "Is Grep All You Need? How Agent Harnesses Reshape Agentic Search" (arXiv 2605.15184, 14 May 2026, preprint, Sen et al.) tested 116 LongMemEval questions across four harnesses, including Claude Code, Codex and Gemini CLI. It found grep "generally yields higher accuracy than vector retrieval," but that results varied substantially with harness and tool-calling style (arXiv). Today's RAGFlow quick hit goes further. As relayed by @dair_ai, a BM25-plus-grep harness answered 85% of BrowseComp-Plus and 91% of FRAMES with no vector index, and structured indexes mainly cut tokens. That is the same benefit Claude Context claims, at the cost of roughly triple the latency github +1.

Why it matters now. The finding that holds is narrower than either side's slogan. Vector indexes rarely raise accuracy for agentic code search in these tests, and they can cut tokens. That is a cost lever, and it comes with staleness, permission and data-exfiltration costs. Sending your code to a hosted vector store is a security decision as much as a retrieval one. For a self-hosted reader, the defensible default is grep plus BM25, adding an index only where measured token savings justify the operational burden github +1.

Claude Code removed from the $20 plan "test", the ban complaints and the April postmortem (AINews, 24 April 2026)

3 sources, 2 min read

What it said. AINews collected four Anthropic stories. First, an apparent test removing Claude Code from the $20 Pro plan for new sign-ups. Anthropic said the test covered "~2% of new prosumer signups", but commenters noted the pricing comparison page itself had changed. Second, a report of an entire organisation of about 110 users banned without warning. Third, an open letter protesting the Claude 4.6-to-4.7 transition and complaining of hallucinations. Fourth, Anthropic's postmortem of three bugs that made Claude Code worse: reasoning effort cut from high to medium on 4 March (reverted 7 April), a caching bug from 26 March that dropped reasoning history, and a 16 April system-prompt change limiting responses to 25 words between tool calls (reverted 20 April) reddit.

How it aged. The Pro removal was later reversed. Ed Zitron's post of 21 April documents the change: the support page was retitled from "Using Claude Code with your Pro or Max plan" to "Using Claude Code with your Max plan," and Amol Avasare, Anthropic's head of growth, called it a "small test of 2% of new prosumer signups," adding "our current plans weren't built for this." An update on the same post records that "At an unknown time, Anthropic reversed the changes to the website and support documentation" (Where's Your Ed At). As of 4 November, Anthropic's pricing page lists Claude Code as included in Pro at $20 billed monthly, or $17 a month billed annually (Claude pricing) reddit.

The restructuring Avasare hinted at did happen, in a different form. The pricing page now shows Max at $100 a month with 5x Pro usage and $100 a month in API credits. A tier called Ultra at $200 has "No 5-hour limit‡" for verified accounts and 10x Pro usage per week. Mythos-class Fable is metered differently by plan: credit-billed on Pro, included in Max "up to half your weekly limit." Rather than removing Claude Code from the cheap tier, Anthropic made the newest model the thing that is rationed (Claude pricing) reddit.

The compute-constraint explanation behind all of this now has numbers. Today's S-1/A shows compute and infrastructure expenses up $14.4 billion, or 329%, over nine months, and about $895.4 billion in commitments (CNBC). Whether the organisation-wide ban in the April thread was ever explained could not be established; no follow-up was found. The 4.6-to-4.7 complaints were overtaken by later releases: Opus 4.8 in late May and the Fable/Mythos 5 line from June, according to Wikipedia's Mythos timeline (Wikipedia) reddit +1.

Why it matters now. Three lessons still apply. Changes to pricing pages are product decisions even when they are labelled tests. The April postmortem confirmed degradation that users had suspected, which argues for running your own evals rather than trusting perceived model quality, as today's agent-evals quick hit suggests. And depending on one provider whose plans, model versions and access rules change on weeks' notice (including a government-ordered shutdown in June) is an operational risk to design around reddit +1.

Brain & consciousness

Stanford's Digital Brain Project: a foundation-model "twin" from 14,000 hours of imaging

1 source, 2 min read

The Transmitter's Natalia Mesa reports that Stanford's Wu Tsai Neurosciences Institute announced the Stanford Digital Brain Project on 2 November 2026. The aim is to build a "digital twin" of the human brain that predicts brain activity. The team of almost a dozen Stanford researchers includes Dan Yamins and Russell Poldrack. Funding comes mainly from Mark and Mary Stevens, with additional money from Clara Wu Tsai; Stanford would not disclose the amount. The plan is about 100 participants over five years in 10 data-collection campaigns. The first involves 10 people, each scanned roughly twice a week for a year in each modality. The modalities are 7-tesla fMRI, at about millimetre resolution but lagging neural activity by several seconds, and optically pumped magnetometer MEG, at millisecond timescale but with coarser localisation, worn as a helmet with hundreds of sensors. The tasks progress from videos to decisions to video games and VR. The model, trained on about 14,000 hours of imaging, builds on existing task-trained models that already predict some brain activity. The data will go to OpenNeuro and the computing will run on Stanford's Marlowe GPU cluster (The Transmitter) thetransmitter.

The scepticism in the piece is specific. Bing Wen Brunton (University of Washington) said she is "kind of skeptical of all ventures in science and engineering" built on "Name hard problem X. Let's build a foundation model for problem X," and asked "What's the evidence that this is going to work, besides that we're hoping it does?" Caterina Gratton (UIUC) asked: "Can we even make any digital brain that's a reasonable simulation of any one person at all?" Nikolaus Kriegeskorte (Columbia), who is part of a competing Meta-backed effort with the same name, called the question of whether either project will gather enough data "a very difficult question that I don't have a good answer to." For scale, the article gives Meta's project as $15 million, 15,000 hours planned, nine funded teams and at least 90 participants, launched in August. It says Meta's TRIBE v2 used more than 1,000 hours from 720 people, and that current models explain about half of response variance (The Transmitter) thetransmitter.

For whole-brain emulation, be clear about what "digital twin" means here. It is a model that predicts BOLD and MEG signals at millimetre and millisecond resolution from stimuli and tasks. It is not a model of neurons or synapses, and nothing in the article claims mechanistic fidelity. Brunton's point that testing brain-likeness requires researchers to "poke at the inside of it" is the emulation question in miniature. A model can match aggregate signals without matching how the brain computes. The stated end goal, forecasting an individual's response to TMS or focused ultrasound, is a predictive-medicine aim and should be judged as one. Deep within-subject sampling, hundreds of hours per person, is the part most likely to yield something durable whatever the model does thetransmitter.

Ila Fiete: the genome is a recipe, not a blueprint

1 source, 2 min read

In a Transmitter perspective of 2 November 2026, MIT's Ila Fiete argues that "genes set the rules and turn the knobs, and self-organization does much of the rest." She contrasts blueprint mechanisms (Sperry's chemoaffinity, Wolpert's French-flag gradients, the fly bicoid cascade) with self-organisation (Turing patterns, mechanical forces). Blueprint models scale with body size but are noise-sensitive and gene-hungry. Turing patterns are robust and gene-cheap but produce a single spatial scale. Hence her question: "not which mechanism the brain uses, but which it uses where and at what stage of development." Her examples are digits formed by a Wnt/BMP/SOX9 Turing pattern (James Sharpe's group); fly gap genes that still rely on network dynamics (Thomas Gregor's team); and her own grid-cell work with Mikail Khona and Sarthak Chandra. In that work, two local interactions, one graded and one of fixed width, produce discrete grid modules through "peak selection." Module count does not depend on network size, and the model is testable with future connectomics. In her visual-cortex model with Talia Konkle, activity-dependent growth under a synaptic "construction budget" yields areas, hierarchy and retinotopic maps from spontaneous waves alone. It predicts smooth gene-expression gradients rather than steps at area boundaries (The Transmitter) thetransmitter.

The piece contains no genome-bits-versus-synapses calculation. Its case is about mechanism, evolvability ("Evolvable systems are controllable systems") and control, not information capacity. It also includes P. Robin Hiesinger's caveat that even "recipe" gives genes too much credit, because the order and timing of developmental steps can themselves emerge (The Transmitter) thetransmitter.

For emulation this cuts two ways. If adult wiring is largely the output of self-organising rules run on activity, then a static connectome scan captures the cake but not the recipe. That may be enough to run a brain, but not to understand why its parameters are what they are or how it would rewire. On the other hand, Fiete's testable predictions (gradient slopes, interaction widths, smooth expression gradients) are exactly what joint connectomic and transcriptomic datasets can check. That makes her framework a reason to collect both modalities together thetransmitter.

What neuroscience loses without primates

2 sources, 1 min read

The Transmitter's Alissa de Chassey asked 17 neuroscientists which questions would go unanswered if support for nonhuman primate research keeps falling. The page names 11. The page itself is dated 9 October 2026, although the newsletter carried it on 3 November. Its context is three US federal moves from the past year: FDA plans to phase out all animal testing by 2030, the CDC closed its nonhuman primate programme, and the NIH said it would favour animal-free "new approach methodologies" such as organoids and computer models (The Transmitter) thetransmitter.

The answers are concrete. Jonathan Pillow (Princeton) said AI-based virtual brains are still far off: "We don't know enough about the brain yet." J. Anthony Movshon (NYU) noted that mice lack trichromatic colour vision. Bruno Averbeck (NIH) said monkeys learn tasks in "three or four trials, based on how much reward they're getting." Jonathan Michaels (York): "When it comes to dexterous motor behavior, nonhuman primates are by far the ideal model." Mark Churchland (Columbia) noted that stroke symptoms in humans differ greatly from rodent models. Katalin Gothard (Arizona) said of eye-contact studies: "That's an experiment you cannot do with mice or rats; very few other animals make eye contact." Jay Rappaport (Tulane) said new approaches are "really not quite ready to replace whole animals." The article's grouped lists of open questions are not attributed to individuals (The Transmitter) thetransmitter.

Read alongside the Stanford story, there is a policy irony. The NIH favours computer models as replacements just as the Stanford brain digital-twin effort faces open questions about its scientific utility and feasibility. Human BCI and motor-cortex neurotech relied heavily on primate electrophysiology. If that pipeline thins out, model validation will lean harder on human invasive data, which is scarce and ethically constrained thetransmitter +1.

Ways of thinking

Internal DDoS: when output outruns attention

4 sources, 2 min read

Karri Saarinen (Linear) argues, in a post dated 2 November 2026, that organisations now face a denial-of-service attack from inside. No one is malicious. The volume of well-meant work simply exceeds the capacity to review and decide: "We can generate changes much faster than we can give them that attention." The risk is "leadership losing the ability to steer." His three moves follow. Stop "treating output as proof of value," because "A working implementation shows that something can be built, not that it belongs in the product," and "Some changes have negative value." State intent upfront ("what we're betting on, what matters right now, what's out of scope") so that "People and agents can check their own work against it." And gate releases deliberately. Linear "had to lock down our internal release channel because things were changing too quickly," and the gate "gives us one place to consider changes together before they land." He also admits the gate tracks change but does not confirm direction (Karri Saarinen) karrisaarinen.

The model generalises as a queueing statement. When arrival rate exceeds service rate, queues grow without bound, and the fixes are to raise service rate, lower arrivals, or drop requests at admission. Agents raise arrival rate almost for free. Review, the service rate, is still bounded by human attention. Saarinen's intent statement is admission control (rejecting work early by checking it against declared scope), and his release gate is batching. The DDoS analogy also suggests a fix he does not name: rate limiting at the source, meaning a cap on how many open agent branches each person or team may have.

Today's news fits it closely. OpenAI built Pando because agent-driven commits, a 2,442% quarterly increase by its own figure, overwhelmed its Git servers. That fixed the machine side of the queue but not the human side (Interesting Engineering). Maple's 287,000-line React port by about 40 Claude agents took three days. But code review still found about 180 defects the 2,600-variant screenshot harness missed, which is what review capacity is for. Anthropic's S-1 disclosure that it may soon reach its internal definition of recursive self-improvement, where AI systems help develop increasingly capable AI models, is the same structure at a lab: generation outrunning verification. The honest version of Saarinen's argument applies there too: a gate tracks change without confirming direction karrisaarinen +3.

Wildcards

NVIDIA's June open-model push: Cosmos 3, Nemotron 3 Ultra, RTX Spark (2 June 2026)

2 sources, 2 min read

Why this is here: exploring LLM personalities, open models, and AI commentary.

The saved item is a 2 June post by NVIDIA's Ming-Yu Liu introducing Cosmos 3. It claimed top spots across "8+ open model leaderboards," including "#1 open" on world reasoning. The AINews commentary around it pointed to Nemotron 3 Ultra, a 550B-total, 55B-active open-weights LLM it called "the new US SoTA," and to an RTX Spark personal computer previewed with OpenClaw and Hermes Agent as launch partners x.

What holds up, five months on. Artificial Analysis, which says it partnered with NVIDIA on the evaluation, scored Nemotron 3 Ultra at 48 on its Intelligence Index with BF16 weights. That puts it ahead of the other US open-weights models it listed: Gemma 4 31B at 39, Nemotron 3 Super at 36 and gpt-oss-120b at 33. It remained behind the China-led open frontier, with Kimi K2.6 at 54. So "US SoTA" was accurate in the narrow sense of best American open-weights model on that index, not best open model. Artificial Analysis also measured over 300 tokens per second on a pre-release DeepInfra endpoint, against a typical 50 to 100 tokens per second for comparable DeepSeek and Kimi models. It describes the model as about 550B total and 55B active, roughly 90% sparse (Artificial Analysis) x.

The Cosmos 3 leaderboard claims rest on NVIDIA's own post in the bundle. Search-result leads said Artificial Analysis ranked it first among open-weight models on text-to-image and image-to-video, but that page was not opened, so the claim is not checked here. The RTX Spark "1 petaflop" figure was not checked either x.

Why this fits the reader's interests: the open-models question in 2026 is increasingly geopolitical and commercial rather than technical. NVIDIA releasing big open weights is partly a demand play. Open models that run fast on NVIDIA hardware sell NVIDIA hardware, and "most intelligent US open model" is a positioning claim aimed at buyers barred from Chinese weights. The MiniMax archive item above shows the other side. Chinese open models kept prices low ($0.30/$1.20), though Artificial Analysis now scores MiniMax-M3 at 19 on its Intelligence Index, below the median of comparable open models. On "LLM personalities": Artificial Analysis now runs an AA-PersonalityBench that lists Claude Opus 5.5 and Fable 5.1 among its models, a sign that model temperament is becoming something people benchmark (Artificial Analysis). Whether that benchmark measures anything stable was not examined x +1.

Verdict: the Nemotron claim holds up in its narrow form and is independently scored, though by an evaluator that says it partnered with NVIDIA. The Cosmos claims are NVIDIA's own until checked.

Quick hits

Agents & tooling

9 sources, 2 min read

• Agents converge on one exec tool. One newsletter item argues that agents are collapsing their tool catalogues into a single "exec" tool, so models write short scripts that chain and await actions inside sandboxes rather than calling one tool per turn philschmid.
• Framer's Harness 2 runs agent code while it streams. Framer says executing JavaScript as it streams, with eager execution and early cancellation, gives up to 33% lower cost and 20% faster execution, 43% fewer tool steps and 39% fewer cached input tokens per message. The figures are vendor-reported framer.
• Harness over model, again. A Decoding AI course launch cites LangChain moving its agent from 53% to 67% on Terminal-Bench by changing only the harness, from outside the top 30 to the top 5. It also claims about half of Ramp's merged PRs come from a custom harness. The newsletter carried a sponsor, and its numbers are unverified source.
• Porting 287,000 lines of React in three days. Maple moved its observability app to Foldkit with about 40 Claude agents, putting most human effort into a harness comparing more than 2,600 screen variants. Review still found about 180 defects the screenshots missed, and the startup bundle roughly doubled maple.
• Microsoft's Copilot Cowork went Python to Rust while live. Microsoft says it reached global availability in four and a half months, crediting written specs, narrow agents with clear boundaries and automated checks that genuinely verify changes microsoft.
• Figma's PM OS. Figma PMs use 31 Claude Code skills for context gathering, Slack updates, artifacts and experiment generation, per Lenny's Newsletter lennysnewsletter.
• Next.js 16.4 ships an agent skill for trimming client JS. It uses Turbopack's module graph to find eager imports, duplicate dependencies and missed tree-shaking. Vercel reports removing or deferring nearly two megabytes of compressed JavaScript across v0 and vercel.com pages nextjs.
• AWS Agentic AI Lens as a Claude skill. Smarsh checks a repo against all 150 practices and gets an evidence-cited workbook in hours. It surfaced missing prompt-injection screening and cost controls amazon.
• Grep and BM25 match indexed retrieval. As relayed by @dair_ai, InfiniFlow's "Context as Infrastructure" paper reports a BM25-plus-grep harness with MiniMax M3 answering 85% of BrowseComp-Plus and 91% of FRAMES without any index. Navigation trees cut query tokens by 91% where evidence sufficed, at roughly triple the latency. Secondhand via X; the paper was not read x.

Models & research

7 sources, 1 min read

• GPT-6.2 Astra spotted in Codex. TestingCatalog reports GPT-6.2-Astra appearing in Codex usage breakdowns, likely an A/B test or staged rollout. It says OpenAI reportedly skipped GPT-6.1 Astra over deception and scope concerns. That claim is unconfirmed testingcatalog.
• OpenAI's LifeVal. A benchmark for everyday tasks such as budgeting, finding childcare and accessing government services. Details were not checked openai.
• Teaching Qwen Why. A LessWrong post extends Anthropic's "Teaching Claude Why" methods, synthetic document fine-tuning and SFT on stories and ethical dilemmas, to Qwen to reduce agentic misalignment lesswrong.
• LLM novelty judges are unstable. Ai2's benchmark, built from ICLR 2026 reviews, finds small prompt changes swing accuracy by more than 50 points on AI-generated ideas, and extra retrieval or reasoning did not reliably help allenai.
• R²Orch. A Hugging Face paper (89 upvotes) on recursive self-improvement for agent orchestration via self-play in a skill-internalisation loop. Not read; claims not checked huggingface.
• Mechanism design for agents. MIT Technology Review on "reverse game theory": designing rules (as in cut-and-choose cake splitting) so that rational agents are incentivised to comply. The piece notes big open questions about practice technologyreview.
• Smaller models, routed. Snowflake argues for model routing over defaulting to the biggest model, citing internal tests of up to three times better token efficiency on some agent workflows. Vendor-run techradar.

Infrastructure

3 sources, 1 min read

• Training on compute islands. Coreauto argues that frontier runs could span many smaller clusters of mixed accelerator generations and vendors. It warns that one faulty or compromised site could quietly degrade or tamper with a model in ways that are hard to trace coreauto.
• Swarm training. General Reasoning on "collective inference-time scaling" and designing RL incentives for parallel cooperating agents gr.
• Weight teleportation. Humans& reports trainer-to-sampler weight-sync pauses under 0.23 seconds for RL, using GPU-accelerated LZ4/Snappy compression with a Zstd layer humansand.

Security

8 sources, 1 min read

• ChatGPT account takeover chain. Parameter Labs, via Simon Willison: the MathLive library in ChatGPT's HTML Previews could spawn an iframe loading YouTube scripts despite CSP. YouTube's oEmbed endpoint could then reach OpenAI API endpoints and steal data from anyone opening a share link simonwillison.
• Langflow unauthenticated RCE. IBM reports four flaws in 1.0.0 through 1.12.8, including an auth bypass (CVE-2026-93680) and code execution via MCP tool enumeration (CVE-2026-110186). A public Metasploit module enumerates Langflow MCP tools without credentials. Only 1.13.0 fixes them, and there is no workaround thehackernews.
• GitLab max-severity RCE under active exploitation. More than 1,000 internet-facing servers are still vulnerable to CVE-2026-97229 in the CI/CD regex compiler, now in CISA's KEV catalogue. Self-hosters should patch bleepingcomputer.
• WorkOS breach used an AI-assisted offensive framework. Unauthorised access on 30 October to an internal sales app exposed business contacts, account histories and excerpts of customer communications. External access is disabled pending investigation workos.
• Pragmatic Engineer on a bad week. Guessable CA keys, critical PHP, GitLab and Node.js flaws, leaked Railway customer secrets and a month-long TiDB control-plane breach. The argument is that AI makes exploitation faster and cheaper, so security spending will rise pragmaticengineer.
• Supermarket freezers set to defrost. A suspected attack across seven European countries pushed freezer temperatures reportedly to 50°C. One Delhaize branch reported €100,000 in losses, and Sabcobel says affected units need physical changes, per the BBC bbc.
• Wake and Break. A PSP exploit for AMD navi31 GPUs disables the firmware signature check so the card loads unsigned IP firmware github.
• GitHub enclaves. A new primitive for cross-repo agentic workflows that limits what agents working on different private repositories can tell each other githubnext.