How Congress Lost Control of America’s Wars

Last updated 1 week ago ago. Our resources are updated regularly but please keep in mind that links, programs, policies, and contact information do change.

An Authorization for the Use of Military Force sounds like bureaucratic paperwork. But these little-known congressional resolutions have become the legal foundation for America’s longest wars.

An AUMF is a joint resolution passed by both houses of Congress and signed by the President. It grants the President legal authority to deploy American troops into combat, according to Military.com.

Since World War II ended, the AUMF has become the only way America formally starts major military conflicts. It has completely replaced the constitutional declaration of war that the founders envisioned.

A declaration of war triggers a formal state of war under international law. An AUMF authorizes more limited force, though the limits are often vague, as explained by Cornell Law School.

Two AUMFs passed after September 11, 2001 have fundamentally reshaped American warfare. They’ve served as the legal foundation for military operations across the globe for over two decades.

Their broad language and expansive interpretation by successive presidents have placed them at the center of an intense constitutional debate over war powers, executive authority, and congressional responsibility, according to the Open Society Foundations.

The Constitutional Tug-of-War

The framers of the Constitution deliberately created overlapping war powers between Congress and the President. They wanted the decision to go to war to be a collective judgment, not the choice of one person.

This constitutional ambiguity has fueled a centuries-long struggle between Congress and the President. The AUMF has become the primary modern tool for navigating this contested space.

The Framers’ Plan

The founders were acutely aware that monarchs and executives tend to drag nations into costly wars. James Madison, a chief architect of the Constitution, wrote that “the Executive is the branch of power most interested in war, and most prone to it,” according to the Friends Committee on National Legislation.

So they split military powers between the branches. Article I, Section 8 gives Congress crucial military powers, including the authority to raise armies, maintain a navy, and most importantly, the sole power “to declare War.”

This was meant to ensure that any decision to start a war could only be made through deliberation by the branch most accountable to the American people.

At the same time, the framers recognized the need for unified military command once war began. Article II, Section 2 makes the President “Commander in Chief of the Army and Navy.”

This gives the President authority to direct the military during conflict. The Commander in Chief power also includes an inherent right to defend against sudden attacks.

Constitutional debate notes from Madison and Elbridge Gerry clarify that giving Congress the power to “declare war” would still leave “to the Executive the power to repel sudden attacks.”

The Supreme Court confirmed this in the Prize Cases of 1863, ruling that if the nation is invaded, the President is “bound to resist force by force…without waiting for any special legislative authority.”

This structure creates what the House Foreign Affairs Committee calls a “twilight zone of concurrent authority.” Congress can initiate and fund war, while the President conducts it and defends the nation.

This deliberate ambiguity set up a continuous struggle over where one branch’s authority ends and the other’s begins.

Declaration vs. AUMF

The practical difference between a formal declaration of war and an AUMF is substantial.

A declaration of war is a formal act that triggers a “state of war under international law,” according to the Congressional Research Service. It authorizes “total war” – the full and unqualified use of the U.S. military against a specified enemy, typically another nation.

It’s the most constitutionally clear grant of war-making authority. But it has become extremely rare.

Congress has passed a formal declaration of war only 11 times in five conflicts. The first was the War of 1812. The most recent were the declarations against Japan, Germany, Italy, and other Axis powers in 1941 and 1942.

An AUMF is different. It’s a statutory force authorization passed as a joint resolution. The Supreme Court has long held that Congress can authorize not just “general hostilities” but also “partial hostilities” or “limited war.”

An AUMF is the modern tool for authorizing such limited conflicts. Unlike a declaration of war, an AUMF can be constrained with specific instructions about the region, nation, or individuals against whom force can be used.

It authorizes “all necessary and appropriate force” rather than the total war implied by a formal declaration.

The shift away from declarations of war is stark. Since World War II, every major U.S. military conflict has been initiated through an AUMF or unilateral presidential action, not a declaration of war.

This change partly reflects the evolution of international law. The United Nations Charter, ratified after WWII, prohibited war as a tool of foreign policy, except in self-defense or when authorized by the UN Security Council.

Alexander Hamilton noted as early as 1787 that formal declarations had already begun falling out of use. The UN Charter accelerated this trend, making them largely obsolete in modern international relations.

The AUMF became the modern, more flexible legislative tool for granting the President authority to send troops into combat.

But there’s a paradox. This tool designed for “limited war” has enabled conflicts of seemingly unlimited duration and scope.

