Anthropic Attempts to Block Chinese Developer's Open-Source 70B Model on GitHub; Project with 20,000 Stars Sparks Lawsuit

On June 19, 2026, a Chinese developer released the airllm 70B open-source model on GitHub, gaining 20,000 stars. Anthropic and other companies subsequently attempted to block the repository and filed a lawsuit.

On June 19, 2026, Chinese developers released the airllm 70B local model on GitHub, and the project received 20,000 stars. Companies such as Anthropic subsequently attempted to block the repository and filed a lawsuit.

Practical Feasibility of Local Operation

The airllm 70B model supports direct loading and inference on consumer-grade hardware, without relying on cloud APIs. Users can start after downloading the weight file, and the code repository provides a one-click installation script. In actual testing, FP16 inference of 70B parameters can be completed on a single 24GB graphics card.

This implementation approach bypasses external service calls, reducing the data upload step. The model file size is approximately 140GB, and users need to prepare sufficient storage space.

Comparison with Closed-Source Services

Closed-source models are typically provided through APIs and billed by token. The airllm 70B, on the other hand, requires users to bear the hardware costs themselves. Under the same prompt, the response latency of the local model depends on the performance of the local device, reaching up to 20 tokens per second, while API services are often above 50 tokens per second.

In terms of privacy, the local model does not send input text to third parties. Companies such as Anthropic, however, retain clauses allowing the use of data for model training. A cost comparison shows that continuous use of an API for one year may exceed the cost of purchasing a graphics card, while the local model only requires a one-time hardware investment.

Blocking Measures and Legal Dispute

After the GitHub repository was reported by Anthropic, access restrictions appeared, and the developer subsequently faced a lawsuit. The grounds for the lawsuit involve the sources of model training data and intellectual property. Following the public disclosure of the incident, two stances emerged within the community: one side believes local deployment protects user data, while the other is concerned that the model could be used in unregulated scenarios.

As of June 21, 2026, the lawsuit is still ongoing, and the repository's star count remains above 20,000.

Recommendations for Developers and Enterprises

  • Teams that need to process sensitive data can prioritize testing the local deployment of airllm 70B and verify hardware compatibility before deciding on long-term use.
  • For applications with high inference speed requirements, it is recommended to keep the API as a supplement and switch when local model responses are insufficient.
  • Enterprises should establish a model source review process to avoid using weight files with legal risks.
  • Open-source contributors need to pay attention to license changes and back up code repositories in a timely manner.