A War Nobody Voted For — And a Congress That Let It Happen

There’s a line in the U.S. Constitution so simple it shouldn’t require interpretation. Article I, Section 8: Congress has the power to declare war. Not the President. Congress. The Founders were explicit about this. James Madison called it “the most sacred of all” constitutional provisions — the one safeguard against a single person dragging a republic into bloodshed.

On February 28, 2026, at approxiomately 1:15 am ET, the United States began bombing Iran. No declaration of war. No congressional vote. No single national security incident was cited as the basis for the attack—Trump instead recounted 47 years of U.S.–Iran tensions, beginning with the 1979 hostage crisis, as justification. The bombs fell anyway.

What happened next is the part that should disturb you more than the war itself.

Congress had a choice. It had the tool — the War Powers Resolution of 1973, passed over Nixon’s veto precisely to prevent this kind of unilateral military adventurism. The law is unambiguous: the president may not enter U.S. troops into hostilities without express congressional authorization, regardless of a conflict’s scale or duration. The 60-day clock started ticking the moment the first bomb dropped. Congress could have acted.

It didn’t. When Senators Kaine and Paul introduced a War Powers Resolution on March 1, the Senate voted it down 53–47. Then they voted it down again. And again. By mid-April, the Senate had rejected Democratic efforts to force an end to U.S. military involvement in Iran four separate times, voting largely along party lines.

Four votes. Four failures. This is not a story about Trump breaking the law. It’s a story about Congress watching him do it and choosing, repeatedly, to look away.

The War Powers Resolution was supposed to be the fix for exactly this situation. Widely considered a measure for preventing “future Vietnams,” it was nonetheless generally resisted or ignored by subsequent presidents, many of whom regarded it as an unconstitutional usurpation of their executive authority.

Every president since Nixon has treated it as optional; Clinton in Kosovo, Obama in Libya, and now Trump in Iran. The pattern is so consistent it barely registers as news anymore. But what has changed, and what makes Operation Epic Fury different, is the scale.

This is markedly different in scope, scale, and objective from the more limited US attack on Iran of June 2025 which targeted senior leadership, military infrastructure, and nuclear capabilities. This is a war by any honest definition. The administration just refuses to call it one.

Secretary of State Marco Rubio told Fox News: “This is not a war against Iran,” the same view held by most modern presidents and their lawyers in the Office of Legal Counsel. If you call it something else—a “police action,” a “limited engagement,” or a “kinetic military operation”—you never have to ask permission. Truman did it in Korea. Nixon did it in Cambodia. The euphemisms change; the evasion doesn’t.

But here’s the thing about this particular evasion. Congress isn’t powerless here it’s passive. The appropriations power alone gives lawmakers the ability to cut off funding for any military operation they find objectionable.

The annual National Defense Authorization Act process, combined with supplemental appropriations, provides multiple leverage points. Republican leadership isn’t using any of them. They’re not even seriously trying. Speaker Johnson called the War Powers Resolution vote “a terrible, dangerous idea” that would “empower our enemies.” That’s not a constitutional argument. That’s cover.

And the Democrats? They’ve forced the votes, yes. Sen. Tim Kaine (D-Va.) has been relentless. But Kaine himself acknowledged that the renewed effort was unlikely to go anywhere, but said it’s important for members of Congress to go on record. "Going on record." That’s what it’s come to—symbolic gestures in the face of a $200 billion war that nobody voted for.

The costs are real. The war has already cost at least $12 billion, and the Pentagon has asked the White House to approve a $200 billion supplemental request to Congress to fund the conflict. The Strait of Hormuz closed. Global oil markets lurched. Economic shocks have rippled outward, with the costs falling on ordinary Americans while those who profit from endless war count their returns. Children were killed at a school in Minab. The 60-day deadline has come and gone.

The War Powers Resolution was built for this moment. It was written by legislators who had watched Vietnam consume a generation because no one in Congress had the spine to call a war a war. “After Nixon, it’s gone on from one president to the next , they believe they can use military force against one country after another,” says Louis Fisher, who served for 35 years as senior specialist in separation of powers at the Congressional Research Service.

Fifty years later, the lesson has not been learned. The resolution that was supposed to restore congressional war powers has instead become a ritual. A series of doomed votes that let lawmakers signal opposition without actually exercising it.

There is one question that cuts through all of it. Sen. Kaine asked it directly on the Senate floor: “If you don’t have the guts to vote yes or no on a war vote, how dare you send our sons and daughters into war where they risk their lives?”

No one answered him. That silence is the real story.

The 1973 War Powers Resolution wasn’t just a law. It was a promise that the United States would never again stumble into a catastrophic military conflict without the consent of the people’s elected representatives. Operation Epic Fury has broken that promise to the American people once again. Congress has the power to keep it. Right now, it is choosing not to.

That choice has a cost. Someone should start paying it.