Everyone covered the $25B Amazon deal. The real partnership is a JSON protocol on your Mac.
Amazon added $5B with room for $20B more. Google and Broadcom expanded compute. CoreWeave signed a long-term deal. Accenture went multi-year. Project Glasswing brought in Apple, Microsoft, and Nvidia. That is the press cycle. This page is about the other partnership, the one that happened quietly in a file called acp-bridge/src/oauth-flow.ts, and why an indie Mac app like Fazm can plug into Claude on roughly the same footing as Claude Code itself.
THE HEADLINES
What Anthropic actually signed in April 2026
Five announcements dominated the April 2026 coverage of Anthropic partnerships. Each one matters. None of them are the reason your app can talk to Claude today.
Amazon, an additional $5B with room for $20B more
Bloomberg reported Amazon investing another $5 billion in Anthropic, with optionality for up to $20 billion more. Anthropic, in turn, committed to spending more than $100 billion on Amazon cloud and chips over the next decade. This is primarily a compute and capital deal. It changes where Claude runs and how much of it there is. It does not change the request shape your app sends.
Google and Broadcom, expanded TPU supply
Anthropic bulked up its existing deal with Google and Broadcom to ship Google TPU chips at a larger scale. Reporting pegged Anthropic's run-rate revenue around $30 billion at announcement. The partnership is primarily about inference capacity for paid Claude plans and for API customers, which is the capacity that serves every third-party client that talks to claude.ai on behalf of a user.
CoreWeave, long-term compute partnership
CoreWeave signed a multi-year agreement with Anthropic aimed at processing capacity for the Claude model family. More suppliers, fewer single points of failure, same basic economics for end users on paid plans. Same story. Capacity side of the house.
Accenture, multi-year enterprise rollout
Accenture and Anthropic launched a multi-year partnership to deploy Claude across enterprise customers. This is a go-to-market channel. It affects big-company adoption. It does not affect whether a 20-person startup can ship a desktop app that uses Claude via a user's own subscription.
Project Glasswing, gated cybersecurity consortium
The headline partnership of the month in the security press. Anthropic, with Amazon, Apple, Microsoft, Nvidia, and a small handful of others, around the new Claude Mythos preview model. Mythos is gated because it is unusually capable at identifying and exploiting software vulnerabilities. Glasswing is explicitly not open to general developers.
THE REFRAME
Every headline is about capacity. None is about integration.
Read those five announcements back to back and a pattern appears. Amazon buys inputs (cash, compute). Google and Broadcom and CoreWeave sell inputs (chips, data centers). Accenture resells outputs to enterprises. Glasswing tests outputs with a small trust circle. Every one of those deals is about the size of Claude, not the shape of Claude's interface.
If you are building a product on top of Claude, none of those five deals tells you how to ship a feature next week. The answer to that question lives in a different place entirely: a node_modules directory, an OAuth callback on localhost, and a keychain entry Anthropic's own CLI wrote first.
THE QUIET PARTNERSHIP
The Agent Client Protocol is the partnership
Anthropic does not need to sign a contract with every third-party client. It ships a protocol, publishes the reference SDK, and any app that implements it can act on behalf of a logged-in Claude user. The Fazm desktop app does this. Here is the diagram.
How Fazm plugs into Claude
THE ANCHOR FACT
One OAuth constant explains the whole setup
Inside Fazm's source tree there is a 200-line TypeScript file that reimplements the Claude Code CLI sign-in flow without a TTY, so a GUI desktop app can use it. The first block of constants is the whole story.
Line by line. The CLIENT_ID is the same OAuth application ID the official Claude Code CLI uses. The authorize URL points at claude.ai, not at a partner portal. The token URL is the public Anthropic console. The scope is the single user:inference scope, which is exactly what a human using Claude on their own account can do. And the keychain service is literally named “Claude Code-credentials”.
WHY THIS LINE MATTERS
Because the keychain slot is shared with Claude Code, a macOS user who is already signed in to Claude Code in their terminal is already signed in to Fazm the first time they open it. No second OAuth round trip. No “enter your API key” screen. No separate Anthropic billing relationship. The partnership surface is a string literal.
MODE A VS MODE B
Two ways a third-party app can be “partnered” with Anthropic
There are exactly two paths. The ACP bridge picks between them on startup with a single check on acp-bridge/src/index.ts line 535. If the environment has ANTHROPIC_API_KEY set, the bridge runs in Mode A and spends the app publisher's API credits. If the key is missing, the bridge runs in Mode B and drives the user's own Claude Pro or Max login.
| Feature | Mode A (app pays) | Mode B (your Claude login) |
|---|---|---|
| Who pays for tokens | The app publisher, via API key | The user, via existing Claude Pro or Max subscription |
| OAuth required | No | Yes, Claude Code flow with PKCE |
| Model access | Whatever the API key is entitled to | Whatever the user's plan includes, Sonnet 4.6 default, Opus 4.7 selectable |
| Credentials stored | ANTHROPIC_API_KEY env var | macOS Keychain under "Claude Code-credentials" |
| Needs a custom Anthropic partnership | No | No, public OAuth client |
| Works offline or air-gapped | No, still hits api.anthropic.com | No, still hits claude.ai for auth and api.anthropic.com for inference |
Both modes route through the same ACP wire protocol. The only thing that changes is whose credits get drawn down. That choice lives on acp-bridge/src/index.ts line 535 as a ternary on env.ANTHROPIC_API_KEY.
THE WIRE
What an ACP sign-in and first turn looks like
When a user launches Fazm for the first time and is not already signed in to Claude Code, the bridge performs an OAuth round trip, stores the tokens, and then streams the user's prompt to Claude. Roughly:
First query, Mode B
Every box above runs on the user's machine and on Anthropic's public surfaces. No intermediate “partner” API. No additional token exchange with a Fazm server. The Fazm server does not even see the user's prompt in Mode B.
The last column is the whole argument.
TRYING IT
What “no partnership” looks like at a shell prompt
Most of this is boring if you already use Claude Code. The keychain entry it creates is exactly the one Fazm reads. You can confirm the share with one command, and you can watch Fazm pick it up on startup.
WHAT FAZM ADDS
If the protocol is free, what is the product?
An honest question when the partnership is “install a package from npm”. The Fazm answer: the protocol is free, but plumbing it into the macOS accessibility APIs, shipping five built-in MCP servers, and making the whole thing feel like a native Mac app is not free. The bridge's own code lists the built-in servers in one line near the top.
fazm_tools
First-party MCP server for common desktop actions that do not fit inside the other servers. Hardcoded in BUILTIN_MCP_NAMES alongside four other built-ins.
macos-use
Native MCP server that drives any AX-compliant macOS app via the accessibility tree. Used for Finder, Settings, Mail, Notion, Slack, anywhere a DOM does not exist.
playwright
Only used when the task is actually in a browser tab. Fazm does not pretend to be a browser agent when the user is in a native app.
Drives the native WhatsApp Catalyst app, not WhatsApp Web. Again, avoids a fragile browser dependency for something that exists as a real macOS window.
google-workspace
Gmail, Calendar, Drive via the user's own Google OAuth. Not wired through a Fazm server.
Custom via ~/.fazm/mcp-servers.json
Added in Fazm 2.4.0 on 2026-04-20. Users can bring any MCP server the Claude ecosystem supports, toggled in the Settings UI.
“Upgraded Claude agent protocol to v0.29.2”
Fazm CHANGELOG.json, v2.4.0, 2026-04-20
That single line from the 2026-04-20 changelog is what a partnership bump looks like when the partnership is a JSON-RPC spec. No press release. Upgrade the dependency, ship the build, inherit the wire-format improvements the same day Anthropic publishes them.
THE PARTNERSHIP MAP, REDRAWN
Same company, two orbits
The tidy way to resolve the Amazon-versus-ACP tension is to draw Anthropic with two orbits around it. One orbit is capacity. The other orbit is interfaces. Both are real partnerships. They just pay off on different timelines.
Left-leaning items are capacity and enterprise partnerships. Right-leaning items are protocol-level clients. Both revolve around the same center.
WHO SHOULD CARE
Three audiences, three different actions
For investors
If you came to this page searching for “anthropic partnership april 2026” expecting another writeup of the Amazon deal, the CoreWeave contract, or the Project Glasswing cybersecurity consortium, you have those in the FAQ below. The spine of this page is the claim you will not find in the other results, that the partnership most relevant to a shipping desktop app is not any of those, it is the Agent Client Protocol, the OAuth client shared with Claude Code, and the keychain entry that makes single-sign-on a zero-line change.
Want to see an ACP-powered Mac agent in action?
Fifteen minutes on a call and we will walk through the Fazm bridge live, from OAuth to first token stream.
Book a call →Frequently asked questions
What partnerships did Anthropic actually announce in April 2026?
Five that dominated the coverage. Amazon committed an additional $5 billion, with room for another $20 billion, bringing its total Anthropic investment near $25 billion. Anthropic plans to spend more than $100 billion over ten years on Amazon cloud and chips in return. Separately, Anthropic expanded its compute agreement with Google and Broadcom to ship TPU chips at larger scale. CoreWeave signed a long-term compute partnership on top of that. Accenture announced a multi-year partnership to deploy Claude across enterprise clients. And Project Glasswing, a cybersecurity partnership with companies including Amazon, Apple, Microsoft, and Nvidia, launched around the new Claude Mythos preview model.
Is any of this a partnership a small or consumer app can actually participate in?
Not directly. Amazon, Google, Broadcom, CoreWeave, Accenture, and Project Glasswing are infrastructure and enterprise deals, not developer relationships. The real partnership surface for a third-party consumer app is not a contract. It is Anthropic's Agent Client Protocol (ACP), an open JSON-RPC transport the Claude Code CLI speaks, plus the OAuth flow that lets an app act on behalf of a user's Claude Pro or Max subscription. Fazm is a live example of this pattern on macOS.
What is the Agent Client Protocol (ACP) and why does it matter here?
ACP is the Agent Client Protocol developed in the same ecosystem as the Claude Code CLI. It defines how a host app streams sessions, prompts, tool calls, permissions, and model selection over line-delimited JSON on stdin and stdout. Fazm depends on the npm package @agentclientprotocol/claude-agent-acp version ^0.29.2, declared in /Users/matthewdi/fazm/acp-bridge/package.json. That single dependency is what lets a Swift desktop app speak the same protocol that Anthropic's own tooling speaks, without a private contract and without a custom Anthropic integration.
What is the anchor fact about Fazm's integration with Claude?
The file acp-bridge/src/oauth-flow.ts uses CLIENT_ID "9d1c250a-e61b-44d9-88ed-5944d1962f5e" on line 25 and writes credentials to KEYCHAIN_SERVICE "Claude Code-credentials" on line 30. That is the same Keychain slot Anthropic's Claude Code CLI writes to. A macOS user who is already signed into Claude Code in their terminal is already signed into Fazm on first launch. Mode B (personal Claude Pro or Max login) is selected automatically when ANTHROPIC_API_KEY is not present in the environment, as seen on acp-bridge/src/index.ts line 535.
What is the practical difference between the Amazon deal and the protocol-level story?
The Amazon deal is about where Claude runs. Anthropic will spend more than $100 billion on Amazon compute, and Amazon gets a deeper investment position. None of that changes the request your app sends. The ACP layer is about how third-party apps talk to Claude on behalf of a user. That changes every day for every app that ships on top of Claude. If you are building a product, the second story is the one that affects your code this week. If you are buying stock, the first one matters more.
Does Fazm benefit from Anthropic's expanded compute deals?
Indirectly. More TPU and GPU capacity means fewer overloaded and rate-limited turns for paid Claude subscribers, which is what Fazm routes through in Mode B. It also lets Anthropic keep Opus 4.7 on the same pricing as Opus 4.6 despite demand, which helps the cost basis of any pay-as-you-go extra usage. But Fazm does not sign anything with Amazon, Google, CoreWeave, or Broadcom. It inherits the improvements the moment they reach the consumer Claude plan a user is logged into.
What is Project Glasswing and is Fazm on the list?
Project Glasswing is Anthropic's gated partnership program for the new Claude Mythos preview model. Public reporting says it is distributed to a small set of partners, including Amazon, Apple, Microsoft, Nvidia, and a handful of others, because Mythos is unusually strong at identifying and exploiting software vulnerabilities. It is explicitly not a broad developer program. Fazm is not on that list and does not plan a product strategy that depends on Mythos. The Fazm default model is still claude-sonnet-4-6, set on acp-bridge/src/index.ts line 1245, with Opus 4.7 selectable from the in-app model picker.
Why does the CHANGELOG.json mention upgrading to ACP v0.29.2?
Fazm 2.4.0, dated 2026-04-20, bumps the Agent Client Protocol dependency to v0.29.2. That line in CHANGELOG.json reads "Upgraded Claude agent protocol to v0.29.2". The upgrade keeps Fazm on the current wire format and reflects the point made throughout this guide, the partnership is the protocol. Every version bump of @agentclientprotocol/claude-agent-acp is effectively a free contract update without any signature.
Do I need to be an Anthropic partner to build something like Fazm?
No. The ingredients are public. Install @agentclientprotocol/claude-agent-acp from npm. Implement the ACP wire format over stdio (the Fazm bridge lives in /Users/matthewdi/fazm/acp-bridge/src/index.ts). Implement the Claude Code style OAuth flow with the documented CLIENT_ID, AUTHORIZE_URL https://claude.ai/oauth/authorize, TOKEN_URL https://console.anthropic.com/v1/oauth/token, and SCOPES user:inference (all visible in acp-bridge/src/oauth-flow.ts). A user who already has Claude Pro or Max can sign in with one click. No separate partnership paperwork required.
How should I think about "Anthropic partnerships" as an investor vs as a developer?
As an investor, the April 2026 deals are about capacity and revenue durability. Amazon $25B, Google and Broadcom TPUs, CoreWeave, the Accenture channel, all reinforce a $30B annualized run rate and a path to more. As a developer or founder, the partnership that ships product is the one with no press release. It is the protocol, the OAuth flow, and the fact that any macOS app can today act on a user's Claude subscription without negotiating anything. The two stories are not in tension, they operate on different surfaces.
Adjacent reads from the Fazm source tree
Related guides
Anthropic release April 2026: Opus 4.7 GA, Mythos, Claude Design
The model release version of this page. Opus 4.7 went GA at Opus 4.6 prices. Mythos went into Project Glasswing. Claude Design shipped in Labs. What all of that means for a Mac agent.
Open-source LLM news 2026
A companion view on the rest of the April 2026 model landscape, outside the Anthropic ecosystem.
What is Claude extra usage?
When a Pro or Max user exhausts their plan and moves to pay-as-you-go, how the rate limit machinery shows up inside a third-party ACP client.