A formal declaration of war against a nation like Germany or Japan has a clear endpoint: the surrender or defeat of that state. The 2001 AUMF, however, authorized force against “organizations or persons.”

This created a legal framework for conflict that lacks a clear mechanism for termination. Non-state actors like al-Qaeda don’t surrender the way nations do.

The result is that the AUMF became the legal basis for a multi-generational, global conflict – far more enduring than what a traditional declaration against a specific country would have produced.

The War Powers Resolution Backfires

In 1973, Congress tried to reclaim its war powers with the War Powers Resolution. Instead, the law’s failures inadvertently encouraged presidents to seek broad, open-ended AUMFs.

Fighting the “Imperial Presidency”

The impetus for the War Powers Resolution was congressional frustration over two major undeclared wars. Heavy U.S. involvement in Korea and Vietnam occurred without formal declarations of war from Congress.

Presidents Kennedy, Johnson, and Nixon successively committed U.S. troops to Southeast Asia with minimal congressional input. Many in Congress saw this as a dangerous erosion of their constitutional role.

The breaking point came with the revelation of secret U.S. bombings of Cambodia, ordered without congressional consent or knowledge. This action, seen as the pinnacle of the “imperial presidency,” catalyzed Congress to act.

The resulting War Powers Resolution was designed “to fulfill the intent of the framers of the Constitution…and insure that the collective judgment of both the Congress and the President will apply to the introduction of United States Armed Forces into hostilities,” according to its text at Yale Law School.

Passed by two-thirds votes in both houses to override President Nixon’s veto on November 7, 1973, the WPR was meant to reassert Congress’s role in war decisions.

How It Was Supposed to Work

The War Powers Resolution established procedures to force collaboration between the branches:

Consultation: The President must consult with Congress “in every possible instance” before introducing U.S. Armed Forces into hostilities. “Consultation” was meant to be substantive – seeking advice from Congress, not just notification after a decision.

Reporting: Without a declaration of war, the President must submit a written report within 48 hours of introducing armed forces into hostilities, foreign territory while “equipped for combat,” or in numbers that “substantially enlarge” existing combat forces.

Termination: This is the heart of the WPR. Submitting a report about forces in hostilities starts a 60-day clock. The President must terminate military force within 60 days unless Congress declares war, passes a “specific statutory authorization” (an AUMF), or extends the 60-day period. An additional 30 days is allowed for safe withdrawal if certified as necessary.

A History of Failure

Despite clear intent, the War Powers Resolution has been controversial since enactment. No president has ever fully accepted its constitutionality.

Presidents from both parties have consistently challenged, sidestepped, or ignored its provisions. While sitting presidents have submitted over 132 reports to Congress since 1973, these are often framed as being “consistent with” the WPR rather than “pursuant to” its requirements.

This careful legal distinction avoids triggering the 60-day clock.

A central weakness lies in the ambiguity of key terms. The executive branch frequently adopts narrow interpretations of what constitutes “hostilities” to avoid the resolution’s requirements.

The Obama administration argued in 2011 that sustained U.S. bombing in Libya didn’t amount to “hostilities” because of limited risk to U.S. forces. This interpretation was widely disputed.

This pattern of non-compliance led many to conclude that the WPR has largely failed to meaningfully constrain presidential war-making.

The Unintended Consequence

The War Powers Resolution’s failure created a strategic vacuum. The law was designed to force congressional debate after a president committed troops. Its primary enforcement mechanism was the 60-day termination clock.

But by seeking a broad, open-ended AUMF before starting a conflict, a president could neutralize the WPR’s main provision from the outset.

The 2001 and 2002 AUMFs explicitly state that they constitute the “specific statutory authorization” required by the War Powers Resolution. Because these AUMFs contained no expiration date, the 60-day clock never became relevant.

The very statute designed to limit presidential war power inadvertently created a powerful incentive for the executive branch to seek sweeping, front-loaded authorizations. These became the foundation for America’s “forever wars.”

The Post-9/11 AUMFs

In the aftermath of September 11, 2001, and again a year later before the Iraq invasion, Congress passed two of the most consequential military authorizations in U.S. history.

These resolutions, born of different crises and political circumstances, established the legal architecture for more than two decades of global military operations.

The 2001 AUMF

The 2001 AUMF was forged in a moment of national trauma and unity. Following the attacks on the World Trade Center and Pentagon, the Bush administration sought swift authority from Congress to respond.

