共有:

Claude Code — Enterprise Ban

US and Chinese giants
closed the same door in one month.

Meta on June 30, Alibaba on July 5. Two of the world's largest technology companies each banned employees from using Claude Code at work within a single month. The reasons are not the same, but the sound of the door shutting is.

AI Navigate Editorial2026.07.056 min read

META (US) ALIBABA (CN) Jun 30 — company-wide ban Llama-first / leak concerns Jul 05 — company-wide ban 10 days after 6/26 distillation call-out 5 days Shut out from both continents in one month
01

Two Doors, One Month

Two doors closed, one month apart

A US giant and a Chinese giant both drew a line at "no Claude Code inside the walls."

On June 30, Meta told employees that using Claude Code for work is prohibited from that day on. The stated reasons: focus internal effort on Meta's own Llama-based coding tools, and reduce the risk of internal source code being sent to a third-party inference endpoint.

Then on July 5, Alibaba issued the same company-wide ban on Claude Code. This one landed about ten days after Anthropic publicly accused Alibaba-linked accounts of running what looked like a large-scale distillation attack against Claude on June 26.

02

Different Reasons

The reasons are not the same

Meta's motive reads as "strategy and leak risk." Alibaba's reads as "damage control after 6/26."

Jun 30
Meta — company-wide
Jul 05
Alibaba — company-wide
10 days
6/26 call-out → 7/05 ban

Meta framed its ban around doubling down on its in-house Llama coding stack. Handing internal code to a competitor's agent was described as "helping the other side," and reducing that leakage was the second stated reason.

Alibaba's context is different. On June 26 Anthropic publicly named traffic from Alibaba-linked IPs as "consistent with a distillation attack." The July 5 ban lands as damage control and an outward signal — "we are stopping this at the source" — rather than a competitive strategy move.

Meta (Jun 30)Alibaba (Jul 05)
Prioritise in-house Llama coding stackRespond to the 6/26 distillation allegation
Prevent internal code from leaking to third-party inferenceSignal "we are stopping this" externally
Strategic self-relianceCompliance-driven
03

Who Feels It

Who actually feels this

Enterprise reach into China

From Anthropic's side, the path into the Alibaba group is now effectively closed. Whether Tencent and Baidu follow is the next signal to watch.

Developers in the US, EU, Japan

For solo devs and everyday Western / Japanese enterprises there is no direct impact today. You may need to answer internal questions about "why are big companies leaving Claude Code?" though.

Procurement and legal

Expect more companies to revisit policies on agents that upload source code. The old debate — which parts of the codebase may cross an inference boundary — is back on the table.


When two giants slam the same door in the same month,
the reasons behind them need not be the same.

AI Navigate — Daily Update · 2026.07.05