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 Plumbing Behind Agent-Written Software
Anthropic replaced git because agents outran it, then shipped standard traces so you can see what those agents did, and Figma moved the spec, the input to the agent, onto the canvas in Markdown. The tools around the model are where this week’s work happened, and they are the parts you will have to govern.
Anthropic Replaced Git After Merges Hit 30,000 a Day
What: On October 13, Anthropic’s engineering team published how it moved its monorepo off git and onto Scion, an in-house version control system, in five months. The numbers behind the decision: Anthropic merged about 2,500 code changes a day in May 2026 and more than 30,000 a day by September. The main branch history is close to 100 GB, and CI alone checks out code on the order of 25 million times a day. Git’s design assumes every client is an offline copy of the whole repository; nearly all of Anthropic’s clients are agents and CI jobs that are always online. Scion moves commits, merges, history, and blame to the server, exposes all of it through an API, and gives clients sparse or virtualized checkouts that only fetch the files a job reads. Anthropic says the new infrastructure uses 200 times less CPU and memory than its git mirrors did, checkouts take seconds instead of minutes, and CI got back 25% of its CPU capacity. A team of seven built Scion plus a code review tool, code search, and access controls in the same five months, with Claude writing most of the code. Engineers still review every change, but by intent rather than line by line, and one recurring job was telling Claude “no” when it violated a system constraint. Anthropic says Scion is not a general replacement for git, expects this class of problem to reach other organizations within six to twelve months, and wants to work with GitHub, GitLab, and the open-source community on server-side improvements.
So What: Almost nobody has a 100 GB main branch. The transferable lesson is what happened once writing code stopped being the bottleneck: every system built for human pace became the bottleneck instead, in order of review, CI, merge queue, and finally source control. Anthropic gave up on a global merge-queue lock entirely and moved to post-merge and pre-deploy testing because agents fix conflicts faster than people can find them. Those are decisions your engineering leaders will face at a smaller scale, and the six-to-twelve-month estimate comes from a company that has already hit the wall.
Now What: If you’re scaling agent-written code, start measuring merges per day and CI checkout time now, so you see the curve before you feel it. Write down your review policy in two tiers: which changes get a line-by-line human read and which get an intent review with automated checks. And look at the “superfan” pattern, a Claude session watching one component’s telemetry all day; it is a cheap way to add operational coverage without adding headcount.
Claude Agents Now Send OpenTelemetry Traces to the Monitoring Tools You Already Run
What: On October 14, Anthropic opened a public beta that sends OpenTelemetry traces from Claude Managed Agents, the Messages API, and the Claude SDKs to any observability tool that accepts a standard OTLP endpoint. For the API and Managed Agents, you add a destination in the Claude Console with no code changes; the SDKs in Python, TypeScript, C#, Go, Java, PHP, and Ruby export traces automatically. Every agent turn, model call, and tool use arrives as a trace with latency, token counts, and IDs, following the OpenTelemetry GenAI semantic conventions. Anthropic listed integrations with Grafana Cloud, Honeycomb, Sentry, Splunk, Datadog, New Relic, Arize, Braintrust, Langfuse, LangSmith, PostHog, and Databricks. Ramp said a system it built to score agent traces has already cut token usage 10% to 20% and made sessions 30% faster on some agents. FloQast’s head of infrastructure said the traces let his team answer an auditor’s “what did the agent do and why” from a single timeline.
So What: Observability is what turns “the agent did something” into evidence. Until now, tracing a Claude agent meant instrumenting it yourself or living with the vendor’s console. Standard traces in your existing stack mean the agent sits next to the services it calls, your on-call engineers debug it with tools they already know, and your auditors get a timeline instead of a screenshot. Because the data follows an open convention, the dashboards survive a model change.
Now What: If you run Claude agents in production, add a destination to the observability tool you already pay for this week; it is a console setting. Then make the trace the artifact your change-management and audit processes expect for agent actions, the way a log is for a service. Check what you export: the full-content option sends prompts and responses to your observability vendor, and from there your retention policy governs them.
Figma Puts the Spec on the Canvas, in Markdown, Where Agents Can Read It
What: On October 15, Figma launched Specs, a Markdown-based document that lives on the Figma canvas next to the designs it describes, in open beta on paid plans across web, desktop, and mobile. You can drag any .md file onto the canvas to turn it into a spec, embed a FigJam file, a frame, or any canvas node inside it, and pull outside context in through connectors such as GitHub for a technical spec or Hex for product data. Figma’s agent can read and reply to comments in a spec, so an open question can be answered by the agent in the thread where it was asked. When the team agrees, the spec’s link goes into a coding agent’s prompt through Figma’s MCP server, carrying the Markdown plus references to frames, diagrams, code layers, and Code Connect snippets. Figma also moved code layers, working code on the canvas, into open beta, and added 20 MCP integrations.
So What: Last week Google Docs learned to edit Markdown natively; this week Figma did. Markdown has become the handoff format between people and agents, and the tools people already work in are adopting it. The more important shift is where intent lives. If the spec is the input to the agent that writes the code, then the spec is the artifact to govern, version, and review, and Figma is making a bid to be where it lives.
Now What: If your product team is in Figma, run one feature end to end: write the spec in Specs, hand it to the coding agent through MCP, and see what the agent gets wrong, which is usually a gap in the spec. Then decide where the canonical spec lives for your organization, whether Figma, the repository, or Docs, because three Markdown copies that drift is worse than the Google Doc you had before.
What You Pay, and What You Can Own
Accenture set a $29 central allowance for Claude, and the reaction showed where token-heavy work concentrates. Anthropic reportedly showed investors revenue covering compute at 1.7 to 1. OpenAI priced speed as its own tier, Microsoft unbundled Copilot from the suite, and Meta released a frontier-class model you can run on two desktops. Every one of these changes the unit economics of an AI program, and most of them land before year end.
Accenture Caps Centrally Funded Claude Spend at $29 Per Employee Per Month
What: 404 Media reported on October 15 that Accenture told employees that, effective October 1, the company will centrally fund only $29 a month per person toward Claude Enterprise usage. All costs are consumption-based, so anyone who exceeds the allowance has to charge the rest to a specific project or team code. Premium plans come with $250 of token usage a week, but many employees are not on that plan. Internal messages seen by 404 Media include employees whose usage runs $500 to $1,000 a month, one building an AI accelerator for multiple clients, now working to get upgraded or find a project to bill. One employee said their access was revoked. The announcement says licenses will be reviewed periodically and reallocated based on business need. An Accenture spokesperson said the company provides “the right tool for the right work” and continues to invest in AI capabilities and enablement.
So What: This is what consumption pricing looks like at the scale of a large enterprise, and the mechanism is sound: a flat allowance per person, chargeback to the project that benefits. The hard part is the transition. Under a flat cap, the people hit first are the ones whose work has already become token-heavy, which is often the people getting the most out of the tool, so the path from “I need more” to “approved” has to exist before the cap lands. A $29 allowance against a $1,000 workload works like a stop sign, whatever the policy intends.
Now What: If you’re moving to consumption-priced AI tools, set the allowance by role rather than one number for everyone, and build the overage path first: who approves, on what evidence, within how many days. Pull the usage report and look at your top 5% of users before you set any cap, because that is where the return on your AI spend is concentrated. And give people a sanctioned way to fund heavy usage, or they will fund it on personal cards and your data governance goes with it.
Anthropic Reportedly Told Investors Quarterly Revenue Reached $16.8 Billion
What: Anthropic hosted institutional investors in San Francisco on October 14 ahead of a planned IPO. The Financial Times, citing people with knowledge of the matter, reported that the company told investors revenue was about $4.8 billion in the first quarter, $11.5 billion in the second, and $16.8 billion in the third, up nearly 50% quarter over quarter. In the third quarter the company reportedly earned $1.70 in revenue for every $1 spent on computing power, with adjusted operating margins of 11% excluding stock-based compensation. Anthropic also reportedly told investors that “distillation,” rival labs training on Claude’s outputs through heavy API use, had accounted for 5% to 7% of revenue and had been cut back materially in the quarter. Bloomberg has reported that IPO marketing could begin the week of November 9, with trading before Thanksgiving. Simon Willison’s write-up of the FT piece is linked below; the FT article itself is paywalled.
So What: Read the numbers as a buyer. Revenue that covers compute at 1.7 to 1 and a positive adjusted margin suggest the vendor is not selling below cost, which is the question behind every multi-year AI commitment. A public listing also brings audited financials and quarterly disclosure, which makes a frontier lab easier to evaluate on a vendor-risk register than a private company whose numbers arrive through leaks. The distillation clampdown is a reminder that unusually heavy API usage patterns now get looked at.
Now What: If Claude, or any frontier model, is on your vendor-risk register, this is the quarter to update the entry with what is now public. If you’re negotiating an enterprise agreement, ask for price-protection terms in writing; a company about to go public has every incentive to sign durable revenue. And treat all of these figures as reported until the prospectus is out.
OpenAI Sells Speed as a Tier: Ultrafast Mode for GPT-6.1 Sol at Six Times the Price
What: On October 8, OpenAI rolled out Ultrafast mode for GPT-6.1 Sol in the API, Codex, and ChatGPT Work. OpenAI describes it as near-Astra intelligence at up to eight times the speed of Sol’s standard tier, and recommends it for debugging an outage, agents navigating applications, and live experiences where every second counts. Pricing is $12 per million input tokens and $60 per million output tokens, against $2 and $10 for the same model in Standard mode. It is available to all API users with its own rate limits, supports US and EU data residency, and OpenAI strongly recommends running it over a persistent WebSocket connection, because for agents making many tool calls in quick succession, network overhead can eat the latency gain. Ultrafast is also available for GPT-6 Astra, and AWS offers it on Amazon Bedrock.
So What: The same model now comes in speed classes with different prices, like compute instances. That changes the decision from “which vendor” to “which tier for which workflow.” For an interactive agent that makes thirty tool calls to answer one question, latency compounds, and a six-fold price for an eight-fold speedup can be the cheaper option once you count the human waiting. For a batch job that runs overnight, it is money thrown away.
Now What: If you run GPT-6.1 Sol, sort your workflows into latency-bound (customer-facing agents, support, incident response) and throughput-bound (batch classification, document processing, overnight runs), and route only the first group to Ultrafast. Measure tokens per second on your own traffic; “up to 8x” is a vendor ceiling. And if you move an agent to Ultrafast, move it to WebSockets at the same time, or you will pay the premium without getting the speed.
Microsoft Will Sell Copilot Without a Microsoft 365 Subscription Starting December 1
What: In an October 14 Partner Center announcement, Microsoft said that beginning December 1, 2026, new Microsoft 365 Copilot and Copilot Business offers can be purchased without a qualifying Microsoft 365 base subscription, across all channels and for commercial, education, government, and nonprofit customers. The new offers carry their own SKU IDs and the same price as today’s. Beginning October 16, the current offers that do require a base subscription get “(add-on)” appended to their names, and those add-on SKUs reach end of sale in the partner channel on December 1, though existing customers can keep renewing. Microsoft notes that Copilot experiences still depend on which Microsoft 365 apps and services a customer is licensed for. The same announcement page moved the default-on date for usage-based billing on new Copilot Business licenses from November 2 to December 1, with a default spending limit of 4,000 Copilot Credits per user per month that admins can adjust.
So What: Decoupling Copilot from the bundle is a distribution move: Microsoft wants to sell Copilot into Google Workspace shops and into budgets that are not the Microsoft 365 renewal. For you, Copilot becomes its own line item that can be evaluated, and cut, on its own. The fine print still matters, because a Copilot seat without the underlying apps is a chat window, and the usage-based billing default is now the larger cost decision.
Now What: If you buy through a partner, check any procurement automation keyed on offer names now; the names change October 16. If you run Google Workspace and have been quoted Copilot, December 1 is when the base-subscription requirement goes away, but get a feature-by-feature list of what works without Microsoft 365 apps before you sign. And set your Copilot Credit limits per user before December 1, or the 4,000 default will set them for you.
Meta Releases Muse Spark Open, an 816-Billion-Parameter Model You Can Run on Two Mac Studios
What: On October 15, three days after launching Muse Wonder, Meta released the weights for Muse Spark Open, which it calls the most capable US open-weight model to date. It is a natively multi-modal mixture-of-experts model with 816 billion total parameters, 42 billion active per token, and a 1-million-token context window, built for coding and long-horizon agentic work. Weights are on Hugging Face, Amazon SageMaker, Google Cloud Model Garden, and Microsoft Foundry; hosted inference is available from Baseten, Fireworks, Groq, Modal, Nebius, OpenRouter, and Together AI; it runs on vLLM, SGLang, TensorRT-LLM, llama.cpp, and Apple’s MLX. Meta worked with Apple so the full model runs on two M5 Ultra Mac Studios with 512 GB of unified memory each, and Apple’s machine learning research team published the benchmarks. The weights ship under the Muse Model License with limited commercial terms, which Meta says lets many developers use the model free. Meta says the open version received additional safety post-training and met the thresholds in its scaling framework; a full evaluation report is still to come.
So What: A frontier-class open-weight model from a US lab, with a hosted-or-self-hosted choice, changes the build-versus-buy math for workloads that can’t leave your network. Two desktop machines that cost tens of thousands of dollars, not a GPU cluster that costs millions, is a real on-premises option for regulated data, air-gapped environments, and data-residency requirements. “Limited commercial terms” is doing a lot of work in that announcement, though, and it is a license your lawyers read before your engineers deploy.
Now What: If you have workloads that can’t use a hosted API, benchmark Spark Open on them through one of the hosted providers first; that costs an afternoon and tells you whether the hardware conversation is worth having. Send the Muse Model License to legal now, with your intended use cases attached, because “many developers” is not “all enterprises.” And if you’re already running an open model, this is the one to compare against before your next hardware purchase.
Agents That Work for One Person
Meta’s new frontier model is built around memory of you. Shopify’s new skill turns the agent you already use into a shopper that knows your sizes. The next wave of agents is personal, which makes context the product and data handling the first question.
Meta Ships Muse Wonder, a Frontier Model Built for Work Agents
What: On October 12, Meta introduced Muse Wonder and Muse Wonder Full, which it calls its most capable models and claims lead on personal and professional agentic tasks. The pitch is two capabilities Meta names Active Memory, carrying context about you across conversations and retrieving what is relevant, and Active Focus, sustaining work on a long task, trying alternatives, and checking in before important actions. Meta published results on Harvey’s Legal Agent Benchmark, the Vals Finance Agent benchmark, MemoryBench, SWE-Marathon, and its own FocusBench, and says the models are its most aligned to date, with its strongest safeguards against chemical, biological, and cyber misuse. Muse Wonder is available through the Meta Model API and Muse Code; Wonder Full is available to Muse Code subscribers. The models were trained at Meta’s gigawatt-scale Prometheus data center, fourteen months after Meta restarted its AI effort from scratch.
So What: This is Meta’s bid to be a fourth credible supplier of frontier models for enterprise work, after Anthropic, OpenAI, and Google. A fourth bidder changes your negotiating position and widens your evaluation matrix. The product bet is memory: an agent that knows your context across sessions is more useful and also the exact feature your data-governance team will ask about first.
Now What: If you already run evaluations for your agentic workflows, add Muse Wonder to the set and let your own tasks decide; the vendor’s benchmark chart is where you start. Before any pilot, ask Meta how memory is stored, scoped, and deleted for enterprise accounts, and whether your data is used for training. Legal and finance teams should look at the domain benchmarks Meta chose to publish; they say which buyers Meta is going after.
Shopify Turns Any Agent Into a Personal Shopper With One Skill File
What: On October 13, Shopify launched shop.md, a skill that turns an agent you already use into a personal shopper connected to your Shop account. Add it to ChatGPT or Claude with one click, or paste the prompt into another agent, and it searches Shopify’s catalog of more than a billion products with your saved sizes and preferences, checks out with Shop Pay after you confirm the merchant, items, total, and payment method, and tracks orders in the Shop app. A second page lets you describe how you shop and what matters to you, then generates a personal prompt to paste into your agent, so you can build your own skill without knowing what a skill is. Underneath is Shop MCP, a server with 17 tools that developers can point any agent at; orders placed through an agent land in the merchant’s Shopify admin like any other, and for stores not on Shopify the shopper approves the purchase and the agent gets single-use card details.
So What: If you sell online, your products are now reachable through agents your customers already use, over a channel you don’t control, and whether you show up depends on your product data. If you run internal AI programs, the design is worth stealing: a capability shipped as a text file, a connected account for identity and payment, and a plain-language page that turns someone’s preferences into a skill. That is the most approachable onboarding to agents we have seen, and it did not require a new app.
Now What: If you’re a Shopify merchant, run your own catalog through the skill this week and fix what the agent gets wrong; it will be product data. If you’re on another platform, ask your vendor when the equivalent ships, because your competitors on Shopify are already in the channel. And if you’re rolling agents out to non-technical staff, copy the “describe how you work, get a skill” pattern for your own workflows before you hand anyone a Markdown file.
Blank Metal is an AI consulting and engineering firm. We help organizations move from AI experiments to production systems. Learn more