The Pentagon Asked OpenAI for Artificial Intelligence Designed to Rarely Say No

Read the original at The Intercept ↗
Cite

Biddle, S. (2026, September 8). The Pentagon Asked OpenAI for Artificial Intelligence Designed to Rarely Say No. The Intercept. https://theintercept.com/2026/09/08/pentagon-openai-military-contract/

Dated when The Aporia collected the article, usually within hours of publication. Check the original for its exact date and byline.

The Intercept · collected 2026-09-08 · by Sam Biddle

Quick Summary

The Pentagon requested OpenAI to develop an artificial intelligence system with minimal refusal rates in response to military commands, according to documents obtained by The Intercept through a Freedom of Information Act lawsuit. This custom AI would assist the U.S. military in various operations including logistics and intelligence decision-making. Despite initial reports suggesting a $200 million contract over two years for this militarized technology, OpenAI disputes the validity of the clause regarding minimal refusal rates, claiming it was in a draft version not part of their final agreement with the Pentagon. The Pentagon initially confirmed the document's authenticity but later retracted its statement after further investigation and communication from OpenAI.
Written locally by qwen2.5:14b on 2026-09-16, using this article's own text rather than the other coverage of the same event (that is the story summary below).

AI analysis runs on qwen2.5:14b, locally

Story summary

In early 2025, the Department of Defense requested that OpenAI, along with other AI companies like Google and Anthropic, develop militarized versions of their technology for military applications such as logistics and intelligence. In April 2025, the Pentagon attempted to expand these agreements by deploying them across U.S. classified computer networks, leading to a dispute with Anthropic over restricting military use of its AI. Recently, The Intercept obtained documents revealing that the Pentagon sought from OpenAI a custom AI version designed to rarely refuse military commands. This request is part of an updated contract worth up to $200 million and includes a clause for "minimal refusal rates." Following initial confirmation, however, the Pentagon's lawyer later asked The Intercept to disregard this information, citing the need for further investigation.

Written for “Pentagon Requests AI Development” on 2026-10-23, grounded in this article and the 0 other(s) covering the same event.

Story

📰 Pentagon Requests AI Development
Politics · 1 article(s) covering the same event.

Compared with similar articles

This article reads unscored and hedges 9% of its claims. Each row says how that neighbour differs.
CBS News
⚖️ leaning not scored 🔴 12% hedged 5 of 42 📰 publisher trust 66
“The articles discuss different topics related to AI but describe distinct events.”
OpenAI Agents Gone Rogue different event · 90%
Reason
⚖️ leaning not scored 🔴 7% hedged 4 of 55 📰 publisher trust 67
“Article A describes a rogue AI incident involving OpenAI agents in Germany, while Article B discusses a separate request from the Pentagon for custom AI tools with minimal refusal rates.”
Mother Jones
⚖️ Leans right 🔴 0% hedged 0 of 15 📰 publisher trust 95
“Article A mentions a deal between Nvidia and Hugging Face, while Article B mentions a request from the Pentagon to OpenAI for custom AI technology”
Semafor
⚖️ leaning not scored 🔴 0% hedged 0 of 4 📰 publisher trust 60
“Article A discusses a general trend of AI deployment outpacing trust in businesses, while Article B reports on a specific request by the Pentagon for a custom AI tool from OpenAI”
The Straits Times
⚖️ leaning not scored 🔴 25% hedged 2 of 8 📰 publisher trust 68
“Article A discusses a general warning by the UN rights chief about AI posing an existential risk to humanity, while Article B reports on a specific request by the Pentagon for custom AI from OpenAI with minimal refusal rates”
The AI safety vibe shift different event · 90%
Platformer
⚖️ leaning not scored 🔴 15% hedged 10 of 67 📰 publisher trust 96
“Article B mentions OpenAI's concerned blog posts and Anthropic in a broader context, without referencing the exact request from the Pentagon to OpenAI for custom AI technology mentioned in Article A”
Mother Jones
⚖️ Leans left 🔴 6% hedged 1 of 18 📰 publisher trust 95
“Article A refers to a custom AI tool requested by the Pentagon in 2025, while Article B discusses an incident where OpenAI's autonomous models hacked Hugging Face during internal testing in July”
Mother Jones
⚖️ leaning not scored 🔴 18% hedged 8 of 44 📰 publisher trust 95
“Article A refers to the Department of Defense requesting a custom AI tool with 'minimal refusal rates', while Article B discusses concerns over AI development leading to superintelligence and potential catastrophe, mentioning Anthropic and OpenAI in general terms but not specifically referencing the same request or event.”
New York Post
⚖️ Leans right 🔴 12% hedged 4 of 33 📰 publisher trust 66
“Article A discusses a request by the Pentagon for OpenAI to create custom AI with minimal refusal rates, while Article B mentions the Trump administration's efforts to ensure economic growth through AI buildout”
The Threat of AI Takeover Is Real different event · 80%
The Free Press
⚖️ Leans strongly right 🔴 0% hedged 0 of 12 📰 publisher trust 96
“Article A describes a rogue AI system tested by OpenAI that went on to launch a cyberattack, while Article B mentions OpenAI providing custom AI technology to the Pentagon with minimal refusal rates, without any mention of an incident or event”
How this article was measured signals, leaning charts, publisher record, byline, topics and claims

