Congress voted twice to end this war. The war didn't end.

Just before dawn on September 5, Iran's Islamic Revolutionary Guard Corps fired ballistic missiles at a U.S. aircraft carrier and a guided-missile destroyer patrolling near the Strait of Hormuz. Both ships evaded the barrage and no American service member was hurt. Within hours, U.S. Central Command answered in kind, but against a different target: not the batteries that had just fired on American warships, but three Iranian oil tankers. CENTCOM says it "permanently disabled" two of the vessels and destroyed a third outright, arguing that the ships were part of a shadow fleet financing the Revolutionary Guard. Iran, in turn, claimed retaliatory strikes on tankers and "U.S.-linked" shipping in the strait, an assertion that has not been independently verified.

None of this happened in a vacuum. It happened five weeks after the House of Representatives passed, for the second time, a resolution directing President Trump to end the war with Iran — and six weeks after the House and Senate did so together for the first time in the history of the modern War Powers Resolution. Congress has now gone on record twice, with bipartisan majorities in a Republican-controlled Congress, saying this war should stop. The war has not stopped. It has escalated into direct missile exchanges with a U.S. carrier group and a shooting campaign against oil tankers in one of the world's most important energy chokepoints.

A war with no authorization and, increasingly, no exit

The conflict began on February 28, 2026, when the United States and Israel launched coordinated strikes on Iranian nuclear, missile and naval targets under the name Operation Epic Fury, after Tehran refused to halt uranium enrichment. A ceasefire took hold after 40 days of fighting, followed by a reported 60-day framework for nuclear talks. It did not survive the summer. Renewed Iranian attacks on shipping brought back American airstrikes, a naval blockade of Iranian ports and, this month, a tanker war that has pushed Brent crude to roughly $96 a barrel — its highest level since late July — and driven U.S. diesel prices to a record $5.85 a gallon. Roughly a fifth of the world's oil normally moves through the strait; shipping-data cited this month put daily transits at a fraction of that baseline.

At no point in that six-month arc has Congress passed anything approaching a declaration of war or an authorization for use of military force. What it has passed, twice, are resolutions invoking Section 5(c) of the 1973 War Powers Resolution, which purports to require a president to withdraw forces from unauthorized hostilities once Congress directs it by concurrent resolution.

Two resolutions, and a widening gap between vote and effect

The record so far:

• On June 3, the House passed H.Con.Res. 86, sponsored by Rep. Gregory Meeks, by a vote of 215 to 208, with four Republicans crossing over.
• On June 23, the Senate followed, agreeing to the same resolution 50 to 48, with Republicans Bill Cassidy, Susan Collins, Lisa Murkowski and Rand Paul joining nearly every Democrat — the first time both chambers had ever adopted an Iran war-powers resolution.
• On July 23, the House passed a second, similarly worded resolution, 214 to 208.
• That same day, a discharge motion aimed at forcing a vote on a binding joint resolution, S.J.Res. 180, failed in the Senate, 47 to 49.

The administration's answer to the June votes was immediate and unambiguous. A White House official told reporters the measure would not reach the president's desk for signature, and the administration has separately argued that concurrent resolutions of this kind are themselves unconstitutional, resting on the Supreme Court's 1983 ruling in INS v. Chadha that struck down the legislative veto. Section 5(c) was written specifically so Congress could act without presidential sign-off; the White House's position is that this is precisely what makes it powerless. The war continued through the summer, the blockade continued, and by the time Iranian missiles were arcing toward a U.S. carrier last week, Congress's two resolutions had produced no change in the fighting they were written to stop.

"If you shoot at two of our ships, we will impose an even higher economic cost — taking out three of yours. We will not hesitate to defend American forces, and if necessary, destroy Iran's limited and exposed oil fleet."

That warning, attributed to CENTCOM commander Adm. Brad Cooper after the September 5 tanker strikes, is a more accurate statement of current U.S. Iran policy than either war-powers resolution has managed to be.

The harder vote Congress keeps declining to force

It would be too simple to read this only as executive defiance. The concurrent resolutions Congress passed in June and July were, by design and by the White House's own account, not legally binding — no presentment to the president, no veto, no enforcement mechanism beyond political pressure. The instrument that would actually bind a president is a joint resolution, which does require presentment and which a president can veto, but which Congress can in turn override with two-thirds majorities. The Senate had exactly that option in front of it on July 23, in the form of S.J.Res. 180. It fell not just short of a veto-proof two-thirds, but short of a simple majority, losing ground from the 50 votes the concurrent resolution had drawn a month earlier. Two Republicans who had crossed over in June, Murkowski and Paul, were not in the winning column on the discharge vote; only Collins held.

That is the more uncomfortable half of this story. A bipartisan coalition in Congress has shown it is willing to cast a symbolic vote against an unauthorized war. It has shown far less appetite for the harder, binding path that would force an actual confrontation with the president over ending it — one that would require members to own the consequences of a withdrawal vote rather than simply register disapproval. The result is a Congress that keeps taking the vote that changes nothing and keeps declining the vote that might.

What the tanker war exposes

None of this is an argument about whether striking Iran's oil fleet was the right operational call, or whether Iran's missile launches at a U.S. carrier group were the reckless escalation Washington says they were. It is an argument about process, and the process has now been tested twice and found wanting. When missiles are being fired at an American aircraft carrier and the administration is expanding a war into direct strikes on tankers at sea, the country is well past the six months contemplated in the original War Powers Resolution's timeline for justifying unauthorized combat. Congress's own preferred tool for that moment has been tried, passed by both chambers, and ignored. The tool built to actually bind a president sat one procedural vote away and did not get there.

A war that neither Congress will vote to fully own nor the executive will pause for review is not a stalemate between branches of government. It is an absence of one of them. As the fighting in the strait intensifies and the odds of a miscalculation — a hit ship, a mass-casualty strike — climb with every exchange, that absence stops being an abstraction about Article I and becomes the operative fact governing how, and how far, this war continues.