War Powers

The Founders wanted war to require broad agreement from the people’s representatives, not one person’s judgment.

When the president decides to go to war

War powers are the constitutional authorities to initiate, conduct, and end military conflicts. The Constitution divides these powers between Congress and the president: Congress declares war and funds the military, the president commands the armed forces once war is declared.

This division was deliberate. The Founders had just escaped a king who could drag the nation into wars on royal whim. They wanted war—the most consequential decision a government makes—to require broad agreement from the people’s representatives, not one person’s judgment.

Where Is It in the Constitution?

The Constitution (Article I, Section 8) is crystal clear: Congress has the power “To declare War.” Not the president. Congress. The Founders were absolutely explicit about this because they’d just escaped a king who could drag them into wars on a whim.

Here’s what actually happens: Presidents bomb countries. Launch drone strikes. Deploy troops. Start conflicts that last decades. And Congress? Congress holds hearings where they complain they weren’t consulted, then they fund the war anyway. The Constitution says one thing. Reality is completely different.

The United States has been at war for 225 out of 250 years of its existence. Congress has formally declared war exactly 5 times. The last declaration was in 1942. We’ve been bombing countries continuously since then. Congress just… stopped declaring war.

Where Does This Come From?

The Constitutional Convention of 1787 debated war powers extensively. The original draft gave Congress the power to “make war.” James Madison and Elbridge Gerry proposed changing it to “declare war” to preserve the president’s ability to “repel sudden attacks”—defensive action only.

Pierce Butler of South Carolina proposed giving war power solely to the president. The Convention rejected this decisively. George Mason of Virginia explained why: “The purse & the sword ought never to get into the same hands.”

The distinction was clear: Congress decides whether to go to war. The president commands the military once Congress makes that decision. Alexander Hamilton explained in Federalist No. 69 that the president’s war powers were “much inferior” to those of the British king, amounting to “nothing more than the supreme command and direction of the military and naval forces.”

James Madison later wrote: “The constitution supposes, what the History of all Governments demonstrates, that the Executive is the branch of power most interested in war, and most prone to it. It has accordingly with studied care vested the question of war in the Legislature.”

The Last Five Declarations

Congress has formally declared war exactly five times in American history:

  1. War of 1812
  2. Mexican-American War (1846)
  3. Spanish-American War (1898)
  4. World War I (1917)
  5. World War II (1941—against Japan, Germany, Italy, Bulgaria, Hungary, and Romania)

Since 1942: zero declarations. Hundreds of military actions.

How the System Broke Down

The erosion happened gradually, through workarounds that became precedents that became normal.

Korea (1950): President Truman committed troops without congressional authorization. He called it a “police action” under United Nations authority, not a war. The conflict lasted three years and killed 36,000 Americans. It’s still technically ongoing—there’s an armistice, not a peace treaty. Congress never voted.

Vietnam (1964): President Johnson asked Congress for authority to use military force in Southeast Asia after alleged attacks on U.S. ships in the Gulf of Tonkin. Congress passed the Gulf of Tonkin Resolution—not a declaration of war, but an authorization to use force. The attacks that justified it were questionable at best, fabricated at worst. The war lasted eleven years, killed 58,000 Americans, and continued for four years after Congress repealed the resolution in 1971.

The lesson presidents learned: Don’t ask for a declaration of war. Ask for an authorization. It’s easier to get, harder to define, and can be stretched indefinitely.

The 2001 Blank Check

Three days after September 11, 2001, Congress passed the Authorization for Use of Military Force (AUMF). The resolution authorized the president to use “all necessary and appropriate force” against those responsible for the attacks.

It passed 98-0 in the Senate, 420-1 in the House. Representative Barbara Lee of California cast the only vote against it, warning: “We must be careful not to embark on an open-ended war with neither an exit strategy nor a focused target.”

She was right.