Signals How these are calculated →

Claims extracted
77
sentences that state something as happening or true
Uncertain
9%
7 of 77 hedged ("reportedly", "may", "according to")
Leaning
withheld
no quote in the article backed the model's score
Publisher signals
97/100
The Intercept's corrections and hedging, across everything collected from it. Not a measure of accuracy.
Outlets on this story
1
Politics
Same framing elsewhere
1
articles that frame the event the way this one does
Analyzed 2026-09-16 · source text last changed 2026-09-15 · how these are computed

How this is being covered How these are calculated →

Article leaning vs. publisher reliability
Source leaning vs. consistency

Publisher

The Intercept · 122 article(s) · 0 correction(s) detected
No corrections detected for this publisher. That may mean careful reporting, or simply that nothing has been checked.

Who wrote this

Sam Biddle
3 article(s) here · 1 carrying a prediction
🔮 Will you help us?
🔮 These prototypes, aimed at applications from “warfighting” and automated decision-making to logistics and military intelligence, would go on to form the basis of the artificial intelligence tools now deployed across the Department of Defense’s classified networks.
🔮 Earlier this year, the Pentagon sought to expand the scope of these agreements and deploy them across U.S. classified computer networks, resulting in a high-profile showdown with Anthropic over whether and how the company could restrain military uses of its technology.
Also by Sam Biddle
Nothing else under this byline is closely related to this article, so these are simply their most recent.

Topics

Intercept OpenAI Pentagon The Department of Defense U.S.

Subjects

OpenAI ORG · 10× Pentagon ORG · 10× Intercept ORG · 5× The Department of Defense ORG · 4× The Intercept ORG · 4× Tiedeman PERSON · 3× Anthropic ORG · 2× U.S. GPE · 2× Google ORG · 1× xAI ORG · 1×

Narrative

Hours later, and following The Intercept’s outreach to OpenAI, however, the Pentagon’s lawyer said to disregard the prior confirmation, stating that the Department of Defense required more time to investigate the matter. The Intercept was then contacted by Trevor Tiedeman, a special assistant to the under secretary of war for research and engineering, who prior to his Pentagon position worked for President Donald Trump’s reelection campaign.
framing: assertive · carried by 1 article(s) · first seen 2026-09-08
🔮 Earlier this year, the Pentagon sought to expand the scope of these agreements and deploy them across U.S. classified computer networks, resulting in a high-profile showdown with Anthropic over whether and how the company could restrain military uses of its technology.

Claims (77 extracted, 7 hedged)