The resulting joint resolution, S.J.Res.23, moved through Congress with unprecedented speed and near-unanimous consent.

It was introduced in the Senate on September 14, 2001, passed both chambers the same day (98-0 in the Senate, 420-1 in the House), and was signed into law by President Bush on September 18, 2001.

At the heart of the law is a single, 60-word sentence that has served as the primary legal basis for U.S. counterterrorism operations ever since.

Section 2(a) states: “That the President is authorized to use all necessary and appropriate force against those nations, organizations, or persons he determines planned, authorized, committed, or aided the terrorist attacks that occurred on September 11, 2001, or harbored such organizations or persons, in order to prevent any future acts of international terrorism against the United States by such nations, organizations or persons.”

Despite the sweeping power this language grants the President to “determine” targets, the final text was actually a compromise.

The Bush administration initially proposed even broader authorization that would have empowered the president to “deter and pre-empt any future acts of terrorism or aggression against the United States.”

Congress pushed back against this open-ended language even in crisis. Lawmakers refused to declare a broad “war on terrorism” and instead insisted on tying force directly to the 9/11 perpetrators and those who harbored them.

At the time, this was understood to mean al-Qaeda and the Taliban regime in Afghanistan. The final resolution was intended to be targeted, not a global blank check.

The 2002 Iraq AUMF

A year later, Congress considered another AUMF in a very different political environment. The 2002 Authorization for Use of Military Force Against Iraq wasn’t a response to direct attack but authorization for potential preemptive war.

The Bush administration spent much of 2002 building a case that Saddam Hussein’s regime posed a grave threat due to alleged weapons of mass destruction and its history of flouting UN Security Council resolutions.

The administration argued an AUMF was necessary to give credibility to diplomatic efforts and use the threat of force to pressure Hussein into compliance.

The legislative process for H.J.Res. 114 was far more deliberative and contentious than its 2001 predecessor.

Introduced in the House on October 2, 2002, it prompted vigorous debate. The resolution passed the House on October 10 by 296-133 and the Senate in the early hours of October 11 by 77-23.

While it secured substantial bipartisan support, it faced significant opposition, primarily from Democrats but also some Republicans. President Bush signed it into law on October 16, 2002.

The 2002 Iraq AUMF authorized the President to use armed forces as he determined necessary and appropriate to:

1. “defend the national security of the United States against the continuing threat posed by Iraq”
2. “enforce all relevant United Nations Security Council resolutions regarding Iraq”

Unlike the 2001 AUMF, it contained procedural constraints, requiring the President to report that diplomatic means had proven inadequate before exercising authority and to continue reporting on the conflict every 60 days.

Two Different Models

The textual differences between the post-9/11 AUMFs established two distinct models with profound implications.

The 2001 AUMF created a “status-based” authority, targeting actors based on who they are – the “nations, organizations, or persons” connected to 9/11. Combined with the President’s power to “determine” who fits that description, this proved highly adaptable.

The 2002 AUMF created a “conduct-based” authority, targeting a threat based on what it was doing – the specific threat “posed by Iraq.” Initially tied to Saddam Hussein’s regime, this language was later stretched to mean any threat from Iraq.

The status-based model of the 2001 AUMF proved far more flexible and legally durable. That’s why it, not the 2002 resolution, became the primary legal engine for the global “war on terror.”

The “Forever Wars”

What began as two distinct authorizations morphed over two decades into sprawling legal justification for a global, multi-generational military campaign.

Through expansive executive branch interpretations, these AUMFs were stretched far beyond their original congressional intent. They became the legal underpinning for America’s “forever wars.”

This expansion occurred through legal path dependency, where each administration built upon the precedents of the last, creating a ratchet effect that continuously broadened presidential war power.

The “Associated Forces” Doctrine

The most critical legal development was the executive branch’s creation of the “associated forces” doctrine.

The 60-word text of the 2001 AUMF authorizes force against those who planned or aided the 9/11 attacks. But it says nothing about “associated forces.”

This concept was an interpretation developed under President Bush and formally expanded under President Obama. The Obama administration argued that authorization to fight an enemy (al-Qaeda) implicitly includes authority to fight its co-belligerents.

It defined an “associated force” as an organized, armed group that has entered the fight alongside al-Qaeda and is a co-belligerent against the United States or its allies.

This doctrine became the legal engine that allowed the 2001 AUMF to apply to a growing list of terrorist groups that didn’t exist on September 11, 2001, and had no direct role in the attacks.

