This joint resolution directs the President to remove United States Armed Forces from "hostilities within or against" the Islamic Republic of Iran unless Congress enacts a declaration of war or a specific authorization for the use of military force. The text grounds the directive in the Constitution and cites the War Powers Resolution and statutory expedited-consideration rules (section 1013 of the Department of State Authorization Act and section 601(b) of the International Security Assistance and Arms Export Control Act).
The bill preserves several limited executive activities — defensive responses to attacks on the United States or U.S. personnel, intelligence collection and sharing, and assisting partner countries attacked by Iran since February 28, 2026, including intercepting retaliatory strikes and providing defensive materiel. The measure reasserts congressional war-declaring authority while leaving important operational questions about scope, timing, and enforcement unresolved.
At a Glance
What It Does
The resolution orders the President to withdraw U.S. forces from hostilities within or against Iran unless Congress passes a declaration of war or a specific AUMF. It invokes section 1013 (50 U.S.C. 1546a) and the expedited procedures of section 601(b), making this a privileged matter for prompt congressional consideration.
Who It Affects
The directive directly constrains the President, the Department of Defense, U.S. combatant commands (e.g., CENTCOM), and any U.S. forces participating in operations against Iran; it also forces Congress to decide whether to authorize continued hostilities or require withdrawal. Partner countries receiving U.S. defensive support and organizations tracking war powers will also be affected.
Why It Matters
If enacted, the resolution would re-center Congress as the deciding body on continued U.S. hostilities with Iran and could require a rapid operational drawdown absent new legislation. It tests statutory and constitutional mechanisms for ending unauthorized military engagements and could set a precedent for how Congress compels withdrawal in future conflicts.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The resolution starts by laying out findings: Congress’s constitutional authority to declare war, the President’s duty to defend the nation, and factual statements about U.S. involvement in what the bill calls Operation Epic Fury (including troop counts and casualties). Those findings frame the authors’ view that current operations against Iran lack congressional authorization and fall within the War Powers Resolution’s definition of "introduction of United States Armed Forces into hostilities."
The operative text (Section 2(a)) is straightforward: Congress "directs the President to remove the United States Armed Forces from hostilities within or against Iran" unless Congress itself authorizes the use of force by declaring war or passing a specific authorization. By tying the directive to section 1013 and section 601(b), the drafters signal that they expect the resolution and any related measures to receive expedited consideration under the statutes cited.
The bill does not, however, lay out a detailed timeline or enforcement mechanism for removal beyond the directive itself.Section 2(b) carves out three categories of allowed executive action. First, the United States may defend against attacks on the homeland, U.S. service members, diplomats, or facilities abroad.
Second, the executive can continue intelligence activities and intelligence-sharing related to threats from Iran or its proxies. Third, the United States may assist partner nations that have been attacked by Iran since February 28, 2026, including intercepting retaliatory attacks and supplying defensive materiel.
Those exceptions preserve a set of defensive and support activities while the broader removal directive applies to "hostilities within or against Iran."Implementation will turn on operational definitions and practical steps: commanders must interpret what counts as "hostilities within or against Iran" and when forces are sufficiently withdrawn to comply; Congress must decide whether to authorize continued operations; and the executive will need to reconcile the resolution’s directive with its obligations to protect forces in the field. The resolution creates a legal obligation for removal but leaves significant discretion and practical work to the President, DoD, and Congress to translate that obligation into movements and missions.
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 enacts a declaration of war or a specific Authorization for Use of Military Force (AUMF).
The text cites the War Powers Resolution (50 U.S.C. 1543(a)) and treats current operations against Iran as an "introduction of United States Armed Forces into hostilities.", It invokes section 1013 of the Department of State Authorization Act (50 U.S.C. 1546a) and section 601(b) of the International Security Assistance and Arms Export Control Act, which triggers expedited congressional consideration procedures for removal directives.
Section 2(b) preserves the executive's authority to defend the United States or U.S. personnel, to collect and share intelligence related to threats from Iran, and to assist partner countries attacked by Iran since February 28, 2026, including intercepting retaliatory strikes and supplying defensive materiel.
The findings state that over 50,000 U.S. service members participated in the operation described and that six U.S. service members were killed, facts the resolution uses to argue urgency and the need for congressional action.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Factual and constitutional predicates for the directive
This section lists constitutional authority (Congress’s power to declare war), the President’s defense responsibilities, and factual assertions about recent U.S. military action labeled "Operation Epic Fury" (troop participation, casualties, and executive statements). Those findings are not operative law but create the record Congress uses to justify directing a withdrawal and to frame the scope of the problem the resolution addresses.
Congress directs withdrawal absent a declaration or specific AUMF
This operative clause commands the President to remove U.S. Armed Forces from hostilities within or against Iran unless Congress enacts a declaration of war or a specific statutory authorization for the use of force. Practically, it converts Congress’s policy choice into a statutory instruction: the President must plan for withdrawal if Congress declines to authorize continued hostilities. The provision references statutory procedures (section 1013 and section 601(b)) that accelerate congressional consideration, but it does not specify a withdrawal timetable or enforcement penalties.
Limited, enumerated exceptions for defense, intelligence, and partner assistance
This subsection narrows the direct withdrawal obligation by expressly permitting the executive to defend the United States and U.S. personnel, continue intelligence collection and sharing about Iranian threats, and assist partner countries attacked by Iran since February 28, 2026, including intercepting retaliatory attacks and providing defensive materiel. Those carve-outs maintain a defensive and support posture but leave undefined boundaries between permissive activity and prohibited "hostilities," raising substantive implementation questions about mission types and force posture.
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 asserting constitutional war powers — the resolution gives legislators a statutory instrument to force a congressional decision on continued hostilities and to compel withdrawal absent authorization.
- U.S. service members and their families — by law, the resolution would limit combat deployments against Iran unless Congress authorizes them, potentially reducing prolonged exposure to hostilities without legislative approval.
- War powers and civil-liberties advocacy organizations — the measure strengthens a statutory precedent for Congress to use law to end unauthorized hostilities and may accelerate judicial or political enforcement of congressional authority.
- Congressional staff and oversight committees — expedited-consideration mechanics and a clear statutory directive focus attention and resources on drafting an AUMF or debating withdrawal logistics, giving oversight actors a concrete path to influence policy.
Who Bears the Cost
- The Executive Branch and the President — the resolution constrains the President’s independent ability to prosecute military operations against Iran, requiring withdrawal absent new legislation and narrowing operational discretion.
- Department of Defense and combatant commands (e.g., CENTCOM) — forced drawdown or mission changes would impose planning, logistics, redeployment costs, and potential operational risks to forces in theater.
- Commanders and deployed troops — hurried or politically driven withdrawal orders can increase risk to personnel and complicate rules of engagement, force protection, and sustainment.
- Allied and partner governments relying on U.S. offensive or deterrent capabilities — a legal requirement to withdraw may create shortfalls in regional deterrence or operational coordination, forcing partners to adjust rapidly.
- Defense contractors and supply-chain actors — contracts tied to sustained operations or ramped logistics support could face cancellation or reduced demand, producing economic impacts.
Key Issues
The Core Tension
The central tension is between Congress’s constitutional claim to control declarations of war and removal of U.S. forces, and the President’s need for rapid operational flexibility to defend forces and respond to unpredictable threats; the resolution strengthens legislative control but does so by issuing a directive that may force difficult, risky operational choices without supplying clear timing, definitions, or enforcement tools.
The resolution raises several implementation and legal questions that the text does not resolve. The operative directive requires removal from "hostilities within or against Iran," but the bill does not define "hostilities" or specify whether the removal applies to advisory personnel, intelligence operators, contractors, or purely defensive air- or missile-defense forces.
Those definitional gaps will determine how much activity the executive can continue under the carve-outs and whether a partial continued presence would comply with the statute.
Enforcement and timing are also open questions. The resolution "directs" withdrawal but supplies no timeline, phasing requirements, or enforcement mechanism (civil remedies, funding restrictions, or criminal penalties).
That leaves the measure dependent on political pressure, implementation orders from the executive, or subsequent congressional steps, including appropriations riders or an AUMF. The invocation of expedited-consideration statutes compresses legislative debate, which could limit Congress’s practical ability to craft a detailed authorization or a measured withdrawal plan.
Finally, the carve-outs for defense, intelligence, and partner assistance are broad in practice: executive determinations about what is "defensive" could allow continued kinetic activity that some lawmakers would view as hostilities, creating a likely point of legal and political dispute.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.