TheInformation had the scoop, and now they have the confirmation — Nvidia is buying HuggingFace for $13B, roughly 80x their $150M ARR, having doubled its customer base in 2026. This is almost double Nvidia’s initial $7B offer in Jan 2026.

What can we say? We love it when the good guys win. But in the backdrop of GLM-5.3-Flash (aka Ox Alpha) impressing everyone (except GDM vaguepoasters) and Qwen also shipping an impressive Flash model on chinese chips, perhaps the post Hot Chips conversation about Western open AI is a great backdrop for this.

AI News for 8/25/2026-8/26/2026. We checked 12 subreddits, 544 Twitters and no further Discords. AINews’ website lets you search all past issues. As a reminder, AINews is now a section of Latent Space. You can opt in/out of email frequencies!

AI Twitter Recap

Top Story: GLM 5.3 Flash launch and reactions

What happened

Z.ai formally launched GLM-5.3-Flash, revealing that the previously previewed “Ox Alpha” model is its public identity.

• Z.ai announced GLM-5.3-Flash as a natively multimodal model with a 1M-token context window, 320B total parameters / 18B active parameters, released under the MIT License, and available via weights, API, chat, coding plan, and AutoClaw.

• Z.ai simultaneously positioned it as a highly price-competitive successor to GLM-5.2, claiming on its internal benchmark that it outperforms GLM-5.2 at every effort level and is on par with Claude Opus 4.8 on coding.

• The launch also resolved the long-running Ox Alpha mystery: multiple posters explicitly connected Ox Alpha to GLM-5.3-Flash, including SemiAnalysis, rasbt, theo, and Cline.

• Early third-party model infrastructure support appeared almost immediately: CoreWeave, Baseten, and Cline’s free integration in VS Code / JetBrains / CLI.

• Shortly after launch, Z.ai engineer Zixuan Li said the chat template had been updated and early downloaders should re-download the model, implying a day-0 packaging or prompt-format correction.

• Artificial Analysis first published an overview with an incorrect 400k context window, then issued a correction to 1M context, aligning with Z.ai’s original announcement.

• Community response was unusually strong for an open-weight release, ranging from brief shock reactions like “HOLY” to more substantive claims that the model may now be the best intelligence-per-dollar option, e.g. Artificial Analysis and zainhas.

• The launch got folded into a broader narrative around Chinese frontier open models, with posts arguing that open Chinese labs are converging on similar architecture choices around linear attention, sparse attention, residual path design, and Muon.

• Independent pushback emerged on at least one modality claim: skalskip92 argued the model looks weak on several vision/object detection tasks despite being “native vision.”

Official claims and launch details

Z.ai’s primary launch tweet is the factual anchor: GLM-5.3-Flash is described as:

• 320B total params / 18B active

• 1M-token context

• natively multimodal

• MIT licensed

• previously previewed as Ox Alpha

• “running entirely on Chinese AI chips”

Distribution/availability at launch:

• Weights on Hugging Face

• Z.ai API

• Chat

• ZCode

• Coding plan

• AutoClaw

The strongest self-reported vendor performance claim came from Z.ai’s coding thread: on the Z.ai Code Bench, GLM-5.3-Flash “clearly outperforms GLM-5.2 at every effort level and performs on par with Claude Opus 4.8”. Because this is first-party benchmarking, it is useful but should be read more cautiously than independent evals.

A follow-up launch-support post from AutoClaw framed the model as suitable for vision-language understanding, code generation, and long-horizon agentic tasks and paired availability with credits/rebates, but this is mainly rollout information rather than new technical evidence: AutoClaw launch post.

Independent benchmarks and cost/performance positioning

The most substantive independent evaluation in the tweet set came from Artificial Analysis. Their summary: GLM-5.3-Flash scores 57 on the Artificial Analysis Intelligence Index.

Artificial Analysis metrics cited

• AA Intelligence Index score: 57

• Gap vs GLM-5.3: 3 points behind GLM-5.3 at 60

• Cost per task: $0.09

• API price: $0.15 / 1M input, $0.50 / 1M output

• Cached input: ~$0.026–$0.03 / 1M, described as 80% discount

• Model size: 320B total / 18B active

• License: MIT

• Context: initially listed as 400k, later corrected to 1M

Comparisons cited by Artificial Analysis