The most prominent example is ISIS. The Obama administration argued in 2014 that it could rely on the 2001 AUMF against ISIS because the group originated as an al-Qaeda affiliate in Iraq and shared a common enemy in the United States.

This interpretation was controversial because ISIS was officially disavowed by al-Qaeda’s leadership in 2014. But it became accepted legal rationale within the executive branch.

Successive administrations have continued to rely on this interpretation to target ISIS and other groups. The full list of “associated forces” often remains classified, hidden from the public and most of Congress.

A Global Battlefield

The “associated forces” doctrine transformed the 2001 AUMF from targeted retaliation for a specific attack into a flexible tool for global counterterrorism.

A 2021 analysis by Brown University’s Costs of War Project found that the 2001 AUMF has been cited to justify military operations in at least 22 countries.

Between 2018 and 2020 alone, the U.S. undertook counterterrorism activities in 85 countries, with the AUMF serving as a key legal justification.

These operations span the globe and take many forms:

Airstrikes and Combat: Sustained combat in Afghanistan and Iraq; airstrikes against ISIS in Syria and Libya; drone strikes against al-Shabaab in Somalia and al-Qaeda in the Arabian Peninsula in Yemen.

Detention: The ongoing detention of individuals at Guantanamo Bay is legally justified under the 2001 AUMF.

“Support” for Partner Forces: The AUMF has been cited to justify deploying U.S. troops to provide training, intelligence, surveillance, and reconnaissance support to partner militaries in countries like the Philippines, Niger, Cameroon, and Kenya.

This vast expansion has come at staggering cost. According to the Costs of War Project, the post-9/11 wars have cost the United States over $8 trillion and have been linked to the deaths of over 900,000 people, including hundreds of thousands of civilians.

The 2002 AUMF’s Second Life

While the 2001 AUMF became the workhorse of the “war on terror,” the 2002 Iraq AUMF was also repurposed long after Saddam Hussein’s fall.

In 2014, the Obama administration began citing it as an “alternative statutory basis” to reinforce legal authority for the campaign against ISIS in Iraq.

The argument was that the law’s authorization to defend against threats “posed by Iraq” could be interpreted to include defending the new Iraqi government from terrorist threats within its borders.

The Trump administration stretched this interpretation further. In a 2018 report, it asserted that the 2002 AUMF authorized force to address threats “to, or stemming from, Iraq,” and crucially, that it “contains no geographic limitation on where authorized force may be employed.”

This expansive view culminated in the controversial January 2020 drone strike in Baghdad that killed Iranian General Qassem Soleimani.

The administration cited the 2002 AUMF as part of its legal justification, arguing that Soleimani, through his leadership of Iran-backed militias in Iraq, posed a threat “stemming from Iraq.”

This use of an AUMF intended for Saddam Hussein’s regime to target a senior official of a different state (Iran) was widely condemned by legal scholars as an overreach of congressional authority.

Even the Biden administration, while officially supporting the 2002 AUMF’s repeal, has cited it as a secondary legal basis for recent strikes against Iran-aligned militias in Iraq and Syria.

This demonstrates the enduring power of these executive branch precedents.

The Current Debate

More than two decades after their passage, the post-9/11 AUMFs are at the center of vigorous political and constitutional debate in Washington.

A broad, bipartisan coalition is pushing to repeal or reform these authorizations, arguing they’re outdated and have enabled unconstitutional expansion of presidential war power.

They’re met with arguments that these authorities, however flawed, remain essential for national security and provide necessary flexibility.

This debate reveals a deep institutional paradox: while Congress has a constitutional interest in reclaiming its war powers, its members often have a political interest in avoiding difficult votes on war and peace that such reclamation would require.

The Case for Repeal

The movement to repeal the post-9/11 AUMFs, particularly the 2002 Iraq AUMF, is driven by a diverse coalition spanning the political spectrum.

Their arguments are rooted in constitutional principles and a desire to end “endless wars.”

Constitutional Responsibility: The core argument is that Congress must reclaim its Article I authority to decide when and where the United States goes to war.

Proponents argue that for too long, Congress has abdicated this “most solemn power,” allowing presidents of both parties to initiate and expand conflicts without specific, contemporary authorization.

Preventing Future Abuse: Leaving outdated AUMFs on the books creates dangerous temptation for future presidents to misuse them.

The Trump administration’s use of the 2002 Iraq AUMF to justify the Soleimani strike is frequently cited as a prime example of how a law intended for one purpose can be twisted to authorize an entirely different conflict.

