This week’s news from Zed, Anthropic, and OpenRouter shows why better harnesses matter more than better models

Our five most-read stories this week covered code collaboration, a model router, a UI change, a benchmark, and a caching tutorial. Five different stories about the same problem: Turning a model into something users can actually use.

That’s the harness: The software around the model that supplies context, connects tools, routes work, and checks results.

Zed was the big news this week and is rebuilding how people review agent-written code. OpenRouter is giving companies more control over where requests are processed. Anthropic is rebuilding its stack to be less confusing. The benchmark shows where coding agents still struggle, and the tutorial explains when you can skip a model call entirely.

Late in the week, Vercel’s AI Gateway reported that the average price per token fell 23.2% in August, the third straight monthly decline. Inference is getting cheaper. Companies are buying the harness around inference now, and Zed, OpenRouter, and Anthropic all spent this week selling it.

Zed and Anthropic are removing blockers

On Wednesday, two companies took aim at a familiar problem: getting people to organize work before they can do it.

Zed launched Delta in public beta, building code collaboration around shared threads instead of pull requests. Anthropic began rolling Claude Chat and Cowork into one interface, removing the upfront decisions about which mode a task belongs in.

Paul Sawers reported the Zed story for The New Stack. It was our runaway piece of the week, drawing more than double the traffic of anything else. Zed is clearly onto something.

Zed CEO Nathan Sobo said it best: “It seems like everyone is in a race to replace GitHub right now.”

His argument is that a diff shows you where an agent landed, but leaves much of the conversation that got it there somewhere else. Delta keeps that conversation attached to the code, while DeltaDB records changes at edit-level granularity.

Zed says 33 of its team members landed 570 changes to Delta’s main branch without opening a single pull request. That’s Delta’s own repository; the public Zed editor repository still accepts conventional pull requests.

Meanwhile, GitHub reported 2.9 billion monthly commits in August, up from 1.4 billion in April. This was despite GitHub crashing for nearly eight hours in August. Sobo thinks the thread will become software development’s fundamental unit. And Zed is not on this quest to replace GitHub alone. Cursor’s Origin and GitLab’s Project Switch are other takes on rebuilding code collaboration for agents.

Anthropic is tackling a different user handoff. This week, it announced a unified interface bringing Cowork’s capabilities into Claude Chat. The goal is to reduce confusion and merge capabilities. The rollout starts with Pro and Max users, with other plans following.

“People used both, and told us the frustrating part was deciding where a task belonged,” the company said, as Amanda Caswell reported.

I’ve been using it since the switch, and removing the choice was the right call. Now, users should more easily grasp the capabilities and workflow possible with Cowork.

The economics make the harness matter even more

OpenRouter’s US in-region routing is now generally available to business and enterprise customers. Requests sent through its US endpoint are decrypted, processed, and served inside the country, or rejected if that guarantee can’t be met.

Sawers wrote that story too. One number explains the demand: Open-weight models accounted for roughly 60% of OpenRouter’s US-originating token consumption in August, with Chinese models making up most of the volume.

DeepSeek V4 Pro, Kimi K3, GLM 5.2. These are models developed in China and available through providers running them in US data centers

The models’ country of origin and the location where your data gets processed are different questions. OpenRouter is selling control over the second one. That matters, since Deloitte’s global survey cited in the story found that 77% of companies factor an AI solution’s country of origin into vendor selection. Stripe’s announced acquisition of OpenRouter, reportedly worth about $8 billion, adds another measure of the interest in this layer.

Vercel’s September AI Gateway Production Index, published September 17, shows the economics from another angle:

Open weights took the volume. Closed models kept the money.

Share of tokens against share of spending on Vercel’s AI Gateway, August 2026.

Open weight crossed into the majority of Vercel’s gateway token volume for the first time, up from a reported 7% in December 2025. Vercel says its current open-weight classification is broader than the one used in earlier reports. Among teams running more than ten million tokens in both comparison months, the median team paid 7.6% less per token, following July’s 2.9% decline.

So what justifies the premium?

Boris Renski, CEO of AI agent integration company Apelogic, argues that much of it buys enterprise plumbing: identity integration, connectors, and observability. In Adrian Bridgwater’s July reporting, CNCF executive director Jonathan Bryce described paying ten times more for a four-month capability lead as “a very expensive form of lock-in.”

Closed models still command most of the estimated spending, and customers may be paying for capabilities that cheaper alternatives don’t reliably deliver.

But cheaper inference raises the pressure on everything around it, and Anthropic spent its week on exactly that. Instead of making headlines with a new model, it shipped a merged interface, documents and slides — features arguably more important to most users.

The harness has to earn its keep

Amanda Caswell covered Real-SWE, a benchmark from Y Combinator-backed Specific Labs built on private codebases from real companies.

The best setup tested, Claude Fable 5.1 running through Claude Code, succeeded 38.8% of the time. GPT-6 Astra through Codex CLI reached 33.8%; Gemini 3.8 Flash through Gemini CLI reached 31.2%. None broke 40%.

The benchmark is small: 10 tasks, with eight attempts per model on each. And it tests models with their coding tools, so the harness is already in the score. Still, no model solved the analytics stream reducer across 64 attempts. Zero.

Solutions touched a median of 11 files, compared with six in the public benchmarks cited in the reporting. Real work is spread out. These agents struggled to follow it.

Fable’s leading failure categories were missed requirements and integration errors. That doesn’t mean the information was missing. An agent can have it and still overlook it, misunderstand it, or skip the check.

The engineering problem is getting context, tools, and verification to work together. So is knowing when the model doesn’t need to run at all.

Abhilash Rao Mesala, a senior data engineer at Meta, wrote a practical guide to LLM response caching for us: reuse an answer when the request, context, permissions, and underlying information make it valid. His example starts with a million calls a month at $0.006 each, or $6,000. A 60% cache hit rate, plus $150 in embedding and vector-store costs, brings that to $2,550. A 57.5% reduction from a principle older than the transformer.

The hard part is knowing when a stored answer is still the right answer.

Pair Mesala’s piece with Ida Silfverskiöld’s on Towards Data Science guide to saving on tokens, which covers prompt caching, model routing, and keeping unnecessary materials out of an agent’s context. Both are worth your time.

It’s hard to ignore the doom and gloom hovering over AI at the moment. But there’s good news out there, too. Each week, the price of inference is dropping, and companies are improving harnesses – both are critical improvements to push AI into the mainstream.

The post appeared first on The New Stack.