• Ties GPT-5.6 Terra and Muse Spark 1.2 at 57, but at much lower cost per task.

• $0.09/task vs $0.68/task for GLM-5.3 max.

• Claimed ~7.5x lower cost per task than GLM-5.3 max.

• Claimed ~5.7x cheaper per task than GPT-5.6 Terra and ~4.4x cheaper than Muse Spark 1.2.

Token-efficiency and reasoning mix

Artificial Analysis notes an interesting tradeoff:

• GLM-5.3-Flash used 149M output tokens to run the Intelligence Index

• compared with 168M for GLM-5.3

• but more than Kimi K3 (133M) and Qwen3.8 2.4T A95B (136M) at similar Intelligence Index score

• 134M of the 149M tokens (~90%) were reasoning tokens

This is an important nuance: the model’s economics look excellent largely because token pricing is extremely low, not because it is especially token-frugal.

Agentic/work evals from Artificial Analysis

Artificial Analysis also reports that GLM-5.3-Flash is stronger than its raw knowledge metrics might imply on agentic tasks:

• GDPval-AA v2 Elo: 1770

  • tied within margin of error with GLM-5.3 and Grok 4.6

  • behind only Claude Opus 5 xhigh/max

• Terminal-Bench v2.1: 84.3% vs 83.9% for GLM-5.3

• τ³-Banking: 47.2%, trailing GLM-5.3 by 3.1 percentage points

Knowledge/hallucination stats

• AA-Omniscience score: +7

• Accuracy: 28%

• Hallucination rate: 28%

• Compared with GLM-5.3:

  • GLM-5.3 accuracy 34%

  • GLM-5.3 hallucination rate 30%

• Compared with GPT-5.6 Terra:

  • Terra accuracy 47%

This suggests a recurring theme in reactions: GLM-5.3-Flash may be much stronger on practical code/agentic workflows than on broad real-world factual knowledge.

Architecture and systems details

Several technically informed reactions tried to reverse engineer or summarize what changed from GLM-5.2 / GLM-5.x.

The most detailed public architecture breakdown in the tweet set came from rasbt, who says GLM-5.3-Flash moves from GLM-5.2’s 744B-A40B backbone to 320B-A18B, and uses:

• Kimi Linear-style 3:1 hybrid attention

• 34 KDA layers (Kimi Delta Attention)

• 11 MLA/DSA layers

  • MLA = Multi-head Latent Attention

  • DSA = DeepSeek Sparse Attention

• DeepSeek V4-style mHC residual path

• four parallel streams

• plus a native vision encoder

The same tweet describes it as “super hybrid” because both major attention components are already “efficient” variants rather than a simple efficient/full-attention hybrid.

Another useful systems-oriented summary from thealexker frames the release as an efficiency story, highlighting:

• compared to GLM-5.2:

  • ~1/10 the cost

  • active params 32B → 18B

  • layers 92 → 45

• hybrid linear + sparse attention

• smaller average KV cache per layer

• lower attention compute compounding at long contexts

• claims that visual intelligence benefited from coding/RL style improvements

• says the GLM-5.3 infrastructure agent co-authored parts of the work by helping with kernels, bottlenecks, and serving stack optimization

The broader context post from eliebakouch is opinionated but technically notable because it places GLM in a Chinese open-model trend:

• nearly all Chinese frontier models now use linear attention

• nearly all use sparse attention / indexer-compression designs

• many use fancy residuals like mHC, attention residuals, gated residuals

• many use Muon

That post is not a direct GLM paper summary, but it helps explain why the architecture details immediately resonated with model engineers: GLM-5.3-Flash appears to be another data point in a fast-converging efficiency-first Chinese frontier OSS design space.

Chinese chip angle and serving implications

The hardware/serving side was one of the most-discussed parts of the launch.

Z.ai itself said the model was “running entirely on Chinese AI chips”. The strongest amplification came from SemiAnalysis, which focused on the claim that 100T tokens/day are being served on Chinese chips. That tweet does not provide all the derivation, but it framed the infrastructure feat as the most shocking part of the reveal.

Reactions emphasized the significance:

• theo: “Ox being a ‘flash’ model is insane. Serving all the traffic on Chinese chips is even more insane.”

• same-day OSS mood post folded GLM into a broader celebratory open-source narrative.

There was also explicit back-of-envelope capacity reasoning from teortaxesTex:

• If inference economics are comparable to V4-Flash,

