Anthropic filed two federal lawsuits Monday after the Pentagon designated the company a supply chain risk and federal officials moved to halt use of Claude in parts of government. One filing was made in federal district court in California, and a second was filed in the federal appeals court in Washington.
In court papers and public statements, Anthropic said the government action was unlawful and asked for judicial relief to block enforcement while litigation proceeds. The company said the designation and related directives exceeded statutory authority and violated constitutional protections. The Defense Department declined to comment, citing active litigation.
The dispute centers on model-use boundaries in military settings. Anthropic said it would not permit unrestricted use tied to mass domestic surveillance and fully autonomous lethal systems. The Trump administration maintains federal policy requires support for all lawful military uses.
The legal question is moving on a different timetable than procurement behavior.
Defense primes and subcontractors are likely to be bogged down with uncertainty and compliance reviews after the designation, according to multiple reports and contractor-facing guidance. Program teams may be forced to assess whether to pause new deployments, isolate covered workflows, or replace model dependencies in systems connected to Defense Department work. Those decisions can trigger contract modifications, security recertification work, and schedule changes before courts address merits.
Agencies that embedded Claude in existing workflows are balancing transition directives against operational timelines, including phased replacement in systems that support classified or mission-critical tasks. Public reporting also indicates that agency interpretations of scope are not identical across departments.
Anthropic’s enterprise clients are responding with segmentation rather than immediate full disengagement. Several large customers with mixed public-private workloads said Claude use would continue in non-DoD contexts while legal teams and procurement units reviewed defense-linked exposure. That approach limits disruption in commercial coding and productivity use cases, but it does not remove risk for contractors with direct federal obligations.
Market reaction is now tied to procedural milestones. A hearing schedule, interim orders, or agency clarification on scope could change contractor behavior quickly, especially where vendor substitution costs are high. If interim relief is denied, compliance teams are likely to continue migration planning under conservative assumptions.
For now, the case is a live test of how far national-security procurement tools can be used against a domestic frontier AI supplier during a policy conflict over model deployment boundaries. Court filings will determine legal limits, while contractor and client behavior will determine near-term commercial consequences.
