Trump's Iran Strikes and the War Powers Question Congress Keeps Refusing to Answer

A Question the Founders Already Answered

Article I, Section 8 of the Constitution assigns the power to declare war to Congress. Not to the President. Not to the National Security Council. Not to a classified finding submitted to eight members of the Gang of Eight at midnight. To Congress.

That was 1787. The Founders had just fought a war against a king who made war unilaterally. They were not confused about what they were doing.

And yet here we are in March 2026, watching Congress return from recess to hold emergency hearings about strikes on Iran — strikes that, depending on which administration spokesperson you believe, either targeted nuclear infrastructure, eliminated key regime figures, or both — and the framing of the debate in Washington is almost entirely wrong. The argument is not about constitutional authority. It's about optics. It's about which party gets to be angrier. It's about the midterms.

The War Powers Resolution of 1973 was Congress's attempt to claw back authority it had been surrendering since Korea. Presidents of both parties have treated it as optional since the day it passed. Ronald Reagan ignored it in Lebanon. Bill Clinton ignored it in Kosovo. Barack Obama ignored it in Libya. The pattern is not partisan. It's institutional. The executive branch expands, and Congress complains without consequence.

The Legal Landscape After Tehran

There is a serious constitutional argument to be made that the President, as Commander in Chief, has inherent authority to respond to imminent threats without prior congressional authorization. The Justice Department has been making that argument in various forms since at least the Nixon administration, and federal courts have largely declined to adjudicate it directly — leaving the question open and the executive branch free to fill the vacuum.

That argument has limits. Even its most aggressive proponents acknowledge that sustained military campaigns, formal wars, occupations — these require congressional authorization. The question is where the strikes on Iran fall on that spectrum.

If the United States conducted a single night of precision strikes against nuclear facilities or specific command-and-control targets, the constitutional case for executive authority is genuinely defensible. Presidents have done this before and faced legal challenge — and survived it. The 1986 Libya strikes. The 1998 Sudan and Afghanistan strikes. The 2020 killing of Qasem Soleimani, which a federal court ultimately ruled did not require prior congressional authorization.

But if the strikes on Iran were broader — if they targeted civilian infrastructure, if they were designed to degrade the regime's capacity for governance rather than to neutralize a specific imminent threat — then the constitutional question becomes much harder to wave away. And Congress has both the right and the obligation to demand a full accounting.

What Congress Is Actually Doing

What Congress is not doing is passing an Authorization for Use of Military Force. It's not drafting a declaration of war. It's not invoking the War Powers Resolution's sixty-day clock in any legally meaningful way. It's holding hearings. It's issuing statements. It's dividing along party lines in a way that suggests the constitutional principle is less important than the political opportunity.

Democrats who cheered the Soleimani strike when it was politically convenient, or who voted for the 2002 AUMF that became a blank check for two decades of Middle Eastern entanglement, now discover constitutional principle when a Republican president acts. Republicans who loudly defended congressional war powers when Obama struck Libya cannot now dismiss those same principles because the President is one of their own.

The hypocrisy is total. And it is the reason the war powers question never gets resolved — because neither party actually wants to resolve it. They want the political flexibility to support or oppose executive action based on who is in the White House, not on constitutional principle.

I spent seven years studying separation of powers doctrine, and the thing that strikes me about this moment is how completely the political class has abandoned good faith engagement with the text. The Constitution is not ambiguous here. Congress declares war. The President commands the military. Those are distinct functions, and the Founders made them distinct deliberately.

The Path Forward Requires Courage

Congress has one lever that is legally unambiguous: the power of the purse. If a majority of Congress believes the Iran strikes were unconstitutional or strategically catastrophic, they can defund the operation. They can pass legislation prohibiting the use of appropriated funds for military action against Iran without a formal declaration or AUMF. They have done this before — the Cooper-Church Amendment in 1971, the Boland Amendment in 1982.

They won't do it now. Because it requires taking a position that is clear, that is binding, and that has political consequences. Hearings carry none of those costs. Statements carry none of those costs. The performance of outrage is not the exercise of constitutional authority.

What this moment demands — what every moment like this demands — is a Congress willing to be what the Constitution designed it to be: a coequal branch that takes its war powers seriously, not as a political weapon, but as a structural check on executive overreach. That requires Democrats to apply the same standard to Democratic presidents. It requires Republicans to apply the same standard to Republican ones.

The founders would find our current arrangement barely recognizable. One branch makes war. Another holds hearings about it. And the constitutional text gathers dust while the republic burns through its inheritance.