Tim Kaine Is Going to Lose His War Powers Vote. He Should Take It Anyway.

The Resolution That Has Never Stopped a War

The War Powers Resolution passed in 1973, over Richard Nixon's veto. It requires the President to notify Congress within 48 hours of committing forces to hostilities and mandates withdrawal within 60 days without congressional authorization. Nixon called it unconstitutional when he vetoed it. Every president since — Democrat and Republican, from Gerald Ford to Barack Obama to Joe Biden — has treated the Resolution as optional, complying with the notification requirement while explicitly disclaiming that the 60-day clock was legally binding on the executive. Federal courts have consistently declined to adjudicate the dispute, calling it a political question between branches. The Resolution has never stopped a military operation. Not Korea. Not Vietnam (it wasn't passed yet). Not Grenada, Panama, Kosovo, Libya, Yemen, or any of the drone campaigns conducted in multiple countries simultaneously. There is a school of thought — expressed with considerable polish in some quarters today — that this track record demonstrates the Resolution is toothless and the legal debate is settled in the executive's favor [4]. The people making this argument have a point about the history. They do not have a point about the Constitution. Eighty years of presidents exceeding a constitutional boundary does not dissolve the boundary. It means eighty years of Congress failing to enforce its own authority — which is, to be direct, Congress's fault as much as any president's.

The Bipartisan Coalition Nobody Expected

Here's the detail that deserves more attention than it's getting: who is standing next to Tim Kaine on this. In the House, Representative Ro Khanna of California filed a companion war powers resolution. That is expected — Khanna has been the most consistent progressive anti-interventionist voice in the chamber for years. What is less expected is the name beside his: Thomas Massie, Republican of Kentucky, representing a district Trump carried by 40 points. Massie has been consistent on this too. He voted against Yemen authorizations. He voted against Syria. He has opposed executive war-making regardless of which party holds the White House, which makes him the libertarian-right's version of Khanna — genuinely principled and genuinely willing to absorb the political hit for it. When these two stand on the same resolution, they are not performing bipartisanship. They are demonstrating that this argument is not partisan — it is constitutional. Both party establishments find it inconvenient. That is, generally speaking, a sign that someone has gotten something right [2].

What President Trump is doing is dangerous, unnecessary, and idiotic. And it is illegal.

— Sen. Tim Kaine (D-VA), February 28, 2026

Democrats Who Disagree — and Why That Makes the Vote More Important

Not every Democrat is on board. Senators John Fetterman and Josh Gottheimer have indicated support for the Iran strikes, with Gottheimer arguing that a war powers resolution would "signal weakness" to adversaries [2]. It's worth engaging that argument before dismissing it. Yes, public congressional opposition to an ongoing operation could theoretically complicate it diplomatically. The question is: what's the alternative? Silence? The answer to "this is hard" cannot be "let's skip the debate and let the executive decide." That is exactly the logic that, applied consistently across eight decades, has produced the constitutional situation we are in now, where the President can launch major combat operations against a sovereign nation and the only people who need to be told — moments before the bombs fall — are eight congressional leaders who cannot formally object. Fetterman and Gottheimer represent a real strand of Democratic foreign policy thinking — the Cold War hawkishness that never fully gave way to post-Iraq war skepticism. They are not wrong that Iran is dangerous, that IRGC leadership has American blood on its hands, or that this administration can point to real strategic rationale. They are wrong that those facts settle the question of process. Good ends do not exempt presidents from constitutional requirements. If they did, we would not need Article I at all [3].

Why the Vote Matters When You Already Know You'll Lose

Tim Kaine knows he doesn't have the votes. He probably knew he didn't have them when he filed war powers resolutions on Yemen, or on Syria, or on the drone program. He filed them anyway. Here is why that matters. When you force a vote on something you know is losing, you accomplish two things. First, you create a record — a set of roll-call votes that constituents, journalists, and historians can examine. Every senator who votes against Kaine's resolution on Monday will have voted, on the record, that Congress does not need to authorize a major military operation against a nation with whom we have no formal declaration of war. That is a significant vote. The voters who sent those senators to Washington deserve to know how it was cast. Second, you force accountability in real time. The alternative — letting the President act, expressing displeasure in press releases, and moving on — is how the War Powers Resolution became a dead letter over 53 years. Every time Congress shrugged and issued a strongly worded statement instead of taking the hard vote, it ceded more ground. The ground does not come back unless someone starts fighting for it. The War Powers Resolution has never stopped a war. It has created a record. Records matter. They are how public opinion shifts, how legal challenges develop, how the eventual constitutional reckoning gets framed when it finally comes. You build the record by taking the vote, even when — especially when — you are going to lose [1].

What Congress Could Actually Do (If It Wanted To)

Here is the uncomfortable part that progressives who are outraged today and hawkish Democrats who are supportive today should both sit with: Congress is not powerless. If Congress genuinely believed the President needed authorization before launching major combat operations, it could attach conditions to military appropriations. It could refuse to fund operations conducted without congressional approval. It could pass legislation with real teeth — not a 1973 statute that every president treats as advisory, but something that has enforcement mechanisms. The reason this has not happened is not that it is constitutionally impossible. The reason is that it is politically difficult, requires courage from members who would prefer to have it both ways — criticizing the President after the fact without ever forcing the hard vote — and the political incentives almost never align to make it happen [4]. Tim Kaine has been filing war powers resolutions for years. He knows the politics. He does it anyway because he believes that someone has to maintain the record, force the accountability, and make the argument even when it loses. That is, for all the cynicism that politics generally rewards, a form of institutional integrity worth respecting. He should take Monday's vote. He should take it cleanly, on the merits, and make every senator answer the question: does Congress have a role in sending this country to war, or not?

Operation Epic Fury will stand. The strikes are done. The legal challenges will wind through courts that will decline to adjudicate them. The debate will fade when the next news cycle arrives. But the vote — if Kaine takes it, if every senator has to go on record — will remain. That's the work. It doesn't look like winning. It is winning, eventually, in the only way constitutional democracy actually functions: slowly, on the record, with accountability that accumulates over time. The voters who sent 100 senators to Washington deserve to know where their senators stand on this. Tim Kaine is going to make sure they find out.