Anthropic - SKEPSIX.

TL;DR: Anthropic refused the Pentagon’s demand to remove AI safeguards, lost a $200 million contract, and OpenAI took it the same day. Then Amodei quietly resumed negotiations. The Oprah interview framed this as a moral stand. The actual timeline tells a different story.

What actually happened: the timeline the Oprah interview skipped

On February 24, 2026, Defense Secretary Pete Hegseth gave Anthropic a deadline: allow unrestricted use of Claude “for all lawful purposes” or lose the $200 million Pentagon contract. Anthropic refused, publishing a statement saying the Pentagon’s language “was paired with legalese that would allow those safeguards to be disregarded at will.” Amodei wrote publicly: “we cannot in good conscience accede to their request.” The Pentagon cancelled the contract and designated Anthropic a “supply chain risk” — a classification normally reserved for companies linked to foreign adversaries.

The same day, the Pentagon struck a deal with OpenAI. Amodei reportedly sent an internal message to Anthropic staff calling the OpenAI deal “safety theater” and the messaging around it “straight up lies.” Pentagon official Emil Michael called Amodei “a liar with a God complex.” The public framing was clean: Anthropic stood on principle, OpenAI didn’t. Two and a half million users reportedly moved to Claude in the weeks that followed.

What the Oprah interview did not mention: within days of the public rupture, Amodei had quietly resumed negotiations with Emil Michael — the same official who had called him a liar. Those talks were reported by the Financial Times and Bloomberg in early March. The red line had already started moving before the cameras were set up for Oprah.

The “not ready” argument is a timeline, not a principle

When Daniela Amodei clarified the position during the Oprah interview, her phrasing was telling: the models are “not ready for this use case” at present. Not “we will never do this.” Not “this is categorically wrong.” The refusal was framed as a technical pause, not a moral absolute.

That framing has a specific implication. If the limit is readiness, then the question isn’t whether Anthropic will eventually work with the Pentagon — it’s when the internal metrics say the models are ready. And those metrics are not public. Anthropic tracks hallucination rates, safety margins, and reliability benchmarks under internal programmes that nobody outside the company can audit. The moment those numbers cross an undisclosed threshold, the “not ready” position becomes “ready,” and the moral argument quietly retires.

Frontier model hallucination rates have improved from 3 to 8 percent in 2023 to roughly 1.0 to 2.5 percent in 2026 on summarization benchmarks. On long-tail factual queries — the kind that would matter for intelligence analysis or classified document review — rates remain at 15 to 40 percent. That gap is the unofficial deadline. When engineering closes it, the public posture will shift. The only question is how loudly.

The Palantir arrangement already crosses the line in everything but name

There is a further complication that rarely surfaces in the coverage. Anthropic maintains a partnership with Palantir, which supplies Claude-powered interfaces to defence clients under a separate API tier. Military analysts already use Claude to interrogate sensitive documents. The foundation model that civilian Pro users access is the same one reaching the defence sector through a vendor intermediary.

This arrangement allows Anthropic executives to say accurately that they have no direct uniformed customer while the underlying reasoning engine already reaches the Pentagon. The “supply chain risk” designation sits alongside an active indirect supply chain. The architecture of the refusal is a licensing construct, not a technical barrier. Removing Palantir as the intermediary would not require new training runs or architectural changes — it would require a contract amendment.

Why Anthropic cannot afford to reverse course loudly

This is where your read of the situation matters more than the article originally acknowledged. Two and a half million users came to Anthropic in part because of that public refusal. They came because Anthropic said something that sounded like a values statement, and they believed it. That audience is not monolithic — some are developers who care primarily about capability, others are users who specifically chose Claude because it felt like the alternative to the “move fast, sell to anyone” model.

If Anthropic formally reverses the Pentagon position — not through a quiet Palantir workaround but through a publicly acknowledged direct contract — the reputational cost is asymmetric. The users who came for the values statement will notice. Some will leave. Gemini and open-weight alternatives exist and are improving. The switching cost for a user who chose Claude for ethical reasons rather than raw capability is low.

Anthropic is not naive about this. The Oprah interview was not accidental — it was a moment of narrative management, reframing a messy and ongoing negotiation as a clean moral stand. The timing, three months after the contract collapse and in the middle of resumed talks, suggests the interview served a specific function: locking in the brand association with safety before the engineering roadmap makes the current position untenable.

What to actually watch: the metrics, not the soundbites

The practical task for anyone trying to understand where Anthropic’s actual limits are is straightforward: ignore the interviews and watch the benchmarks. When internal safety metrics for long-tail factual reliability cross the threshold that Anthropic considers acceptable for high-stakes classified use, the position will change. It may change through a carefully worded announcement about “expanded mission alignment.” It may change through a Palantir contract extension that nobody covers. It may even change through a direct Pentagon deal framed as a breakthrough in responsible AI deployment.

What it will not do is announce itself as a reversal. The framing will be continuity. The substance will be exactly what Amodei said in February he would not do. Track the hallucination benchmarks, not the prime-time appearances. The safety argument will expire when the numbers allow it to — and the numbers are already moving in one direction.

TL;DR: Claude’s usage limits hit hardest in the middle of complex coding, writing, or analysis sessions, breaking flow and wasting tokens. Hallucination rates have fallen, but continuity remains unmeasured. The community builds elaborate workarounds while Anthropic fixes everything except the stop-start experience.

The limit doesn’t warn you. It just stops you.

The complaint surfaces repeatedly: you ask Claude to implement a small bug fix or run a quick analysis, and halfway through the task it runs out of quota. Context vanishes. The thread you built with model and tool is severed, and the error message feels like a rebuke for working too long. This isn’t a hallucination problem; Claude Opus 4.7 now hallucinates on only 1.0 to 2.5% of summaries, a dramatic improvement in factual reliability. But a 1% hallucination rate doesn’t matter when the model cannot complete the summary because you hit a usage wall mid-paragraph. A frontier model with benchmark-leading accuracy is useless when it won’t stay connected long enough to deliver.

The Pro plan grants significantly more usage than the free tier, yet the cap remains an opaque, unbendable limit. Users describe hitting it “every time” they attempt a non-trivial session. The frustration isn’t that a limit exists; it’s that the threshold cuts work off at the worst possible moment, without warning and with no mechanism to finish the thought. You lose not just the tokens you already spent, but the time it takes to reconstruct mental state, re-upload files, and re-establish the conversation’s nuance. The model’s intelligence is not in doubt; the service’s rhythm is.

Claude’s rate limits interrupt coding sessions at the worst moments

Anthropic doesn’t publish exact token quotas for Pro users, but the pattern is unmistakable. A session that starts with architectural discussion, then moves to implementation, will expire right as the code needs testing or the analysis requires a final integration. The cutoff feels arbitrary because it is arbitrary: the system meters tokens over a rolling window, and once you exceed the window, the model simply stops. There’s no warning, no “you have ten messages left” indicator that adapts to message length. You are coding, you send a follow-up, and the UI tells you to wait.

The damage isn’t just the forced pause. A truncated interaction often leaves behind a half-finished artifact. If the model was generating a spreadsheet or a long function and the cap is reached mid-generation, the output is incomplete. Resuming from a summary does not preserve the same fidelity; several users note that the summary itself consumes a comparable number of tokens to the full context, meaning you pay twice for the same session without recovering the lost momentum. This defeats the efficiency the feature is supposed to provide.

When a project is complex enough that you rely on Claude to hold multiple files and constraints in its context window, a mid-task cutoff is not just an inconvenience. It forces a full session restart, manual re-injection of the plan, and a prayer that the model’s interpretation of your intentions remains consistent. In collaborative programming, that kind of reset would be considered a failure of the pair-programming arrangement.

Why users feel they cannot trust Claude for real work

The call of “every time” reveals a deeper erosion of trust. You stop treating Claude as a reliable partner when you cannot plan a session around a predictable budget. The mental model shifts from “I’ll work with Claude to solve this” to “I’ll try to squeeze what I can before the clock runs out.” That scarcity mindset degrades the quality of the interaction: you rush, you skip exploratory questions, and you avoid having the model double-check its own work.

Scott Alexander recently argued that AI “hallucinations” are better understood as shameless guesses: the model has been trained to predict, and it guesses because there is no penalty for being wrong. Claude’s usage problem has a parallel. The model’s design encourages it to be helpful by generating abundant output, sometimes far more than you requested. A user reports that Claude, given a prompt to analyze numbers, took ten minutes to produce an entire spreadsheet that wasn’t asked for, burning $8.50 in API credits. This is a shameless guess about what you might want, and it devours quota before you can intervene. The model isn’t malicious; it’s executing its default “be helpful” training signal without awareness of your budget constraint.

