This joint resolution instructs the President to remove United States Armed Forces from any hostilities within or against the Islamic Republic of Iran unless Congress has declared war or enacted a specific authorization for the use of military force. It invokes the statutory fast‑track procedures in section 1013 of the Department of State Authorization Act (50 U.S.C. 1546a) and the expedited consideration framework of section 601(b) of the International Security Assistance and Arms Export Control Act of 1976.
The resolution limits removal orders by preserving three narrowly framed activities: defensive actions against attacks on U.S. personnel or facilities, intelligence activities, and assistance to partner countries attacked by Iran since February 28, 2026 (including intercepting retaliatory attacks and providing defensive materiel). For practitioners, the measure reasserts Congress’s Article I war‑power, places immediate constraints on ongoing operations, and raises practical questions about implementation timelines and mission planning for Commands operating in the region.
At a Glance
What It Does
The resolution directs the President to remove U.S. forces from hostilities within or against Iran unless Congress has issued a declaration of war or passed a specific authorization for the use of military force. It relies on statutory expedited procedures for congressional consideration and clarifies that the action does not itself authorize military force.
Who It Affects
This affects the Department of Defense and combatant commands with forces operating in or against Iran, the Executive Branch’s national security apparatus, and congressional committees responsible for war powers and defense. Regional partners and defense contractors will be materially affected by changes in U.S. operations and support posture.
Why It Matters
The measure reasserts congressional control over decisions to wage sustained hostilities and could force a pause or reconfiguration of current military operations. It also sets a statutory path for rapid congressional consideration, creating near‑term political and operational pressure on both the White House and the Pentagon.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The resolution begins by stating Congress’s constitutional claim to the power to declare war and asserts that, as of its findings, Congress has neither declared war on Iran nor passed a specific statutory authorization for force within or against Iran. It records that U.S. forces have been employed in an operation identified in the text and treats that employment as the introduction of forces into hostilities under the War Powers Resolution.
Using the statutory vehicle in 50 U.S.C. 1546a, the resolution then directs the President to remove U.S. Armed Forces from hostilities with Iran unless Congress explicitly authorizes those hostilities by declaration or a specific AUMF. That statutory cross‑reference also triggers expedited procedures for congressional consideration; the joint resolution authors its own removal directive under that authority rather than creating a new authorization for force.The text carves out three narrow exceptions to the removal requirement.
The United States may defend against attacks on its territory, personnel, or facilities; it may continue intelligence collection, analysis, and sharing; and it may assist partner countries that have been attacked by Iran since February 28, 2026, including intercepting retaliatory strikes and furnishing defensive materiel. Finally, the resolution contains an explicit rule of construction that it does not itself authorize the use of military force, preserving the distinction between a removal mandate and an AUMF.
The Five Things You Need to Know
The resolution directs the President to remove U.S. Armed Forces from hostilities within or against Iran unless Congress issues a declaration of war or a specific authorization for the use of military force.
It invokes section 1013 of the Department of State Authorization Act (50 U.S.C. 1546a) and the expedited procedures of section 601(b) of the International Security Assistance and Arms Export Control Act of 1976 to govern congressional consideration.
The bill treats the February 28, 2026 deployment (identified in text as Operation Epic Fury) as the introduction of U.S. forces into hostilities under the War Powers Resolution (50 U.S.C. 1543(a)).
Three exceptions permit continued activity: defending against attacks on U.S. personnel or facilities, intelligence collection and sharing, and assisting partner countries attacked by Iran since February 28, 2026 (including intercepting retaliatory attacks and providing defensive materiel).
Section 2(c) expressly states the resolution does not authorize the use of military force and is intended only to direct removal absent a congressional authorization.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Constitutional and factual predicates for the resolution
This part lists the constitutional basis (Congress’s Article I power to declare war) and factual assertions the sponsors rely on — notably that Congress has not declared war on Iran and that the administration launched an operation on February 28, 2026. These findings establish the legal framing the sponsors will use to argue removal is required under the War Powers Resolution and related statutes, and they anchor the measure to a specific set of events rather than a hypothetical future confrontation.
Directive to remove forces from hostilities with Iran
This subsection is the operative directive: it commands the President, pursuant to the statutory removal mechanism in 50 U.S.C. 1546a, to withdraw U.S. Armed Forces from hostilities within or against Iran unless Congress provides a declaration of war or a specific AUMF. Practically, this creates a statutory pull on the Executive to cease offensive or otherwise hostilities‑level activities that the sponsors characterize as unauthorized, and it ties the resolution to an existing statutory framework for congressional direction.
Narrow carveouts for defense, intelligence, and partner assistance
This subsection preserves three categories of activity: (1) self‑defense against attacks on the United States or its personnel/facilities abroad; (2) intelligence activities such as collection, analysis, and sharing; and (3) assistance to partner countries attacked by Iran since February 28, 2026, including interception of retaliatory strikes and providing defensive materiel. Each carveout limits how broadly the removal directive can be read and will be the locus of operational interpretation disputes between the Pentagon and Congress.
Non‑authorization clarification
This short provision makes explicit that the joint resolution does not function as an authorization for the use of military force. That preserves the sponsors’ intention that removal is a cessation mechanism rather than a permissive grant of power, and it signals that any subsequent offensive or escalatory activity would require a separate congressional act.
This bill is one of many.
Codify tracks hundreds of bills on Foreign Affairs across all five countries.
Explore Foreign Affairs in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- Members of Congress seeking to reassert Article I war powers — the resolution provides a concrete statutory instrument to constrain executive military engagements without a new AUMF.
- U.S. service members deployed in or against Iran — by directing removal from hostilities the bill aims to reduce exposure to combat operations not authorized by Congress.
- Advocacy groups focused on congressional oversight and restraint in the use of force — they gain a clear statutory precedent for using section 1013 removal procedures to force executive changes in posture.
- Domestic legal advisors and compliance officers in DoD and State — the resolution clarifies legal boundaries and creates a discrete statutory process for altering operations, reducing ambiguity about which statute governs a congressional removal directive.
Who Bears the Cost
- The Executive Branch (President, Department of Defense) — the resolution constrains operational discretion, forcing changes in missions, rules of engagement, and contingency plans if Congress insists on removal.
- Combatant commands and forward‑deployed forces — they may face abrupt mission discontinuities, redeployments, or reconfiguration of defensive versus offensive postures with attendant logistical and personnel costs.
- Defense contractors and suppliers supporting operations in the region — curtailment of offensive or sustainment activities could disrupt contracts, deliverables, and revenue tied to current operations.
- Regional partners that rely on U.S. offensive capabilities for deterrence — those partners may face gaps in strike options and deterrence, potentially increasing pressure on their own forces or changing diplomatic dynamics.
Key Issues
The Core Tension
The central dilemma: the resolution seeks to restore Congress’s constitutional prerogative to authorize sustained hostilities while preserving the President’s ability to protect forces and respond to immediate threats. Strengthening congressional control reduces executive overreach but can constrain timely defensive operations and allied support, creating trade‑offs between constitutional accountability and operational flexibility.
The resolution rests on statutory cross‑references that trigger expedited congressional procedures, but it does not set a timeline, enforcement mechanism, or detailed logistics for how removal must occur. That raises practical questions: who certifies that ‘‘hostilities’’ have ceased, how quickly forces must withdraw or alter missions, and which authorities govern transitional logistics and liabilities for partner forces or assets left behind.
Those implementation details will be resolved in the interplay between congressional leadership, the White House, and the Pentagon — not by the text of this measure.
The carveouts create implementation ambiguity. The self‑defense exception is standard but operationally broad; intelligence activities and ‘‘assisting partner countries’’ language can be read to permit significant support and even kinetic defensive measures.
The temporal limitation tying partner assistance to attacks ‘‘since February 28, 2026’’ is a blunt instrument: it narrows the universe of partners eligible for assistance but also risks arbitrary distinctions between states or proxy incidents that predate that date. Legal teams will litigate the boundaries between permitted defensive support and prohibited hostilities.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.