The 2001 AUMF is still in effect twenty-four years later. It has been used to justify military operations in Afghanistan, Iraq, Syria, Libya, Somalia, Yemen, Niger, and more. Presidents have stretched it to cover groups that didn’t exist on 9/11—groups that formed years later, in different countries, fighting for different causes.

The AUMF authorized force against Al-Qaeda. Presidents have since used it to justify operations against:

None of these groups existed on 9/11. Congress never voted to authorize force against them. But the 2001 AUMF somehow covers all of them, because presidents say it does.

In 2002, Congress passed a second AUMF authorizing force against Iraq based on claims that Saddam Hussein possessed weapons of mass destruction. The WMDs didn’t exist. The Iraq War officially ended in 2011. The 2002 AUMF remains on the books.

The Expansion of Presidential War Powers

Modern presidents claim sweeping authority to use military force based on:

Article II authority: The president’s constitutional role as Commander in Chief supposedly grants inherent power to use force to protect American lives, defend national security, and respond to threats—no congressional approval needed.

Existing authorizations: The 2001 and 2002 AUMFs can be stretched to cover almost anything if you squint hard enough and define “associated forces” broadly enough.

Self-defense: Any action can be justified as defending Americans or American interests somewhere in the world.

Speed and secrecy: Modern threats require immediate response; congressional debate takes too long and telegraphs plans to enemies.

These justifications have no limiting principle. Any threat anywhere becomes grounds for military action. The president decides what constitutes a threat, when force is necessary, and how long operations continue. Congress finds out when bombs start falling.

The result: Presidents conduct wars across multiple continents without congressional declarations. They maintain that these aren’t “wars”—they’re counterterrorism operations, limited strikes, or support missions. The distinction is semantic. People die. Cities are bombed. Conflicts drag on for years. But they’re not officially “wars,” so the constitutional requirement that Congress declare them doesn’t apply.

The War Powers Resolution was supposed to force regular congressional involvement. Instead, it created a framework for presidents to ignore Congress for 60 days, then just keep going because Congress won’t enforce the deadline.

The Pattern Across Administrations

This isn’t about one president or one party. The expansion of presidential war powers has been bipartisan and incremental. Each president inherits expanded authority from the previous one and expands it further for the next.

Democratic and Republican presidents alike have:

The presidency has accumulated war-making authority the Founders explicitly denied it. Not through constitutional amendment. Not through formal legal change. Through precedent, acquiescence, and Congress’s refusal to enforce its own powers.

If we restored the Constitution’s original design—Congress declares war, the president executes it—we’d lose presidential flexibility to respond to threats without waiting for congressional debate.

Defenders of expanded presidential authority argue:

These arguments aren’t new. Kings made identical claims: only they could act decisively, only they understood threats, only they could protect the realm. That’s exactly why the Founders gave war power to Congress.

Congress can authorize force quickly when necessary. They did it in three days after 9/11. The problem isn’t that Congress can’t act fast—it’s that presidents don’t want to ask permission.

The Founders didn’t create these restrictions because they wanted to make national defense difficult. They created them because they knew unchecked executive power over war and peace leads to endless wars fought for reasons the public never approved.

What We Actually Have

A president can bomb any country, any time, for any reason they claim relates to national security or existing authorizations. Congress will complain, hold hearings, and fund it anyway. The troops fight. The costs mount. And no one actually votes to say “yes, this war serves American interests.”

Twenty-four years of war under the 2001 AUMF. Trillions spent. Thousands dead. And Congress has never once voted to end it.

The Constitution gives Congress the power to declare war. Congress gave that power to the president and pretends it didn’t. This isn’t a subtle erosion of checks and balances—it’s an explicit abandonment of the Founders’ most important safeguard against executive overreach.

Article I, Section 8 says Congress declares war. We’re currently conducting military operations in multiple countries. Congress has declared zero of them. The Constitution says one thing. We do another. And we pretend this is normal.

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *