Anthropic blocks users for anything touching training larger models

The thread is less about a single blocked account than about whether Anthropic is quietly turning Claude into a tightly governed service that researchers and builders cannot safely depend on. Many commenters argue that professionals should treat Claude as a powerful but precarious vendor: maintain model fallbacks, keep workflows portable, and invest in local or open-weight options before opaque enforcement strands them mid-project. They see a company willing to exclude training-related use cases while moving toward higher-value enterprise work, and some frame that as both lock-in and hypocrisy given the industry’s contested use of public data. The evidence on what actually triggers enforcement is messy. Some readers think the reported case was likely amplified by accessing an unavailable service through a VPN, or by having Claude directly create or label training data. Others report using it extensively for novel attention research, BERT training, LoRA-based experimentation, and inference infrastructure without refusals. A few distinguish discussing model training from using Claude as a data-production component for a competing training pipeline. Still, reports of refusals around reinforcement learning and ordinary developer work make the guardrails feel unpredictable rather than narrowly targeted. Claude’s capability remains widely admired, but enthusiasm is tempered by fear that access can disappear without a transparent boundary or appeal process.