Welcome to Blank Metal’s Weekly AI Headlines.
Each week, our team shares the AI stories that caught our attention: the articles, announcements, and insights we’re actually discussing internally. We curate the best of what we’re reading and add the context that matters: what happened, why it matters, and what to do about it.
The Model Is Now a Line Item on Your Cloud Bill
The economics of the model layer moved this week. The frontier labs are selling through the clouds you already pay, OpenAI priced a decision model at ten cents per million input tokens, the company behind the newest consumer agent told investors it is too compute-intensive to launch globally yet, and a research team cut agent token use by a third to a half by letting agents reason outside of language. Together they describe a market where the model is becoming a procurement question and compute is constraining vendor roadmaps.
OpenAI and Anthropic Models Move Onto Your Google Cloud Commitment
What: On October 21, OpenAI and Google Cloud announced that OpenAI’s frontier models and Codex agentic workflows are coming to Google Cloud’s Model Garden. Customers will buy them through the Google Cloud Marketplace, and enterprises with Google Cloud spend commitments can draw down those commitments to pay for them. OpenAI models will also appear in Google Antigravity and the Gemini Agent. General availability is planned “in the coming weeks,” and OpenAI said Microsoft remains its primary cloud partner. Google said it is now the only hyperscale cloud provider offering Gemini, Claude, and GPT on one platform. One day later, on October 22, Anthropic made Claude Models on Google Cloud (Anthropic managed) generally available. That offering gives Google Cloud customers the full Claude Platform, including Managed Agents in beta, code execution, and the MCP connector, all under Google Cloud IAM credentials, on a single Google Cloud invoice, drawing down the existing commitment. Anthropic says new features ship there the same day they reach its own platform. Anthropic is the data processor on that offering; Google’s own managed Claude offering remains for customers who need Google as the processor, strict regional data residency, or Google-native controls such as Model Armor. The Anthropic-managed offering runs on US and Global endpoints today.
So What: The cloud commitment is becoming how enterprises pay for frontier models. You will soon be able to fund OpenAI, Anthropic, and Google models from one prepaid pool on one invoice, which removes the budget argument that used to decide which lab a team was allowed to use. What remains is a per-workload question: who processes your data, where does the endpoint live, and how fast do you need new features. For Claude on Google Cloud, that choice is now explicit: Anthropic or Google as the data processor.
Now What: If you hold a Google Cloud commitment, inventory the model spend that currently sits outside it, on direct API contracts and personal cards, and ask your account team what can move under the commit. For each workload, pick the offering by data-processor and residency requirement first and feature velocity second. And ask about discounts before you migrate anything; Anthropic says discounts cannot be applied retroactively to usage.
OpenAI’s Decisions API Goes Live at Ten Cents per Million Tokens
What: On October 22, OpenAI made the Decisions API generally available. It runs GPT-6 Luna against questions with bounded answers and returns one of three result types: a probability that a condition is true, a choice from options you supply (with confidence), or a score against a rubric. OpenAI says it answers up to 10 times faster than Luna through the standard Responses API, accepts text, images, and native JSON, and takes up to 400 questions per request. It costs $0.10 per million input tokens, $0.01 for cached input, with no output-token charge, and offers US and EU residency and zero data retention for eligible customers. Customer numbers in the announcement: Box saw about 5 times faster document routing with the same accuracy, Datadog measured a 40 times faster p95 when scoring the risk of agent-generated shell commands, Ramp attributed AI costs 4 times faster and 30% cheaper, Sierra runs it under 280 milliseconds p95 at 90% lower cost per call, and Speak cut time-to-next-action in its language tutor from 1.4 seconds to 0.13. TechCrunch reported the launch as OpenAI’s answer to TypeSafe’s Jev, which TechCrunch credits with creating the “decision model” category; TechCrunch says TypeSafe is now valued at $7.6 billion, and noted that public decision indices currently rank several rivals ahead of OpenAI’s entry.
So What: Most of what an agent does all day is small and bounded: classify this, route that, decide whether to continue. Sending those through a frontier model is why agent bills surprise people. A purpose-built decision tier at ten cents per million input tokens, with no output charge and a confidence number attached, changes the unit economics of the whole pipeline, and the confidence number matters most. It gives you a clean rule for which decisions a person should look at.
Now What: If you run agents or classification pipelines, list the three bounded decisions they make most often and test them against a decision model with a few hundred of your own labeled examples. Measure accuracy, p95 latency, and cost per thousand decisions side by side with what you do today. Then set a confidence threshold below which the decision goes to a reviewer, and track how often that happens.
Meta Spent $34.9 Billion on Capex in a Quarter and Still Can’t Run Muse Everywhere
What: Meta reported third-quarter results on October 21. Revenue rose 26% to $64.6 billion, above expectations, and the company guided fourth-quarter revenue to $73 billion to $76 billion. Net income was $9.9 billion. A $10 billion charge for a settlement with state attorneys general over youth safety cut operating income to $13 billion, down 37% from a year ago. Capital expenditures were $34.9 billion for the quarter, up from $19.4 billion a year earlier, and Meta narrowed its full-year capex guidance to $135 billion to $145 billion. Free cash flow was negative $2.1 billion. Meta also created a new non-voting Class C share class to help fund the AI buildout, pay stock compensation, and fund acquisitions. On the call, Mark Zuckerberg said more than 10 million people in the US and Canada had set up the Muse assistant, that “because this is a compute-intensive service to run, we have not launched it globally yet,” and that Meta would work on monetizing Muse sooner than its usual billion-user playbook. He added that “it’s going to be very important to get the math on all of this to work out.” Fortune cited Visible Alpha estimates that tech infrastructure capex will reach about $790 billion in 2026 and $1.2 trillion in 2027.
So What: Read this as a capacity signal from your vendors’ side of the table. A company spending $35 billion a quarter on infrastructure cannot yet run its flagship agent for everyone, which suggests compute is constraining the roadmaps of the labs you buy from, too. That is why you see speed tiers, usage caps, waitlists, and regional rollouts across the industry. Expect those to persist. The other signal is monetization pressure: a consumer agent that costs this much to run will carry ads or fees sooner than past products did.
Now What: If you depend on a frontier vendor for latency-sensitive work, negotiate committed capacity and rate limits in the contract rather than assuming the public tier will hold. Budget for token prices to keep falling while availability stays lumpy; that combination favors workloads you can batch and schedule. And if a consumer agent is becoming part of how your customers reach you, expect the economics of that channel to change within a year.
Stanford and Together AI Let Agents Think Outside of Language and Cut Token Use by a Third to a Half
What: On October 13, researchers from Stanford, the University of Illinois, and Together AI published Hybrid Reasoning Agents, a 45-page paper and open code base. Most agents today reason and act in text, spelling out each intermediate thought as tokens. The paper’s agents switch between two modes inside a single generation: latent reasoning, in which the model passes its internal states forward without writing words, and text, which it uses when it needs to call a tool or communicate. A small adapter the authors call HybridLink handles the transitions, a continuous working memory carries context across turns, and two training stages teach the model when to think silently and when to act in text. Tested at three model sizes across 11 benchmarks spanning mathematics, science, medicine, search, and agentic tasks, the hybrid agents improved average performance by 10.4% over text-based and latent baselines while using 35.5% to 54.7% fewer tokens, running 1.8 to 2.6 times faster, and costing 2.7 to 3.7 times less. The authors say the latent thoughts remain directly inspectable, and the code and data are public on GitHub.
So What: If much of an agent’s cost is the tokens it spends writing out its reasoning, a method that cuts total tokens by a third to a half while scoring higher goes straight at that bill. The trade is transparency. Many teams audit an agent by reading its chain of thought, and latent reasoning hands you internal states to inspect in place of sentences. The authors say those states remain directly inspectable; whether that holds up in a production audit is still unproven.
Now What: This is research on open models up to 14 billion parameters, so there is nothing to buy yet. Check what your agent audit trail records today. If it depends on reading the model’s reasoning text, add the record that holds up under any reasoning format: what the agent read, which tools it called, and what it changed. Then ask your model vendors whether latent reasoning is on their roadmap and what trace they will provide with it.
Agents Report for Work
Agents are moving from a chat window into the organization: a personal agent that holds standing access to your work accounts, two whole-company rollouts measured in hundreds of thousands of seats, a diagnostic system that outscored physicians on hard cases, and a code reviewer that is now a line item. Each one arrives with a governance decision attached, and the decision belongs to the buyer.
Claude Duet Is a Personal Agent That Works Between Your Sessions
What: On October 21, Anthropic opened a research preview of Claude Duet, a standalone app in which Claude works as a proactive agent for professionals and small business owners. It is built on Claude Opus 5.5 and is available by waitlist to Pro and Max subscribers in the US, on iOS, Android, and claude.ai, with no separate charge and shared usage limits. Duet sends a morning brief across connected apps, checks those accounts every few hours and messages you only when something needs attention, and takes on tasks such as scheduling meetings, building dashboards, financial and sales forecasts, prototypes, and web apps. It runs in its own virtual machine with its own browser, so your laptop does not need to be on. Before it sends a message, makes a payment, signs a document, or deletes anything, it shows you what it is about to do and waits for approval; trading securities and moving money between accounts are off limits even with approval. It connects to more than 6,000 connectors and plugins, including Gmail, Slack, QuickBooks, Stripe, Gusto, HubSpot, and Shopify. A classifier rejects card numbers and government IDs in outbound messages, and health and personal-finance data pass only when the user explicitly instructs it. Anthropic lists limitations: it may misjudge urgency, personal errands such as booking tickets are weaker, and it cannot yet show you its browser. CNBC framed the launch against Meta’s Muse, which Meta says more than 10 million people have set up, and OpenAI’s Dots.
So What: Duet joins Meta’s Muse and OpenAI’s Dots, and the form factor is now clear: an agent with standing credentials to your work accounts that acts while you are away. For a company, that is an employee-held agent connected to Gmail, Slack, QuickBooks, and Stripe, running on a personal subscription. The approval-gated action list (send, pay, sign, delete) is the list your IT and finance teams need to see before anyone connects a company account.
Now What: Decide this quarter whether employees on personal Pro or Max plans may connect company systems to a proactive agent, and publish a connector allowlist either way. Write your own agent policy around those four gates and hold every vendor in this category to it. When enterprise versions arrive, evaluate admin controls before price.
Volkswagen Put 330,000 Employees on Copilot, and Uber Put All 30,000 on ChatGPT Work
What: On October 21, Microsoft said Volkswagen Group has equipped more than 330,000 employees with Microsoft Copilot. The rollout was phased: it began with Copilot Chat, where Volkswagen saw upwards of 300,000 monthly active users, and employees across engineering, production, procurement, and sales now use Copilot with Work IQ. More than 26,000 agents have been active across the group in the past month, and the companies intend to expand Volkswagen’s Intelligent Data Foundation on Microsoft Fabric. Microsoft published no productivity figures. On October 22, TechCrunch reported that Uber has put all 30,000 employees on ChatGPT Work after a pilot with 1,000 people, most of them outside engineering. Uber cited analyzing operations data to find trends, localizing training materials across markets, and building personal interactive dashboards, and said it will track how employees use the tool and which workflows they build before deciding how to deploy AI across the business.
So What: The deployment unit is now the whole company. Volkswagen’s rollout ran in two phases: chat for everyone, then agents. Uber went from a 1,000-person pilot to the whole company and says it will watch usage before deciding what comes next. Twenty-six thousand active agents at one company is a governance problem at a scale most registries were not built for. Neither announcement includes outcome numbers, and Uber says it is tracking usage and workflows first.
Now What: If you’re planning a company-wide rollout, design for both phases from the start, and instrument usage and workflow data from day one, because that is the evidence you will be asked for in two quarters. Stand up an agent registry with an owner and a scope for each agent before the count reaches four digits. And write down now what evidence of value you will accept, so the review is not an argument about anecdotes.
Microsoft’s Diagnostic Orchestrator Outscored Physicians on Hard Cases, Mostly Thanks to the Models Underneath
What: On October 22, Microsoft AI published results in Science for MAI-DxO, its diagnostic orchestrator. The system works like a panel of virtual physicians: several agents propose diagnoses, choose which questions or tests to request next, challenge each other across rounds of debate, and weigh each test’s likely value against its cost. On the Sequential Diagnosis Benchmark, built from 304 complex New England Journal of Medicine cases plus typical emergency-department presentations, MAI-DxO reached 83% accuracy on the NEJM cases against 36% for physicians working with reference materials and 22% without. On the emergency cases it scored 80% against 47%. Microsoft says a cost-optimized configuration reached 81% at less than half the cost of comparable systems, and that the gains held when it reran the evaluation with newer models including GPT-5.5. TechCrunch’s reading of the data adds the caveats: the physicians were generalists working alone, while cases this complex are usually handled by specialists and teams; GPT-5 alone scored 78.9% on the complex cases at an estimated $8,400 per case, and the orchestration added about four points while cutting cost by roughly $3,000; and the orchestration added little on emergency cases with the newest model. Microsoft open-sourced the benchmark, announced a prospective study with Beth Israel Deaconess Medical Center in which patients will interact with the system directly, and said it is building a healthcare foundation model with Mayo Clinic.
So What: For anyone deploying AI in clinical settings, on TechCrunch’s numbers most of the accuracy came from the base model and the orchestration’s value is cost control and an auditable reasoning trail. That is still valuable: a system that reaches similar accuracy while ordering fewer tests is a different product than one that only answers better. The panel-and-debate pattern also transfers to any high-stakes decision where you want the reasoning visible, including underwriting, claims, and compliance review.
Now What: If you’re evaluating clinical decision support, ask vendors for accuracy and cost per case together, and ask who the comparison group was. Treat NEJM-style benchmarks as the entry ticket and the prospective study as the result that matters; Beth Israel’s is the one to watch. And if you run high-stakes decisions outside healthcare, pilot the panel pattern on one workflow where a visible reasoning trail would satisfy your auditors.
Code Review for Claude Code Is Generally Available, With a Published Playbook for Reviewing Agent-Written Code
What: On October 15, Anthropic moved Code Review out of research preview and into general availability for Claude Team and Enterprise plans. Reviews now finish about 3 times faster than in preview, roughly 6 to 10 minutes down from 20, and admins can set each repository to Quick, Standard, or Deep. Eligible Enterprise organizations can claim at least $10,000 in Code Review credits through January 15, 2027. During the preview Anthropic priced reviews at $15 to $25 each, billed on token usage and scaling with the size of the pull request; GA pricing was not in the announcement. The same day, the Claude Code team published how it reviews its own code. The team says Claude writes about 90% of Claude Code’s code. By its numbers, from June to September, merged pull requests more than doubled while the share that had to be reverted fell by more than 40%. The share of internal pull requests receiving substantive review comments rose from 16% to 54% after automated review launched. Human approval runs in three tiers set by a classifier on the change itself: low-risk changes need no human once automated review and security checks pass, medium needs one person, high needs two, and an agent’s approval never counts as a person’s. After three review rounds, the reviewer asks the author to reconsider the approach; mean reviews to pass fell from 2.08 to 1.32.
So What: Last week’s story was Anthropic replacing its source control because agent-written code overran it. This is the next bottleneck in the same chain, and the policy is the part to copy: a risk tier set by the change, a hard rule that agent approval is never human approval, and a convergence rule that stops review loops. Those three rules work with any reviewer, and they are the answers your auditors will eventually ask for. Review is also now a per-pull-request cost, which is a new line in the engineering budget.
Now What: If agent-written code is a growing share of what your team merges, write the three-tier approval policy this month and decide which repositories get a deep review by default. Add a convergence rule so a pull request cannot loop indefinitely between an author agent and a reviewer agent. And model review cost per pull request against your merge volume before you turn it on everywhere.
Agents Get Plumbing
The infrastructure under agents is taking shape: a compute class built for them, a security model that treats them as insiders, and a standards body that now holds the interfaces they use. All three put the controls outside the model, give every agent an identity, and assume it will sometimes do the wrong thing.
Google Gives Agents Their Own Compute Class and Puts Token Budgets at the Gateway
What: On October 22, at AGNTCon and MCPCon, Google Cloud introduced Agent Compute Engine, a purpose-built compute service that Google says already runs Gemini’s agent for work tasks, with a customer preview planned “in the coming months.” Each agent gets a hardware-isolated microVM with its own guest kernel, its own cryptographically verified identity, short-lived credentials, and its own persistent disk. Idle agents are paused through checkpoint and restore while they wait on a person or an external system, memory is shared copy-on-write across agents on one template, and service credentials are injected at egress, outside the microVM. Google also open-sourced Agent Substrate on GKE, which it says delivers up to 10 times the compute density of traditional compute and handled 500 activations per second with under 500 milliseconds suspend-and-resume latency in a 200,000-agent benchmark; it works with any harness, including Claude Code. On governance, Google said Agent Gateway will add granular token and cost controls, model routing policies, and delegated user authorization with Ping Identity, SailPoint, and Saviynt this quarter in preview, and that governance for local agents such as Claude Code and the Antigravity CLI on managed devices is coming to preview soon. L’Oreal was named as a customer of the governance stack.
So What: Agents are getting a compute class the way containers did, and the details are the lesson: identity per agent, credentials that never sit inside the sandbox, and a pause state for the hours an agent spends waiting on a human. Those are the properties your security team will ask for whether or not you buy them from Google. The gateway additions matter for finance: a token budget enforced per agent puts cost control inside the platform.
Now What: If you build on Google Cloud, put Agent Compute Engine on your evaluation list and ask for the preview. On any cloud, write the three properties above into your agent platform requirements and ask your current vendor how it meets each one. And plan to meter agents individually; the gateway is where the per-agent token budget will live, so decide now who sets it.
Microsoft Treats Every Agent as an Insider and Dials Its Access Up and Down in Real Time
What: On October 19, Microsoft announced new agent security capabilities across Entra, Defender, and Project Perception, framed as “agents are your newest insiders.” Dynamic Agent Risk combines signals from identity, data, endpoints, cloud, network, runtime, and the agent’s own activity into a continuously updated risk level. Dynamic Conditional Access responds in gradations: reduce permissions, keep reads while blocking writes, narrow data and resources, restrict network paths, shorten or revoke time-bound access, require provable human approval before a consequential action, and at the highest risk isolate the runtime or stop execution. Dynamic Permissions start every agent with no authority and grant task-scoped, time-bound access. Project Perception gains Playbooks and a team of Guardian Agents that investigate why an agent’s risk changed and act to contain it. Defender’s discovery of agents running on employee machines expands from 25 to 60 types, including Claude Code, OpenAI Codex, and GitHub Copilot. GeekWire reported the features are in private preview with broader availability planned for Ignite in mid-November, and that they are part of Microsoft 365 E7, the $99 per user per month tier. Microsoft tied the design to Satya Nadella’s recent argument that the most trustworthy agentic system is the one designed to trust the model least.
So What: The control plane for agents is being built outside the model, in identity and conditional access, which is the same conclusion Google reached this week from the compute side. The insider framing helps right away: you already have an insider-risk program with owners, scopes, and graduated responses, and agents map onto it directly. A “read-only mode” for a misbehaving agent is a far better first response than a kill switch, because it keeps the work visible while the risk is investigated.
Now What: Extend your insider-risk program to agents this quarter: every agent gets an owner, a stated purpose, and a scope, and discovery of agents on endpoints runs now rather than after an incident. Define graduated responses and test that your platform can actually demote an agent to read-only. If you’re on E5, price E7 against point tools for agent identity and discovery before Ignite, when broader availability arrives.
The Linux Foundation Now Holds Agent Skills, Open Responses, OpenEnv, and OpenSandbox
What: On October 22, the Agentic AI Foundation under the Linux Foundation announced four new projects. Anthropic donated Agent Skills, the open standard for packaging specialized knowledge and workflows for agents; OpenAI donated Open Responses, an open specification for multi-provider LLM interfaces based on its Responses API; Hugging Face donated OpenEnv, a framework for reinforcement learning environments; and Alibaba donated OpenSandbox, a general-purpose sandbox platform for AI applications. The foundation launched in December 2025 with three projects and now hosts ten, including MCP, A2A, agentgateway, and AGENTS.md. Anthropic’s own post gives the scale of the Skills donation: more than 70 agent platforms, including ChatGPT, Cursor, GitHub Copilot, and VS Code, have adopted the standard since it was published in December 2025, about 1 million skills have been published, and nearly 280 million have been installed. Anthropic handed over the name, logo, GitHub organization, and agentskills.io domain; maintainers from Anthropic, Google, OpenAI, and other companies work on it as individuals; and the proposed roadmap includes versioned releases, a formal proposal process, and security guidance for people who write and install skills.
So What: The interfaces of the agent stack are landing in neutral governance: tools through MCP, packaged know-how through Skills, the API shape through Open Responses, and the sandbox underneath. For a buyer, that lowers the lock-in risk of standardizing on them, and it is the reason to prefer these formats over a vendor’s proprietary equivalent. The roadmap still lists security guidance as future work. A skill is a folder of instructions and scripts that an agent executes, 280 million have been installed, and formal security guidance is still on the to-do list.
Now What: If you’re building internal agent capabilities, package them as Skills and expose systems through MCP; portability now has a governance body behind it. Treat skill installation the way you treat package installation: an allowlist, a review step, and an inventory of what is installed where. And if you want to keep your application code portable across model providers, watch Open Responses; it is an attempt to make the API shape itself a standard.
Blank Metal is an AI consulting and engineering firm. We help organizations move from AI experiments to production systems. Learn more