• 10K tokens/s/NPU is “realistic”

• 864M/day per chip

• 100T/day would imply about 116K chips

• suggesting 100K+ chips scale, “doable” but consuming an enormous fraction of total compute

That estimate is speculative rather than confirmed, but it shows how engineers interpreted the serving claim: not as marketing fluff alone, but as an infrastructure statement implying very large domestic accelerator fleets and mature inference optimization.

Adoption and distribution reactions

A notable part of the reaction cycle was how quickly usage posts appeared.

Cline said GLM-5.3 Flash was already its fastest growing model in Cline history, driving 11% of all traffic in less than a week, while also advertising it as free in Cline. This is partly promotional, but it is also a concrete demand signal.

Infrastructure providers moved quickly:

• CoreWeave: “coming soon to CoreWeave Serverless Inference”

• Baseten: day-0 availability, emphasizing general intelligence + agentic coding, native vision, and 1M context

• Dell via Jeff Boudier: framed GLM 5.3 Flash and Qwen 3.8 Flash as open models ready for on-prem deployment

This matters because it reinforces that GLM-5.3-Flash was not treated as a curiosity; it was immediately slotted into real inference/developer stacks.

Facts vs opinions

Facts / externally attributable claims

• Z.ai launched GLM-5.3-Flash as 320B total / 18B active, 1M context, MIT-licensed, multimodal, previously previewed as Ox Alpha.

• Z.ai claims the model runs on Chinese AI chips.

• Artificial Analysis reports AA Intelligence Index 57 and $0.09 cost/task, plus various benchmark details and pricing.

• Artificial Analysis later corrected its context listing from 400k to 1M.

• Zixuan Li said the chat template was updated and model users should re-download.

• Cline said the model drove 11% of all traffic in under a week.

• Baseten, CoreWeave, AutoClaw, and others announced support/distribution.

Opinions / interpretations

• theo, zephyr_z9, and nicdunz expressed strong positive surprise.

• thealexker interpreted the release primarily as a story of efficiency engineering.

• eliebakouch framed it as evidence of exciting convergence in Chinese frontier open architectures.

• zainhas argued it is now the best intelligence-per-dollar choice.

• skalskip92 argued the model is bad at vision, pushing back on the launch’s multimodal framing.

• scaling01 alleged it was “painfully obvious” Ox Alpha was a GLM model and further alleged ZAI used hype accounts; that claim is unverified in the tweet set.

Different perspectives

Read more

By far the biggest announcement at the 37th Hot Chips conference was OpenAI’s stunning progress on their own chip, less than a year after the Broadcom announcement… and that it isn’t an ASIC; but a full on Blackwell-beating alternative.

The key metric now is shifting to performance per watt, and Jalapeno delivers:

The full Hot Chips presentation is not yet out but various takes are below. For a fuller breakdown, watch along with the rest of OpenAI:

AI News for 8/24/2026-8/25/2026. We checked 12 subreddits, 544 Twitters and no further Discords. AINews’ website lets you search all past issues. As a reminder, AINews is now a section of Latent Space. You can opt in/out of email frequencies!

AI Twitter Recap

OpenAI’s Jalapeño Inference Chip and the Shift in the Inference Stack

• Jalapeño’s published numbers are the day’s biggest technical story: OpenAI released first benchmark details for its custom inference chip Jalapeño, claiming materially better efficiency and latency than NVIDIA GB200/GB300 systems on real model workloads. In OpenAI’s tests, Jalapeño delivered 1.5–1.9× more work per watt at peak throughput and 1.7–3.6× lower end-to-end latency, with 2.1–4.1× higher performance for highly interactive workloads; the chip is rated at 700W but reportedly stayed at or below 550W on the tested runs. OpenAI says deployment into its own infrastructure begins by year-end, with Gen 2 already deep in development and Gen 3 underway (OpenAI announcement, deployment roadmap, Sam Altman).

• Why engineers care: the claim is not just raw perf, but a more balanced inference architecture that reduces the usual throughput/latency tradeoff. Multiple technical reactions highlighted that some comparison points are especially notable because Jalapeño reportedly performed well even without tricks like aggressive prefill/decode disaggregation or speculative decoding in some setups, while beating systems that did use them (gdb, kimmonismus summary, eliebakouch analysis, You Jiacheng). SemiAnalysis framed it as unusually strong for a first-generation ASIC and compared it directly against Blackwell and Rubin-class systems (SemiAnalysis, dylan522p).