Repealing these laws, advocates say, is about removing a loaded gun from the table.

Irrelevance and Obsolescence: The original justifications for both AUMFs are long gone.

The 2002 AUMF was passed to deal with Saddam Hussein’s regime, overthrown in 2003. The 2001 AUMF was passed to target the 9/11 perpetrators, yet it’s now used against groups that didn’t exist at the time and have little connection to those attacks.

No Impact on Current Operations: A powerful argument for repealing the 2002 Iraq AUMF is that it’s not operationally necessary.

The Biden administration, the Chairman of the Joint Chiefs of Staff, and numerous national security officials have stated that no current U.S. military operations rely solely on the 2002 AUMF as their legal basis.

The President retains inherent Article II constitutional authority to act in self-defense to repel sudden attacks, meaning repeal wouldn’t leave the country defenseless.

The Case for Retention

Opposition to straightforward repeal comes from several corners, with arguments focusing on national security flexibility and the need for modern legal framework.

Deterrence and Flexibility: Some lawmakers argue that repealing the 2002 AUMF would send a message of weakness and could embolden adversaries, particularly Iran.

They point to the Soleimani strike as evidence that the AUMF provides a useful tool for deterring Iranian aggression and protecting U.S. personnel in the region.

More broadly, proponents of retaining the 2001 AUMF argue that its flexibility is essential to combat a diffuse and evolving terrorist threat.

They contend that requiring a new congressional vote for every emerging threat would be too slow and cumbersome, risking judicial decisions that could halt critical counterterrorism operations.

The “Repeal and Replace” Position: A significant group in Congress argues not for simple repeal, but for “repeal and replace.”

This position, articulated by figures like House Foreign Affairs Chairman Michael McCaul, holds that simply repealing old AUMFs would leave a legal vacuum.

Instead, they advocate for Congress to draft a new, updated AUMF specifically tailored to today’s threats. Such authorization would clearly name enemy groups (e.g., ISIS, al-Qaeda), could include geographic limitations, and would likely include a sunset provision requiring Congress to review and reauthorize it periodically.

This approach, they argue, would both reassert congressional authority and provide the executive branch with clear, legitimate legal backing for necessary ongoing operations.

Current Status

The contemporary debate has translated into concrete legislative action and official administration policy.

Legislative Action: There is significant bipartisan momentum for repealing the older, more obsolete AUMFs.

In March 2023, the Senate passed S. 316, a bill to repeal both the 1991 Gulf War AUMF and the 2002 Iraq AUMF, by a strong bipartisan vote of 66-30.

The House has also passed standalone repeal bills in previous sessions with bipartisan support. However, the legislation has consistently stalled, often due to disagreements about whether to pursue simple repeal or a more complex “repeal and replace” strategy, particularly for the 2001 AUMF.

The Biden Administration’s Position: The executive branch’s position reflects the core tension in the debate.

The Biden administration has issued formal statements strongly supporting repeal of the 1991 and 2002 AUMFs, stating they’re not needed for any ongoing military activities and that their repeal would have “no impact on current U.S. military operations.”

However, the administration’s stance on the 2001 AUMF is markedly different. While expressing commitment to work with Congress to replace it with a “narrow and specific framework,” top officials have testified that the 2001 AUMF is “the critical one” that they “need to hang on to” to continue current counterterrorism operations.

This pragmatic position – repeal what’s not needed, but retain what is – highlights why repeal of the 2002 AUMF has gained traction while comprehensive reform of the 2001 AUMF remains elusive.

The debate over AUMFs ultimately reflects a larger question about the proper balance of power in American democracy. How much authority should one person – the President – have to commit the nation to war?

The framers of the Constitution thought this decision was too important to leave to any single individual. But in practice, Congress has found it politically convenient to let presidents make the hard choices about war and peace.

The result is a system where broad, vaguely written authorizations passed in moments of crisis become the legal foundation for conflicts that span decades and continents.

Whether Congress will reclaim its constitutional role – or continue to outsource the most consequential decisions of statecraft to the executive branch – remains an open question. The answer will shape not just American foreign policy, but the fundamental character of American democracy itself.

The stakes could hardly be higher. As one congressional aide put it, “We’re not just talking about legal authorities. We’re talking about who gets to decide when America goes to war.”

Our articles make government information more accessible. Please consult a qualified professional for financial, legal, or health advice specific to your circumstances.