Distillation headlines · spring 2026
In April 2026 the White House released a memo accusing Chinese labs of running “industrial-scale” campaigns to copy US AI models. Anthropic has publicly named DeepSeek, Moonshot and MiniMax. Naturally, developers running open-weight Chinese models locally start asking the obvious question: is this thing safe on my laptop?
The short answer: the news is about training-time IP theft, not runtime risk. They are completely different categories of concern. Below: what changes, what doesn't, and what we actually expose in DevPulse so you can make an informed call.
The headlines · what they actually say
Using a competitor's public API at scale to generate training data, then fine-tuning your own model on that data. The accusation is that Chinese labs ran thousands of accounts against Claude / GPT-4 to bootstrap their own models cheaply.
Anthropic has publicly identified DeepSeek, Moonshot (Kimi), and MiniMax. OpenAI has separately accused DeepSeek of copying its technology. The labs deny it. The dispute is unresolved.
Commits the executive branch to share threat info with US AI firms, develop best practices, and “explore” accountability mechanisms. It does not propose a ban on running open-weight Chinese models, and it doesn't claim the models themselves are unsafe.
Notice what's not in any of this: a claim that the released GGUF weights are backdoored, a claim that running them locally exfiltrates data, or any technical safety advisory. The dispute is about how the models were built, not what they do after you download them.
Three categories · keep them separate
GGUF and SafeTensors are data formats, not executable code. Loading a model in Ollama, llama.cpp or LM Studio doesn't run code from the model's author. The historical exception — Python pickle (.pt) — isn't how local runtimes ship models in 2026.
Ollama's daemon runs on 127.0.0.1. It downloads weights on `ollama pull`, then runs inference on-device. No prompts, tokens or telemetry leave your Mac during normal use. Verify yourself with Little Snitch, tcpdump, or DevPulse's port monitor.
Some teams won't use models trained via disputed methods, regardless of runtime safety. That's a values call. The catalog labels every model with its lab and license so you can apply your own filter — DevPulse takes no position.
What DevPulse exposes
Each model in Can I Run? shows its origin lab inline: Meta, Mistral AI, Alibaba, DeepSeek, Google, Microsoft. Pick what fits your stance.
Apache 2.0, MIT, Llama Community, Qwen Research — license shows in the row's expand panel. If you need a model for commercial use, the license is the first filter, and it's right there.
A one-line reminder above the model list: weights run fully offline once downloaded; weights don't execute code; no data leaves your Mac. Same in the popover and on the web.
Want the source of truth? The model catalog is a JSON file shared between the macOS app and this website — same lab, same license, same RAM estimates in both places. Browse the full list in Can I Run AI Models? →
Practical · what to actually do
References
DevPulse shows lab, license and runtime status on every model — no editorial, just facts.
Download for macOS