• A second-order story is model-assisted systems optimization: OpenAI’s post also said GPT-Astra + Codex helped write and optimize low-level kernels, bringing three previously unplanned open-weight models to high performance on Jalapeño in about two months; for selected attention and MoE blocks, these implementations reportedly ran 1.5–1.8× faster than existing human-expert-written code (kimmonismus, eliebakouch). That is a meaningful signal that compiler/kernel work is increasingly being folded into the model improvement loop, not just application-layer coding.

• Broader infra implication: several posts tie Jalapeño to a larger industry transition in which frontier labs may no longer be strictly downstream of NVIDIA for inference economics, even if packaging and foundry capacity remain a hard bottleneck (Liam Fedus, teortaxesTex reaction, LearnOpenCV caveat on TSMC/CoWoS capacity).

Agent Harnesses, Memory Systems, and Eval Engineering Becoming First-Class

• Harness quality is increasingly as important as model choice: several papers and launches converged on the same theme: agent performance depends heavily on the surrounding system. A new Microsoft-led paper on AutoSaddler treats the harness as code and patches prompts, tool configs, and control logic offline using failure traces, reporting gains of +9.0 on GAIA2, +9.6 on SWE-Bench Pro, and +10.0 on Terminal-Bench 2.0 over base harnesses (paper summary). In parallel, another paper quantified harness variance directly, finding that swapping harnesses could move scores far more than swapping models, with model-pair rankings flipping across scaffolds; the proposed fix is a structured Harness Card disclosure standard (analysis, “There Is No Neutral Harness”).

• Long-horizon software engineering remains very unsolved: SWE Refactor Bench measures whole-repository migration tasks like C→Rust, Maven→Gradle, and POSIX→WebAssembly across real projects including SQLite, zlib, and libsodium. Across 520 runs, only 28 survived all three stages, for a 5.4% survival rate, and 13/20 tasks were solved by nobody (EinsiaAI). This is a useful corrective to strong bug-fix numbers on more local coding benchmarks.

• Memory systems are being redesigned as programmable state, not compressed chat history: one Alibaba paper summarized by DAIR backs agent sessions with an append-only event log plus a persistent Python kernel, binding tool outputs and derived state to typed variables instead of continually serializing them into prompts. Reported results include 94.8% on LongMemEval_S, 73.1% on BEAM_10M (+5.1 over the previous best published memory system), and 86.7% on LOCA_256K with Qwen3.8-Max (summary). Related work on Knowledge Triage showed that naive context compaction destroys exact-rule retention; after five rounds of compaction, one setup preserved only 10% of safety rules, while type-aware retention policies preserved 2–4× more (summary).

• Practical eval-engineering is moving from ad hoc to productized workflows: LangChain/partners shared a concrete loop for turning traces and human feedback into task specs, synthetic environments, and evals that can be used to measure and post-train agents over time (Vtrivedy10, hwchase17). LangSmith Engine also shipped >2× better performance on key internal benchmarks with better issue detection/clustering, SaaS and self-hosted support, Slack/Linear integrations, and cost-tiered analysis modes (LangChain).

Local-First Agents, On-Device Inference, and the New Personal Compute Stack

• Perplexity’s Portable Computer is the clearest local-agent product launch of the day: Perplexity launched Portable Computer on NVIDIA DGX Spark, positioning it as a fully local version of Perplexity Computer where the orchestrator LLM, subagent LLM, and agent harness all run on local hardware with no cloud dependency (Perplexity launch, model details, NVIDIA, Arav Srinivas). The initial local stack uses a post-trained PPLX 27B with Qwen 3.8 27B also available; Nemotron 3.5 Lightning support is coming.

• The deeper trend is persistent, always-on local agents: Srinivas explicitly sketched a future of background processes that continuously ingest context from connectors, perform multi-hop reasoning in a perpetual loop, and run on your own hardware (Arav Srinivas). Community reactions were split between excitement about privacy/control and skepticism that “local-first” should mean a $5k DGX Spark rather than commodity consumer devices (theo critique, theo follow-up).

