Congress divided sits at the center of this dementia and brain health question.

Congress is divided on whether military strikes against Iran in late February 2026 were legal without a formal war declaration, and the split breaks down almost entirely along party lines. The fundamental disagreement comes down to a constitutional question that has haunted American foreign policy for decades: Does the president need explicit congressional approval before launching military action, or can executive notification of military leadership satisfy the legal requirement? When the Trump administration ordered strikes against Iranian targets without prior congressional authorization, it reignited this debate with particular intensity. Democrats and some Republicans introduced two separate measures calling for a vote on the legality of the action, both of which failed in early March 2026. The core issue isn’t new, but the circumstances forced Congress to confront it directly.

The military strikes happened on a weekend in late February without advance warning to the full Congress, only to select leadership. Within days, lawmakers introduced resolutions demanding a vote on whether the military action was constitutional. The Senate resolution failed 47-53 on March 4, 2026, and a similar House measure failed on March 5, 2026. This article explores why Congress can’t agree on what the law actually requires, and what that division means for future military action.

What Does the U.S. Constitution Actually Say About War Powers?
The War Powers Resolution: What Does It Actually Require?
Why Congress Split Almost Entirely Along Party Lines
The Failed Congressional Resolutions and What They Meant
Historical Precedent: Why Past Wars Matter to This Argument
The Notification vs. Authorization Dilemma
What This Division Means for Future Military Action
Conclusion

What Does the U.S. Constitution Actually Say About War Powers?

The Constitution is surprisingly direct on this point: Article 1 gives Congress—not the president—the power to declare war. This is one of the clearest powers the Constitution delegates to the legislative branch. The founders deliberately separated this authority from executive control precisely to prevent any one person from unilaterally committing the nation to armed conflict. Yet that clarity has become increasingly ambiguous in practice, which is why the iran strikes created such a sharp divide. The tension emerged because the Constitution gives Congress the power to declare war, but military action and warfare aren’t always the same thing constitutionally. A declaration of war is a formal legal statement—Congress passes a resolution that officially establishes a state of war. But the United States can use military force without that formal declaration.

The distinction matters legally, and it’s where the disagreement starts. Supporters of the administration’s actions argue that targeted military strikes, even significant ones, don’t require a full war declaration. Opponents argue that strikes extensive enough to constitute military action against another nation should require congressional approval beforehand, not just notification afterward. Consider the practical difference: A formal war declaration changes everything legally—it suspends certain civil liberties, affects trade relationships, activates wartime authorities. But it also triggers constitutional requirements. The absence of a declaration doesn’t mean military force is automatically legal; it means the lines between what does and doesn’t require congressional approval have become blurred. This ambiguity is exactly why Congress is so divided.

What Does the U.S. Constitution Actually Say About War Powers?

The War Powers Resolution: What Does It Actually Require?

In 1973, Congress passed the War Powers Resolution, attempting to clarify the constitutional muddle. Under this law, the president must notify Congress within 48 hours of committing military forces to armed conflict. The strikes against iran violated the spirit of this requirement by not notifying the full Congress until after the action had already happened. However, the administration took the position that notifying congressional leadership satisfied the statutory requirement, since the law specifies “Congress” can mean leadership or selected members. Here’s the crucial limitation: The War Powers Resolution requires notification, but it doesn’t explicitly require advance congressional approval before military action begins.

This is why Secretary of State Marco Rubio defended the administration’s conduct by saying that “congressional leadership and the Gang of Eight were notified per statutory requirements.” He was technically correct about the notification—the question is whether notification is enough, or whether authorization should come first. This distinction became the crux of the congressional disagreement. The resolution also says that military action can continue for 60 days without congressional authorization, with an additional 30-day withdrawal period. After that, the president must get explicit congressional approval or withdraw the forces. This suggests Congress intended that 60-day window to be for emergencies, while approval should come within that timeframe for longer operations. But again, the law doesn’t explicitly mandate advance approval, which is why interpretations differ so sharply. If the strikes were brief and limited, opponents argue they still exceeded constitutional authority; supporters argue they fit within the emergency framework the law contemplates.

Why Congress Split Almost Entirely Along Party Lines

The division on whether the Iran strikes were legal reveals something important about how national security debates have become polarized. Democratic Senator Chris Murphy of Connecticut called the actions “illegal” without authorization. Meanwhile, Republican lawmakers largely defended the military action as necessary against a hostile regime. This wasn’t a splitting of hairs over constitutional interpretation—the positions reflected fundamentally different views on executive power and congressional authority. Democratic leaders introduced the Senate resolution alongside Republican Senator Rand Paul of Kentucky, and Democratic Representative Ro Khanna introduced a House measure with Republican Representative Thomas Massie of Kentucky. These bipartisan pairings show that some principled opposition to executive power exists across party lines.

However, the votes—47-53 in the Senate, with similar failure in the House—show that most of the party supported the sitting president’s actions. When Senator Tim Kaine joined with Rand Paul to push the Senate resolution, they were swimming against strong partisan currents in their own respective parties. What’s notable is that the disagreement isn’t really about the Iran threat itself—both parties acknowledge the threat. The disagreement is about process and constitutional authority. Republicans argued the administration had the power to act; Democrats argued that power belongs to Congress. But that ideological split has largely reversed historical positions: Democrats, who once expanded executive war powers, now defend congressional authority, while Republicans once skeptical of executive power now defend presidential military action. This inversion shows how much partisan loyalty now outweighs consistent constitutional positions.