When the billing or usage cap is metered per token and the model generates verbosely, the user bears the cost of the model’s over-helpfulness. That’s a misalignment of incentives. Anthropic can reduce hallucination and improve reasoning, but if Claude still writes epic treatises when you needed two sentences, the trust problem remains. You can’t rely on a tool that sometimes chooses to spend your finite resource on a guess.

The hidden cost nobody calculates when choosing a Pro plan

The official feature set of Claude Pro lists “5x more usage than free” and “priority access during peak times.” Nowhere does the marketing page quantify the cost of interrupted sessions. That cost is real and accumulates over a month. A developer who uses Claude for daily coding might lose twenty to thirty minutes per disruption re-uploading context and re-establishing the thread. Multiplied across dozens of sessions, that’s hours of unpaid, invisible labor. The subscription price looks cheap, but the time tax is high.

This hidden cost also distorts how users evaluate the model’s intelligence. A model that could solve a problem in three turns if left alone might need six because two of those turns were wasted recovering from a cutoff. The perceived sluggishness or repetitiveness is sometimes not the model’s fault; it’s the byproduct of a fragmented dialogue. Benchmarks that test isolated prompts in a single turn miss this entirely. They report accuracy, but not continuity. In a world where real work spans dozens of exchanges, continuity is a capability metric that matters as much as reasoning.

Moreover, the workarounds themselves introduce additional expense. Users who route mechanical coding tasks to a cheaper model to preserve Claude’s quota are effectively paying two subscriptions to approximate a smooth experience with one. The economic calculus shifts: the effective cost of a “reliable” AI coding assistant is the sum of multiple tools and the time spent orchestrating them. That premium isn’t advertised.

The variable no AI benchmark measures: continuity

George Hotz recently argued that the real singularity is the community networks and ad-hoc tooling that transform raw AI into something useful. Claude’s rate limits have spawned exactly that kind of grassroots ingenuity: users devise systems that persist a plan to disk before every major prompt, that split workloads across multiple AI providers using separate quota pools, and that write small scripts to checkpoint context so resumption is nearly free. These are clever solutions, but they are born of failure. The platform’s inability to provide continuous, bounded assistance forced users to become process engineers.

The true measure of an AI assistant’s usability should include a metric like “session completion rate” or “hours of uninterrupted productive flow.” No benchmark slate does this. Vectara’s HHEM evaluates summarization hallucination; RAGTruth looks at faithfulness when integrating retrieved documents; TruthfulQA measures closed-book factuality. None of them penalize a model for stopping mid-sentence because of an API throttle. Yet a typical professional session with Claude can involve dozens of steps, each contingent on the previous one. A tool that can’t be relied on to finish a thought introduces a failure mode orthogonal to intelligence but equally limiting.

Anthropic has invested heavily in alignment research and in beating hallucination benchmarks. Those efforts matter, but they tackle problems that occur inside the model. The rate-limit problem occurs at the service boundary and is entirely within Anthropic’s control to fix through design. A more continuous experience would not require new training runs or architectural breakthroughs; it would require a rethinking of how usage is metered and how sessions are buffered.

What if Anthropic let you finish your thought?

The simplest solution sits in plain sight: allow an “overdraft” that lets the current task complete, with the excess usage deducted from the next refresh. The model already counts tokens; it could, upon reaching the threshold, grant a grace buffer equal to the size of the last message or the estimated completion cost of an ongoing generation. The user would never see a mid-paragraph cutoff again, and Anthropic would still enforce the agreed quota over the window. This is a product decision, not a technical impossibility.

A deeper redesign would allow users to set a “task budget” at the start of a session: “I need 200,000 tokens for this project; warn me at 80% usage, then let me finish.” The metering becomes predictable and user-controlled, aligning the incentive structure: the user plans around a known budget, the model doesn’t overspend on shameless verbosity, and completion is assured. Workflows that today require manual segmentation across multiple tools would collapse into a single conversation.

The community has already demonstrated that this is feasible by building their own systems. The question for Anthropic is whether it will continue to treat the rate limit as an immutable constraint or recognize it as the user’s primary gripe, even as models get smarter. Lower hallucination rates win paper citations, but uninterrupted sessions win daily loyalty. If Claude frustrates its most dedicated users with every long session, it risks training those users to look elsewhere, not because another model is more accurate, but because another service respects their time.

Anthropic Pentagon Contract: A Moral Stand or a Moving Target?