This week Google returned to the frontier. Gemini 4 Argon, its first new flagship since Gemini 3 Pro, became generally available on October 13 at an introductory price of $2 per million input tokens. The price of a capable model fell at the low end too. Anthropic shipped Claude Haiku 5.5 at a tenth of its predecessor's token price. Meta released its first frontier model, OpenAI rebuilt ChatGPT answers around interactive interfaces, and Mistral previewed a trillion-parameter open-weight flagship.
Under the models, the hardware story moved to the rack. At the Open Compute Project Global Summit, NVIDIA, AMD, Microsoft, Intel, and Marvell all showed new chips and open rack designs. Memory stayed the tightest link in the chain.
This issue follows the usual order. Models first, then tooling, then standards, then infrastructure. Each section ends with what the news means for teams building with AI and data.
Models: Google Returns to the Frontier With Gemini 4 Argon
Gemini 4 Argon
Gemini 4 Argon is the lead model story of the week. Google first announced Argon on September 30, but only for trusted cybersecurity partners in its Fairwind Program. On October 13, Google made Argon globally available to developers, enterprises, and paying consumers. It is the first model in the Gemini 4 family.
Access now runs through several doors. Developers can call it in AI Studio and on the Gemini platform under the model ID gemini-4-argon. Google AI Ultra subscribers get it in Google Antigravity, Google's agentic coding environment. Ultra and Pro subscribers get it in the Gemini app and AI Mode in Search. Enterprises get it in Gemini for business.
The price is the surprise. Argon launches at an introductory rate of $2 per million input tokens and $10 per million output tokens, with cached input 95% off. That matches GPT-6.1 Sol. The discount ends on November 30, 2026. After that, Argon costs $4 input and $20 output, the same band as Claude Opus 5.5 and Meta's Muse Wonder. Budget for the higher number, not the launch number.
The token limits stand out. Argon keeps a 1 million token input window. Google also raised the output limit to 1 million tokens, up from 64,000. Google describes this as a unified input-output limit, served through a new continuation protocol for long outputs. Every other model in this issue caps output at 128,000 tokens or less. Long outputs matter for agents that write whole codebases, long reports, or large data transformations in one run.
Google's benchmark claims are vendor-reported, so read them with care. Google says Argon ranks #1 on the Vals Index, which measures performance on finance, coding, legal, and tax work. It reports 87% on the Embodied Reasoning (ERQA) benchmark for physical and spatial reasoning. On the Gray Swan Indirect Prompt Injection benchmark, Google says Argon cut attack success to 0.7% across 15 adaptive attempts. For security work, Google reports that Argon matches GPT-6 Astra on CWE-bench, which measures finding and patching vulnerabilities.
Outside analysts are more measured. Futurum's read is that Argon puts Google level with OpenAI but behind Anthropic. TechTarget noted that Argon is Google's first new top-tier model since Gemini 3 Pro in November 2025, and that its claims still need proof in enterprise settings. Independent results on the full Vals suite and Artificial Analysis should land within days.
Google backed the launch with internal results. Engineering teams using Argon in Antigravity increased agentic code submissions by more than 35% and cut code rollbacks by nearly a third. Given a skills rulebook and a one-paragraph goal, Argon worked overnight on Google's open source Agent Development Kit. Its changes, now merged, cut in-memory session prep time by 40% in long sessions and sped up cold imports by 21%. Google also reports a 2.85x end-to-end inference speedup for Gemma 4 E2B on vLLM, with the work sent upstream as pull requests.
One internal result belongs in the infrastructure conversation. In the September 30 announcement, Google said a team of Argon agents analyzed fleet-wide profiling data and applied memory fixes across its data centers. The changes freed over 300 TiB of memory once rolled out, with 500 TiB to 1 PiB in total savings expected. In a month when memory is the scarcest part in AI hardware, a model that finds memory in existing software is worth noting.
Security shaped the rollout. Argon went to cyber defenders first, the same defender-first pattern Anthropic used with Claude Mythos under Project Glasswing. On October 13, Google began expanding Fairwind to hundreds of additional partners. Google plans to give trusted defenders a version of Argon without cyber guardrails. For the public model, Google says it trained Argon to pause for human confirmation before irreversible steps. It reports that shortcut attempts on coding tasks fell to 2%, and it runs a monitor that reads the agent's reasoning and actions to block unintended workarounds in real time.
What it means for you. For two months, the price matches GPT-6.1 Sol while the claims match the top tier. That makes now a cheap time to run Argon against your own evaluation set. Test the 1 million token output limit if your agents produce long artifacts, since no other frontier model offers it. Plan costs at the post-November rate of $4 and $20. And note where Argon lives. Its best agentic experience runs in Antigravity, which follows this week's pattern of labs keeping their strongest experience inside their own tools.
Claude Haiku 5.5
Anthropic released Claude Haiku 5.5 on October 7, 2026. It completes the Claude 5.5 family alongside Sonnet 5.5 and Opus 5.5. The API model ID is claude-haiku-5-5.
The headline is price. Haiku 5.5 costs $0.10 per million input tokens and $0.50 per million output tokens for prompts up to 100,000 tokens. Haiku 4.5 lists at $1 and $5. That is a 90% cut in the base token price.
The pricing has a second tier. Above 100,000 tokens, the rate rises to $0.50 input and $2.50 output per million tokens. Haiku 5.5 is the only current Claude model priced this way. Sonnet 5.5, Opus 5.5, and Fable 5.1 bill the full window at one rate.
The context window grew five times. Haiku 5.5 takes 1 million tokens of context and returns up to 128,000 output tokens, up from 200,000 and 64,000 on Haiku 4.5. The cheapest Claude model now has the same window as the most expensive one.
Anthropic frames the savings as about 75% per task, not 90%. The gap comes from the tokenizer. Haiku 5.5 uses the tokenizer introduced with Claude 4.7, which produces roughly 30% more tokens for the same input than Haiku 4.5 did. Lower prices per token, more tokens per task.
Haiku 5.5 is also the first Haiku with Anthropic's effort settings and adaptive thinking. That changes the cost math again. Artificial Analysis scored Haiku 5.5 at 43 on its Intelligence Index at maximum effort, ahead of GPT-6 Luna at 38. But Haiku 5.5 produced about 440 million output tokens across the full test suite, against 140 million for Luna. Per test question, that worked out to about $0.21 for Haiku and $0.07 for Luna.
Those are independent numbers, not vendor claims. Artificial Analysis also reported 33% on Terminal-Bench 4.0, up from 0% for Haiku 4.5. It flagged one agent automation result as likely understated and plans to re-run that test.
Anthropic made two related pricing moves the same day. It halved the Sonnet 5.5 cache read price to $0.10 per million tokens and said that makes Sonnet 5.5 about 20% cheaper on most agentic work. It also added monthly API credits to subscriptions. Max 5x and Max 20x plans include $100 and $200 a month in Claude Platform credits, and Team plans get up to $500.
Availability is broad. Haiku 5.5 runs on the Claude API, Amazon Bedrock, Google Cloud, Microsoft Foundry, and Claude Platform on AWS. It also shipped in Claude Code and GitHub Copilot on day one.
Code written for Haiku 4.5 needs updates. Anthropic lists API changes that break older integrations, so test before you swap the model ID in production.
What it means for you. Small models do most of the work in agent systems. They classify, route, extract, summarize, and run as sub-agents under a larger planner. A 90% cut in the base rate makes it cheap to run many more of those calls. Keep prompts under 100,000 tokens where you can, since the price jumps five times above that line. And measure cost per task, not cost per token. The Artificial Analysis data shows a cheap token can still produce an expensive answer if the model thinks at length.
Meta Muse Wonder
Meta's Superintelligence Lab released Muse Wonder and Muse Wonder Full on October 12. TechCrunch called it Meta's first attempt at a frontier model. The earlier Muse Spark models targeted low latency. The Wonder models are larger and aim at coding and long-running agent tasks.
Developers can call Muse Wonder through the Meta Model API as muse-wonder-1.0. It costs $4 per million input tokens and $20 per million output tokens. That puts it in the same price band as GPT-6 Sol and Claude Opus 5.5.
The twist is the second checkpoint. Muse Wonder Full is only available to Muse Code subscribers and will not be served through the API. Both models also power Meta's Muse agent. So the best version of Meta's model lives inside Meta's own coding product.
Both models support a 1 million token context window and accept text, images, video, and audio. Meta stressed a feature it calls active memory, the ability to keep and reuse what a user shares over time.
On benchmarks, treat the numbers as vendor-reported. Meta's model card shows Wonder and Wonder Full scoring comparably to Claude Fable 5.1 and GPT-6 Astra. Wait for independent runs before you rank it.
What it means for you. Meta has moved from open weights to a paid frontier API. That is a strategy change, not just a model release. If your team planned around Meta as the open-weight option, the plan needs a second look. And the split between an API checkpoint and a subscriber-only checkpoint is a pattern to watch. When a lab keeps its best model inside its own app, API builders get the second-best version.
Mistral Large 4 Preview
Mistral opened a public preview of Mistral Large 4 on October 6. The preview runs on Mistral Studio and the Mistral API. Mistral says the open weights will follow by the end of October.
Large 4 is a mixture-of-experts model with 1.05 trillion total parameters. Mistral's launch post lists 49 billion active parameters, while its model page lists 52 billion. It takes text and image input. Mistral trained it from scratch on 3,800 Grace Blackwell GPUs in its own European data centers.
The context window depends on where you look. Mistral advertises 1 million tokens. OpenRouter documents 524,288 tokens. Check the limit on the endpoint you plan to use.
Mistral's coding numbers are vendor-reported. It cites 61.7% on DeepSWE v1.1. In a blind coding-quality evaluation run by Mistral with Surge AI annotators, the preview scored 3.74 out of 5. That placed it second of five, behind Claude Opus 5 at 4.22 and ahead of Kimi K3 at 3.59.
Independent testing gives a more modest picture. Vals.ai ranks Mistral Large 4 at #32 of 44 models on its Vals Index with 48.05%. Its best showing was #6 of 75 on Harvey's Legal Agent Benchmark.
What it means for you. The value of Large 4 is not the leaderboard. It is ownership. If Mistral ships the weights on schedule, teams get a trillion-parameter multimodal model they can run in their own data centers. That matters for regulated industries and for any team with data sovereignty rules. Plan the hardware budget now, since a model this size needs serious memory to serve.
OpenAI: GPT-6 Reaches Every ChatGPT User
OpenAI began rolling out GPT-6 with Intelligent UI across ChatGPT on October 7. Plus, Pro, Business, and Enterprise users got it first. Free and Go users started getting it on October 8.
The model behind it depends on your plan. Paid tiers run on GPT-6 Sol, and Free and Go tiers run on GPT-6 Luna. OpenAI says the release reaches more than 1.2 billion weekly ChatGPT users.
Intelligent UI is the real change. GPT-6 can now answer with graphics, buttons, forms, charts, and small interactive tools inside the chat. A question about splitting a bill can return a working calculator. OpenAI also lets GPT-6 start answering while it keeps thinking. For web search questions, GPT-6 Instant starts answering 44% faster on average than GPT-5.6 Instant, according to OpenAI.
There are limits. Intelligent UI does not work on the Pro reasoning option, which still runs Astra. OpenAI's safety card also notes that Codex and ChatGPT Work keep the September versions of the models.
For API users, the bigger model news came the week before. OpenAI introduced GPT-6.1 Sol at DevDay on September 29 as gpt-6.1-sol, priced at $2 per million input tokens and $10 per million output tokens. OpenAI reports that it matches GPT-6 Astra on DeepSWE v1.1 at roughly one-fifth the cost. This week it became the default in Codex CLI, which we cover in the tooling section.
What it means for you. Generated interfaces are now a mainstream answer format. That raises the bar for every data product. Users will expect a chart or a filter control when they ask a question about numbers, not a paragraph. It also raises a trust question. A generated chart looks authoritative even when the data behind it is wrong. Teams that serve data to AI assistants need clean, governed sources more than ever.
Google: Gemini App Access Shifts
Alongside Argon, Google also changed who gets which model in the Gemini app. Starting October 9, Gemini app users without a subscription get Flash-Lite, not Flash or Gemini Pro. Google AI Plus subscribers keep Flash but lose Gemini Pro on dates sent by email. Pro and Ultra subscribers keep all three.
This is the other side of the price war. Labs cut API prices for developers and tighten free consumer access at the same time. Argon itself is limited to Pro and Ultra subscribers in the Gemini app. Serving frontier models to hundreds of millions of free users costs real money.
Other Releases
Release trackers logged several smaller models this week. LLM Gateway lists Reka Edge 2603 on October 9, GLM 5.3 Fast from Z.AI on October 7, and Microsoft-Decision-1 on October 9. We have not confirmed specs for these against their labs' own announcements, so treat them as leads for your own testing.
Model Quick Reference
All benchmark figures above from Google, Anthropic, Meta, Mistral, and OpenAI are vendor-reported unless the text names an independent source such as Artificial Analysis or Vals.ai.
The Pattern in Models
Three trends stand out this week. First, prices keep falling at both ends. Haiku 5.5 resets the small-model floor, and Argon launches at a mid-tier price for a frontier model, at least until November 30. One million token windows are now standard across price levels, and Argon pushes output to 1 million tokens too. Second, labs are splitting releases into API versions and app-only versions. Meta's Wonder Full, OpenAI's ChatGPT-only Intelligent UI, and Argon's Antigravity experience all keep the best experience inside the lab's own product. Security-sensitive models now launch to defenders first, as Argon did through Fairwind. Third, cost per task matters more than cost per token. Adaptive thinking means two models with the same token price can differ by three times in what a real job costs.
Tooling: Coding Agents Compete on Control, Not Just Smarts
The coding agent race shifted this week. The new features were not about writing better code. They were about controlling agents: which model each one runs, what files and networks it can touch, and how many can work at once without stepping on each other.
Claude Code 2.1.296
Anthropic shipped Claude Code 2.1.296 on October 9. The headline feature is workflow-level model pinning. A new environment variable, CLAUDE_CODE_WORKFLOW_SUBAGENT_MODEL, forces every subagent in a multi-step workflow to run on one chosen model. Before this, each subagent picked its own default.
That sounds small, but it solves a real cost problem. In a long workflow, one subagent quietly running on a premium model can dominate the bill. Pinning gives teams one switch to control spend and keep behavior consistent across runs.
The release notes also add subagent auto-compaction and larger Read support. Subagents can now compact their own context instead of growing until they hit a limit. Admins got a new code key in the Claude apps gateway's managed policies, which applies the same settings as the CLI inside Claude Desktop's Code tab. The earlier 2.1.293 release made Claude Haiku 5.5 the default Haiku model in Claude Code.
Codex CLI 0.162
OpenAI answered within days. Codex CLI 0.162.0 added managed Git worktree tools and pinned tasks in its Command Center. The release before it, 0.161.0, made GPT-6.1 Sol the default model and added terminal MCP sign-in.
Worktrees are the quiet standard of 2026. Each agent gets its own Git worktree, so parallel agents edit separate copies of the repository and never collide. Managed worktrees turn that from a manual setup into a built-in feature.
GitHub Copilot
GitHub's weekly Copilot release notes for October 9 carried the most important security change of the week. Local sandboxing is now generally available in Copilot CLI, the Copilot app, and VS Code sessions that use Agent Host. It limits what agents can reach on your machine: files, networks, and credentials. GitHub includes it with Copilot at no extra cost.
The same release made Claude Haiku 5.5 available to Copilot Pro, Pro+, Max, Business, and Enterprise users. The Copilot app now lets you use one GitHub account for your Copilot license and a different one for your repositories. That fixes a common problem for consultants and anyone with a personal and a work account.
VS Code 1.141 added an Agents window that shows agent sessions side by side in a grid. You can compare results from several agents or follow several tasks at once. A new "Open worktree cleanup" command in chat shows how much disk space inactive session worktrees use and lets you delete them. Anyone who has run a dozen parallel agents knows how fast those copies fill a drive.
GitHub also put computer use into public preview for Copilot CLI and the Copilot app. The agent can now operate desktop applications, not just the terminal and the editor. As of this week, Codex CLI and Claude Code had not shipped an equivalent public feature.
GitHub also cleaned house before these launches. On October 2, it deprecated older models across Copilot Chat, inline edits, ask mode, agent mode, and code completions. If your team pins specific models in Copilot settings or scripts, check that those models still exist. A deprecated model ID fails quietly in some setups and loudly in others.
Cursor
Cursor kept pace on mobile. Its iOS app now has Remote Control for local agents, per its October 6 changelog. You can start and steer an agent running on your desktop from your phone. Its /best-of-n command runs several candidate solutions in separate worktrees so you can pick the best one.
The same article makes a useful observation. By October 2026, nearly every coding tool runs several agents at once, each in its own Git worktree. Cursor, the Copilot app, Claude Code desktop, Codex, Zed, and Warp all do it. Parallel agents are no longer a differentiator. They are table stakes.
ChatGPT Moves From GPTs to Plugins
OpenAI plans to retire custom GPTs across ChatGPT plans and provide a migration path to plugins. Only Enterprise has firm dates so far. No new GPTs can be created after October 26, and retirement follows on December 11. If your organization built internal GPTs, start the migration plan now.
Open Source Projects Set AI Rules
The tooling story is not only about vendors. Open source projects are writing rules for how AI tools fit into their work. This week Andy Grove proposed updated AI guidance for Apache DataFusion Comet contributors. Automated reviews are welcome. But every pull request approval must come from a human, with or without AI help.
On the Apache Polaris list, contributors debated using AI to write release notes instead of maintaining a changelog by hand. They chose to tighten the human guidance first and keep AI summaries as a later option. The theme is the same in both projects. AI can do the work, but a named person signs off.
What it means for you. Three practical moves follow from this week. Turn on sandboxing for any agent that runs on a developer laptop, now that GitHub ships it free. Pin subagent models in long workflows so one step does not quietly drive up cost. And write a short AI policy for your repositories. The Comet rule, human approval on every merge, is a good starting point that any team can adopt today.
Standards: MCP Grows Up While Agent Identity Stays Split
MCP After the Stateless Revision
The Model Context Protocol is in its first full quarter on the stateless specification. The 2026-07-28 revision removed the initialize handshake and session tracking. Each request now declares its protocol version in metadata and in an MCP-Protocol-Version HTTP header. Any server instance behind a plain load balancer can answer any request.
That change is now showing up in production behavior. The MCP Dev Summit in Toronto on October 5 and 6 focused on the work of running MCP in regulated environments. The agenda covered identity, authorization, audit, gateways, registries, evaluation, and reliability. One preview of the event reported 70 speakers across six tracks and more than fifty sessions.
MCP is now hosted by the Linux Foundation's Agentic AI Foundation and supported by OpenAI, Google, and Microsoft. The question is no longer whether MCP wins. The question is how teams secure and govern it.
Security Products Arrive
The security market noticed. On October 14, Radware announced MCP Server Protection, a product built to defend MCP servers against protocol abuse, authentication attacks, tool enumeration, tool flooding, and denial of service. The release cites a Stacklok survey in which nearly half of software companies reported using MCP in production, with 19% reporting broad production use.
A dedicated security product is a maturity signal. Web APIs got API gateways and web application firewalls once they carried real business traffic. MCP is reaching that stage now.
Hiring data tells the same story. API Evangelist counted job postings and found 102 companies naming the Model Context Protocol, against 99 naming OpenAPI. The author is careful to say this measures hiring intent, not production use. Still, a protocol less than two years old now appears in as many job posts as the API description standard that has defined web APIs for a decade.
A2A and the Agent Stack
MCP connects agents to tools. Agent2Agent (A2A) connects agents to each other. Google transferred A2A to the Agentic AI Foundation on August 20, placing it beside MCP under one neutral home. The foundation has grown to more than 250 member organizations.
The next big gathering is close. AGNTCon + MCPCon North America runs October 22 and 23 in San Jose. It is the foundation's flagship event, and specification announcements often cluster around it. Expect news on MCP, A2A, goose, and AGENTS.md there.
Agent Identity Remains Unsettled
One gap stands out. There is still no agreed standard for agent identity and authorization. A recent analysis found that the IETF has no adopted working group for agent identity, only a crowd of competing individual drafts. One of those drafts, on agent-native OAuth challenges, expired on October 5.
Drafts keep coming. The OpenA2A Agent Authorization Protocol draft defines agent identity tokens, scoped capability grants, cross-agent delegation, and revocation. It argues that OAuth 2.0, SAML, and OpenID Connect were not designed for agents. Other drafts make similar arguments with different designs. Until one wins, every vendor ships its own approach.
Generated Interfaces Need a Standard Too
OpenAI's Intelligent UI raises a standards question. MCP already has an answer in its ecosystem. MCP Apps is an official extension that standardizes how MCP servers deliver interactive interfaces such as dashboards, forms, and charts to host applications. Intelligent UI is a model-generated interface inside one product. MCP Apps is a server-delivered interface that works across hosts. Both will matter. Teams building data tools should know the difference before they pick a path.
Standards at the Data Layer
Some of the most useful standards work this week happened in the data layer, where agents get their facts. Apache Ossie, the open semantic interchange specification, debated whether to ship an MCP server and where it belongs. The emerging answer is to keep a small shared contract in the spec, a declarative query shape plus standard error codes, and let engines and catalogs run the servers. One contributor already built a ClickHouse executor against that contract and reported which error codes it supports.
Apache Iceberg passed a vote to recommend a standard User-Agent format for REST catalog clients, with 19 votes in favor and none against. Iceberg contributors also agreed to add a none value to the access delegation header, so a client can say it brings its own storage credentials. These are small rules. They are exactly the kind of rules agents need, because an agent cannot ask a human which credential path a catalog expects.
What it means for you. Treat MCP like any production API. Put it behind a gateway, log every tool call, and scope credentials tightly. Do not wait for an agent identity standard before you build controls. Use short-lived credentials and per-agent scopes with the auth tools you already have. And if your agents query business data, give them a semantic layer and a catalog with clear contracts, not raw tables.
Infrastructure: The Rack Becomes the Product
The OCP Global Summit ran October 12 to 15 in San Jose. It is where hyperscalers and chipmakers publish the hardware designs that data centers build from. This year the message was clear. The unit of AI compute is no longer the chip. It is the rack, and everyone wants their rack design to become the standard.
NVIDIA Opens Vera Rubin
NVIDIA contributed its Vera Rubin rack and compute tray designs to OCP through its MGX architecture. That lets system builders such as Foxconn, Quanta, Wiwynn, and Supermicro build compatible racks faster.
The new MGX 1.2 spec supports racks up to 250 kW. It adds native 19-inch equipment support, configurable I/O bays, and fanless liquid-cooled compute trays. NVIDIA also released four open source components for its DSX AI Factory software for configuration, cluster readiness, rack management, and cluster provisioning.
NVIDIA joined AMD, Google, Meta, and Microsoft to publish the Open Data Center Specification v0.7 and an OCP Grid Resilience Specification. With Cisco, it is developing the Ultra-Dense Small Form Factor Pluggable optical module, which targets four times the bandwidth density in a similar footprint.
For context, each Rubin GPU carries 288 GB of HBM4 at 22 TB/s of bandwidth, and a Vera Rubin NVL72 rack holds 72 GPUs and 36 Vera CPUs. A 250 kW rack is roughly the power draw of a small office building, packed into one cabinet.
Microsoft Maia 300
Microsoft unveiled its Azure Maia 300 AI chip at OCP on October 12. Microsoft says it delivers 40% more tokens per megawatt than leading GPU-based systems. A 96-chip rack offers seven times the rack-scale token throughput of Maia 200.
Note the metric. Microsoft did not lead with FLOPS. It led with tokens per megawatt. Power, not chips, is now the binding limit for many data centers, so the useful measure is how much work each watt buys. Maia 200 already runs Microsoft 365 Copilot and OpenAI models in production, so Maia 300 has a real workload waiting.
AMD Helion and the CPU Comeback
AMD introduced Helion on October 12, an open rack blueprint built on an OCP spec design and aimed at AI agent workloads. One example configuration is a CPU-only rack with up to 32,768 Zen 6 cores. AMD plans to contribute the spec to OCP, and partner configurations from Cisco, Dell, Hon Hai, and HPE are slated for November 2026.
Why a CPU rack for AI? Agents do a lot of work that is not matrix math. They call tools, run code, parse documents, query databases, and wait on network calls. That work runs on CPUs. As agent systems grow, CPU capacity becomes as important as GPU capacity.
Lisa Su also showed a 6th Gen EPYC chip codenamed Verano, which AMD describes as the first EPYC CPU with an LPDDR memory interface. It arrives in 2027. LPDDR trades some serviceability and maximum capacity for better bandwidth per watt.
Intel Bets on LPDDR5X Instead of HBM
Intel detailed its GPU D-series, formerly code-named Crescent Island. It pairs up to 480 GB of LPDDR5X memory with 1.5 TB/s of bandwidth and 1.3 petaflops of FP8 compute in a 350-watt envelope. Intel says one card supports models with up to 300 billion parameters. Customer sampling is underway, with no price or ship date announced.
The memory choice is the story. Intel skipped HBM entirely. LPDDR5X has far less bandwidth than HBM4, but it costs less, uses less power, and is not sold out. For inference on large models, capacity often matters more than peak bandwidth.
Marvell and CXL Memory
Marvell showed its Structera CXL memory expansion line, Teralynx T100 102.4T switch, and 1.6T optics at OCP. Coverage of the summit reported that Marvell's new CXL chip supports up to 9 TB of memory. CXL lets servers attach large pools of memory over a standard interconnect, another way around the HBM shortage.
The HBM Squeeze
All of these memory choices trace back to one shortage. HBM4 contract prices jumped 117% week over week in early October, according to the Korea Economic Daily. Mass production only started ramping in the second quarter of 2026, just as NVIDIA's Vera Rubin and AMD's Instinct MI455 began drawing on the same suppliers.
AMD moved to lock in supply. After Lisa Su met Samsung executives in Seoul on October 7, AMD and Samsung signed a three-year memorandum covering HBM4, advanced DDR5, joint memory development, advanced packaging, and possible future foundry work. AMD's MI455 ships with 432 GB of HBM4 on board.
The shortage reaches beyond data centers. A roundup of October 12 news noted that Counterpoint estimated smartphone shipments fell 20% in Q3 as memory shortages constrained supply. The same day, parts of FERC's order on large loads such as data centers took effect, including a large load definition and registry.
Formats Are Infrastructure Too
Hardware is only half of the cost story. The other half is how data is stored and moved. This week the Apache Parquet community merged the C++ implementation of ALP encoding for floating-point data. Floating-point columns are everywhere in AI: embeddings, model features, sensor readings. Better compression on those columns means less storage, less I/O, and less memory per query.
Parquet contributors also debated a native vector type. One side wants a simple fixed-length VECTOR type now. The other side argues the real gains come from quantized vectors, where storage and speed improve by orders of magnitude. Apache Iceberg is designing its own vector type on top of the Parquet work. And Apache Arrow shipped release 26.0.0, the in-memory format that moves data between engines without conversion.
What it means for you. Memory is the constraint to plan around for the next year. If you buy or rent GPU capacity, expect HBM-heavy instances to stay scarce and pricey. Look at LPDDR and CXL-based options for inference workloads that need capacity more than bandwidth. And do not overlook the cheapest fix. Compressing and organizing your data well cuts memory and I/O on every query, no new hardware required.
The Data Layer: Where Agents Get Their Facts
Every story this week ends at the same place. Cheaper models, generated interfaces, and agent fleets all need trustworthy data to work with.
Look at the model news. Haiku 5.5 makes it cheap to run thousands of small agent calls. Each of those calls needs context: a table, a metric, a document. If the context is wrong, a cheap model produces a cheap wrong answer at scale. GPT-6's Intelligent UI turns answers into charts. A chart built on a bad join looks just as convincing as one built on a good one.
The open lakehouse is building for this. Apache Iceberg voted this week to add a File type to its v4 spec. A file column stores a URI, offset, size, content type, and checksum for each referenced object. That lets a table track the PDFs, images, and audio that AI pipelines process, with the same metadata and governance Iceberg uses for rows. Iceberg also passed a rule that snapshot timestamps must always increase in v4, which fixes time travel queries when writer clocks drift. When an agent asks what the data looked like last Tuesday, it gets the right answer.
Apache Polaris, the open catalog for Iceberg, discussed exposing table labels to engines as a view over its tag system. Labels carry classifications such as personal data or confidential. Callers only see the labels they already have permission to see. That is the kind of control an agent needs before it reads a table.
Apache Ossie is the layer that gives agents shared meaning. It defines metrics, dimensions, and relationships once so every tool reads them the same way. This week a contributor tested a simple sum metric through 14 converters. Eight preserved the standard SQL expression. Only one preserved Ossie's own portable dialect. That honest measurement is exactly what a young standard needs. It shows where the gaps are before agents depend on them.
The takeaway is simple. Open formats, open catalogs, and open semantic definitions are not side projects to AI. They are the foundation that makes cheap, fast models safe to use on business data.
The Week in Numbers
- 1 million. Gemini 4 Argon's output token limit, up from 64,000.
- $2 and $10. Argon's introductory price per million input and output tokens, rising to $4 and $20 after November 30.
- 300 TiB. Memory Google says Argon agents freed across its data centers.
- 90%. The cut in Claude Haiku 5.5's base token price compared with Haiku 4.5.
- 75%. Anthropic's estimate of the average per-task savings, once the new tokenizer's extra tokens are counted.
- 30%. How many more tokens the Claude 4.7 tokenizer produces for the same input than Haiku 4.5's tokenizer did.
- 440 million vs. 140 million. Output tokens Haiku 5.5 and GPT-6 Luna each used to finish the Artificial Analysis test suite.
- 1.2 billion. Weekly ChatGPT users OpenAI says now get GPT-6.
- 44%. How much sooner GPT-6 Instant starts answering web search questions than GPT-5.6 Instant, per OpenAI.
- 1.05 trillion. Total parameters in Mistral Large 4.
- 3,800. Grace Blackwell GPUs Mistral used to train Large 4.
- 250 kW. Maximum rack power in NVIDIA's MGX 1.2 spec for Vera Rubin.
- 40%. More tokens per megawatt Microsoft claims for Maia 300 over leading GPU systems.
- 32,768. Zen 6 cores in AMD's CPU-only Helion rack configuration.
- 480 GB. LPDDR5X memory on Intel's GPU D-series partner cards.
- 117%. The week-over-week jump in HBM4 contract prices reported in early October.
- 102 vs. 99. Companies naming MCP and OpenAPI in job postings in API Evangelist's count.
- 19 to 0. The Apache Iceberg vote on a standard REST client User-Agent format.
Read together, these numbers tell one story. Model prices are falling fast while memory prices are rising fast. The labs can only keep cutting prices if hardware gets more work out of each watt and each gigabyte. That is why this week's OCP news centered on power, memory, and open rack designs rather than raw chip speed.
Practitioner Takeaways
- Test Gemini 4 Argon now. The introductory price runs through November 30. Run it on your own evaluations, but budget at the $4 and $20 rate.
- Re-run your model cost math. Haiku 5.5 at $0.10 per million input tokens changes which tasks are worth automating. Measure cost per completed task, since thinking tokens can triple the bill.
- Watch the 100,000-token line. Haiku 5.5 charges five times more above it. Trim context or split long jobs where you can.
- Turn on agent sandboxing. GitHub now includes local sandboxing with Copilot. Use it, or an equivalent, on every developer machine that runs agents.
- Pin models in long workflows. Claude Code's new workflow pinning keeps every subagent on one model. That keeps cost and behavior predictable.
- Plan the GPTs migration. Enterprise ChatGPT users cannot create new custom GPTs after October 26. Start moving to plugins.
- Secure MCP like an API. Gateways, logs, and scoped credentials. Dedicated MCP security products are now on the market.
- Budget for memory, not just compute. HBM4 prices jumped sharply this month. Consider LPDDR and CXL options for capacity-heavy inference.
- Give agents governed data. Use an open catalog with clear access rules and a semantic layer with shared metric definitions.
What to Watch Next Week
AGNTCon + MCPCon North America opens in San Jose on October 22. Expect MCP and A2A specification news, new members for the Agentic AI Foundation, and security tooling launches. Mistral's promised open weights for Large 4 are due by the end of October, so watch for the download and the license terms. Independent benchmarks for Gemini 4 Argon and Meta's Muse Wonder should start appearing, and Google says more Gemini 4 models are coming. The OCP summit wraps up October 15, and more rack and memory details will trickle out after it. On the open data side, the Iceberg File type vote closes, and the Parquet vector type debate continues.
Keep Learning
The AI and data world moves fast, and a weekly newsletter only scratches the surface. I have written more than 50 books on AI-assisted development, agentic AI, the open lakehouse, Apache Iceberg, and data engineering. They cover the tools and ideas in this newsletter in depth, with hands-on examples.
Browse the full catalog at books.alexmerced.com and pick the book that fits what you are building next.
Top comments (0)