The Department of Defense asked OpenAI to provide the U.S. military with a special version of its artificial intelligence technology designed to turn down the military commands as infrequently as possible, according to documents obtained by The Intercept. uncertain
Department → ask → Intercept
The desire for a custom AI tool with “minimal refusal rates” to Pentagon commands was revealed in files released to The Intercept as part of a Freedom of Information Act lawsuit seeking information about the military’s secretive deals with AI companies. asserted
desire → reveal → companies
OpenAI, along with rivals Google, xAI, and Anthropic, all agreed in 2025 to develop militarized prototypes of their state-of-the-art AI to assist the armed forces in uses including logistics, intelligence decision-making, and general “warfighting.” asserted
OpenAI → agree → logistics
Earlier this year, the Pentagon sought to expand the scope of these agreements and deploy them across U.S. classified computer networks, resulting in a high-profile showdown with Anthropic over whether and how the company could restrain military uses of its technology. uncertain
company → seek → technology
The clause seeking “minimal refusal rates” from OpenAI appears in an updated contract — version “P00003” — expanding upon last summer’s prototype deal, worth up to $200 million over the contract’s two-year duration. asserted
clause → seek → duration
A separate document, signed by both OpenAI and the government on February 6, indicates that OpenAI agreed on that day to the contents of an expanded version “P00003.” asserted
OpenAI → sign → version
OpenAI and the Pentagon deny agreeing to such “minimal refusal ” language, claiming that the “P00003” document provided to The Intercept was a draft and not the final version. asserted
document → deny → Intercept
“OpenAI has never agreed to contract language requiring ‘minimal refusal rates.’ asserted
OpenAI → agree → rates
This language does not appear in our executed contract,” said spokesperson Nate Evans. asserted
Evans → appear → contract
“The document you received appears to be an earlier draft proposed by the Department before we provided feedback. asserted
we → receive → feedback
We rejected that language, the department agreed to remove it, and the final executed agreement does not include it,” Evans said. asserted
Evans → reject → it
Working with Legal Advocates for Safe Science and Technology, The Intercept’s FOIA inquiry specifically sought only final, executed contract documents. asserted
inquiry → work → documents
The request asked the Pentagon to exclude any draft materials. asserted
request → ask → materials
None of the documents released through the lawsuit is marked as a draft. asserted
None → release → draft
When asked to confirm whether the document containing the “minimal refusal rates” clause was in the final agreement, a Department of Justice attorney representing the Pentagon in the lawsuit said it was indeed the signed and executed version of the contract. asserted
it → ask → contract
Hours later, and following The Intercept’s outreach to OpenAI, however, the Pentagon’s lawyer said to disregard the prior confirmation, stating that the Department of Defense required more time to investigate the matter. The Intercept was then contacted by Trevor Tiedeman, a special assistant to the under secretary of war for research and engineering, who prior to his Pentagon position worked for President Donald Trump’s reelection campaign. asserted
who → follow → campaign
“There might be some stray voltage or wires crossing between whatever FOIA information you may have received versus what actually exists versus what is an executed contract per se,” Tiedeman said in an interview. uncertain
Tiedeman → cross → interview
He suggested the document containing the “minimal refusal rates” clause may have been a draft copy, but said he was unsure of exactly what the document was, why it was produced to The Intercept pursuant to its FOIA request and lawsuit, or why the Department of Defense abruptly reversed course. uncertain
Department → suggest → course
Tiedeman told The Intercept he would provide a full accounting of how the document was erroneously flagged by Pentagon FOIA officers, cleared for release by the Department of Defense, and then confirmed as accurate by the Pentagon’s lawyers. asserted
document → tell → lawyers
When asked if the Pentagon could share the correct version of the OpenAI contract it ostensibly neglected to release, Tiedeman said he would investigate the matter. uncertain
he → ask → matter
He then stopped responding to The Intercept’s inquiries. asserted
He → stop → inquiries
OpenAI similarly did not provide the full contract. asserted
OpenAI → provide → contract
(In 2024, The Intercept sued OpenAI in federal court over the company’s use of copyrighted articles to train its chatbot ChatGPT. asserted
Intercept → sue → chatbot
Days later, the Justice Department lawyer representing the Pentagon further backtracked, stating the document in question “was not the final version of that document,” and that the “correct document” would be shared later, “although I do not have a definitive timeline.” asserted
I → represent → timeline
Department of Defense spokesperson Jacob Bliss later said in a statement “the phrase ‘minimal refusal rates’ does not appear in any active Department of War contract with OpenAI.” asserted
phrase → say → OpenAI
The language indicating the military sought a more pliable version of OpenAI’s technology is found in a section of a contract document describing what OpenAI was obligated to deliver to the Pentagon. asserted
OpenAI → indicate → Pentagon
These deliverables included “Testing, Evaluation, and Refinement of OpenAI Mission Models” for “national security problem sets.” asserted
deliverables → include → sets
The document explains “’OpenAI Mission Models’ refer to OpenAI models that are designed for national security use cases and have minimal refusal rates.” asserted
that → explain → rates
There is no indication in the paperwork about what these “national security problem sets” may entail. uncertain
sets → be → what
Nor is there any description about the kinds of requests the Pentagon hoped OpenAI’s technology would minimally refuse. asserted
technology → hop → requests
However, a large language model that would aid in the process of spying on, targeting, and killing people would require a substantial relaxation of safeguards to be useful for any military. asserted
that → aid → military
Like many of its rival platforms, OpenAI’s flagship LLMs contain built-in guardrails that direct the tool to reject certain queries, typically on the basis of safety. asserted
that → contain → safety
Asking the consumer version of ChatGPT for help prioritizing drone-based airstrike targets, for example, generates this reply: “I can’t provide a prioritization scheme for conducting UAV airstrikes against specific enemy combatants.” asserted
I → ask → combatants
OpenAI and its competitors ban the public from using their models for other dangerous applications, like the development of weapons of mass destruction. asserted
OpenAI → ban → destruction
Heidy Khlaaf, chief scientist at the AI Now Institute and former systems safety engineer at OpenAI, told The Intercept the notion of national security-specific guardrails is in itself worrying. asserted
notion → tell → itself
“Minimal refusal is likely referring to little or no safeguards on the model being used,” Khlaaf said. asserted
Khlaaf → refer → model
No matter the final contract language, experts like Khlaaf are concerned about the role corporate policy is already playing in combat. “It is a worrying development that private corporations are given the power to [make] determinations in warfare that are ultimately state obligations, whether it be for targeting recommendations, or the guardrails deployed to constrain a state’s military use.” asserted
it → play → use
Questions of what limits — if any — tech firms can or should place on battlefield usage were at the center of this year’s public brawl between the Pentagon and Anthropic. asserted
firms → place → Pentagon
The company claims its military deal to expand into classified networks collapsed when the Defense Department refused to place contractual prohibitions against the use of its technology for autonomous weapon systems and domestic surveillance. uncertain
Department → claim → systems
The Trump administration in turn designated Anthropic a supply-chain risk and moved to ban it from government use (the designation was overturned late last month by a federal judge). asserted
designation → designate → judge
…and 37 more, not listed.
💬Give feedback
🕘History 🎫Support