Why Congress Split Almost Entirely Along Party Lines

The Failed Congressional Resolutions and What They Meant

Two separate resolutions attempted to force a vote on the Iran strikes’ legality. The Senate Joint Resolution 123 (S.J.Res.123) and House Concurrent Resolution 38 (H.Con.Res.38), both from the 119th Congress, sought to declare that the military strikes against Iran violated the War Powers Resolution and therefore required congressional authorization. Neither resolution passed, but the votes themselves revealed the split. The fact that these resolutions failed doesn’t mean Congress approved the military action—it means Congress failed to disapprove of it. This is an important distinction. A failure to pass a war powers resolution isn’t the same as passing one; it’s an absence of action.

By not voting to require congressional authorization or to withdraw forces, Congress effectively allowed the military action to continue. Some argued this silence implied tacit approval, while others said it revealed Congress’s unwillingness to confront the constitutional question directly. The failed votes suggest that most lawmakers, regardless of party, are uncomfortable actually voting to restrict military action once it has already happened. The comparison is instructive: If the resolutions had passed, Congress would have been formally asserting its war powers authority. Instead, Congress allowed the action to proceed, and the question remains unresolved. This creates a precedent that future administrations might cite—military strikes without advance authorization, followed by notification to leadership, followed by failed congressional resolutions, becomes a template rather than a violation. Without a clear congressional assertion of authority, the executive gains more practical power even if the constitutional question remains theoretically unresolved.

Historical Precedent: Why Past Wars Matter to This Argument

The Iran strikes weren’t the first time Congress failed to formally declare war before military action occurred. The Korean War happened without a declaration. Vietnam escalated without one. The 1991 Gulf War had congressional authorization but technically no war declaration. The 2001 authorization for military force after 9/11 has been invoked to justify operations in multiple countries. Each of these established precedents that later administrations cited to justify their own actions. This history cuts both ways in the current debate. Supporters of the administration cited decades of executive military action without war declarations as proof that this is normal practice.

Opponents argued that normalizing unconstitutional practice doesn’t make it constitutional—it just means Congress has been gradually ceding its authority for decades. They warned that allowing the Iran strikes without congressional approval would further erode the separation of powers and push the executive branch’s authority even further beyond constitutional limits. The warning is that once you accept that military strikes don’t require congressional authorization, you’ve essentially eliminated Congress’s war powers in all but the most formal sense. However, there’s also a practical reality that military emergencies sometimes require speed. If a hostile nation launches an attack, waiting for Congress to debate and vote on authorization could take days or weeks. This is why some form of executive emergency power seems necessary. The disagreement is about where that emergency power ends and congressional authority begins. Without a clear line, every president pushes further, and Congress’s authority erodes incrementally.

Historical Precedent: Why Past Wars Matter to This Argument

The Notification vs. Authorization Dilemma

Secretary of State Marco Rubio’s defense centered on notification: the administration had notified congressional leadership within the required timeframe, therefore the legal requirement was satisfied. This argument reflects a particular interpretation of the War Powers Resolution that most Republicans accepted and most Democrats rejected. Under Rubio’s view, notifying the Gang of Eight—the top leaders of both parties on key committees—constitutes notifying Congress. Senator Chris Murphy and other Democrats argued that notification is different from authorization.

Congress needs to vote to authorize military action, not just be informed that it’s happening. There’s a meaningful difference: a notification is one-way communication about a decision already made; authorization is Congress actually having a voice in whether the action proceeds. By the time leadership is notified, the military strikes have already begun. Demanding that Congress vote before military action is fundamentally different from telling them afterward. The practical limitation of the notification-only approach is that it removes Congress’s ability to prevent military action—Congress can only react after the fact by voting to withdraw forces, which is much harder politically than voting against authorization in advance.

What This Division Means for Future Military Action

The failure of the war powers resolutions suggests that future administrations will likely follow the same pattern: military strikes first, notification second, failed congressional resolutions third. Without Congress standing firm on its constitutional authority, the precedent becomes clearer that the executive branch can act unilaterally in military matters. This has implications for future conflicts with Iran, China, North Korea, Russia, or other adversaries. Looking forward, the core question remains unresolved.

Will Congress eventually reassert its war powers authority, or will it continue to delegate that power to the executive through silence and failed votes? The 2026 Iran strikes didn’t answer that question definitively. They exposed it, but left it open. Whether Congress can overcome partisan divisions to defend its constitutional role—regardless of which party holds the presidency—remains to be seen. If another military crisis emerges, the playbook from February and March 2026 will likely repeat: executive action first, congressional debate second, divided votes that change nothing.

Conclusion

Congress is divided on the legality of the Iran strikes because the Constitution gives Congress the war power, but decades of practice have blurred exactly what authority that gives Congress and what authority presidents can exercise independently. The fundamental disagreement isn’t about Iran specifically—it’s about whether the president can commit the nation to military action without congressional vote. When two resolutions demanding a vote both failed in early March 2026, Congress effectively chose not to resolve the constitutional question, allowing the precedent of executive unilateral action to deepen.

The practical consequence is that future military action is likely to follow the same pattern: strikes without advance congressional approval, notification of leadership after the fact, and failed attempts by Congress to reassert control. Without a clear congressional insistence on its constitutional authority, American war powers will continue to drift further toward the executive branch. Whether that represents a dangerous erosion of constitutional limits or a practical necessity for military readiness in a dangerous world remains the central question dividing Congress.