• Apple/macOS local AI tooling is also maturing: exo said Apple featured it on new M5 Ultra Mac Studio and M6/M5 Pro Mac Mini pages, emphasizing low-latency RDMA over Thunderbolt 5 to cluster Macs and run models like Kimi K3 and GLM-5.3 at API-like speeds, with 4× M5 Ultra scaling to about 4.8 TB/s aggregate memory bandwidth (exo). Related posts pointed to Apple’s faster PCIe storage and ANE-based vision pipelines as making small local clusters and mixed CPU/ANE/GPU inference more practical (anemll, onirenaud).

• Tooling continues to fill in around local runtimes: Ollama v0.33 added one-toggle integration to let Claude Desktop use Ollama as a third-party gateway for cloud and local models (Ollama); OpenCode v2 was shown running inside a Cloudflare Durable Object, illustrating how small agent runtimes are becoming embeddable in edge environments (fayazara).

Models, Retrieval, and Search Infrastructure

• Qwen 3.8 is showing up across the stack: enthusiasm around the Qwen3.8 release was visible in both deployment and evaluation posts, with Together adding fine-tuning and dedicated inference support for Qwen3.8-27B (Together) and Unsloth claiming full QLoRA fine-tuning of the 27B model on free 2× Tesla T4 Kaggle instances using optimized kernels (danielhanchen). On the application side, Qwen3.8-27B reached #1 among open models in the Image-to-WebDev Arena and #7 overall, while priced at $0.40 / $3 per million input/output tokens (arena).

• Search and retrieval infra got multiple substantive updates: Hugging Face published a detailed architecture writeup for the Papers with Code search engine: PostgreSQL + pgvector, Qwen 3 Embedding 0.6B, hybrid retrieval, embeddings generated on an NVIDIA L4 via Hugging Face Jobs, artifacts in buckets, and live serving via Inference Endpoints; the same stack powers “related papers” on paper pages (Niels Rogge). Keenable came out of stealth with a Web Search API and Web Query Language for AI, built by former Yandex Search leaders and backed by a $26M seed, explicitly targeting agent-scale web retrieval (styskin).

• Retrieval model design remains active territory: there was renewed discussion around late interaction / multivector retrieval, with claims that scaling behavior is finally becoming visible in retrieval workloads and that model+DB co-design matters at least as much as storage format (mixedbread perspective, Silvio Martinico).

Robotics, Physical World Models, and Embodied Data

• Figure’s “Index” is a major robotics data announcement: Figure introduced Index, described as the largest and most diverse robot dataset in the world, with reported ingestion at 30 minutes of video uploads per second, 16M video uploads, $15M already paid out for data, and 264k downloads. The company also says it will spend $1B over the next 12 months on data and compute (Brett Adcock, follow-up). That scale matters because many robotics labs still appear more bottlenecked on demonstration and perception data than on architecture novelty.

• Large-scale physics/world modeling continues to push context limits: Anima Anandkumar highlighted Accelerated Understanding, a startup building large AI models for physical simulation across modalities and 4D spacetime, claiming 1T parameters during pretraining, 1T context during training, and >5T context at inference without subsampling or patching (Anima Anandkumar). The details are sparse, but the post is notable as a statement of where some frontier non-language modeling work is heading: massive-context multimodal simulation rather than only text/video generation.

• Embodied policy generalization remains an active benchmark target: a separate robotics post introduced S1, a manipulation model that can complete tasks from a single demonstration outside its training distribution (anag004). Google Research also shared AgentHands, an XR system that augments conversational agents with synchronized hand gestures for spatial guidance during physical tasks (Google Research).

Top tweets (by engagement)

• OpenAI chip launch: @sama on Jalapeño, @OpenAI benchmark announcement drove the largest technical conversation by far.

• Local agent launch: @perplexity_ai launching Portable Computer was the biggest product release outside the chip story.

• Developer platform / agent-native web: @OpenAIDevs announcing the WebMCP Challenge and WebMCP support in ChatGPT desktop signal OpenAI pushing websites toward explicit agent interfaces.

• Open-source local task agents: @AndrewYNg on OpenWorker stood out for combining open harnesses, local models, and security-focused workflows.

• Benchmark realism for coding agents: @EinsiaAI on SWE Refactor Bench is one of the more useful benchmark releases in the set because it targets whole-repo migrations instead of local edits.

AI Reddit Recap

/r/LocalLlama + /r/localLLM Recap

1. Qwen3.8 Flash/27B Benchmarks and Local Fit

Read more