H. Con.
Res. 61 is a House concurrent resolution that invokes section 5(c) of the War Powers Resolution to instruct the President to remove United States Armed Forces from hostilities with presidentially designated terrorist organizations in the Western Hemisphere unless Congress has declared war or enacted a specific authorization for the use of military force. The resolution is limited to organizations that the President has designated and to operations occurring in the Western Hemisphere.
The resolution matters because it is an explicit Congressional effort to restrict executive counterterrorism operations close to the Americas and to reassert Congress’s role in authorizing uses of military force. For defense planners, foreign partners, and oversight officials, the measure raises immediate questions about which authorities, activities, and deployments would be affected and how the directive would be implemented and enforced.
At a Glance
What It Does
The resolution directs the President—citing 50 U.S.C. 1544(c)—to end U.S. military participation in hostilities with presidentially designated terrorist organizations located in the Western Hemisphere, except where Congress has declared war or passed a specific authorization for the use of military force. It uses the War Powers Resolution’s removal mechanism rather than proposing a statute or funding restriction.
Who It Affects
The directive would directly affect Department of Defense combat and kinetic counterterrorism operations, U.S. special operations and intelligence personnel deployed in the Americas, and partner-country military cooperation that relies on U.S. operational support. It also bears on congressional committees responsible for authorizations and oversight and on diplomatic and development programs tied to security assistance.
Why It Matters
The measure signals a congressional attempt to constrain executive warfighting authority in the hemisphere and to make future operations subject to explicit statutory authorization. Practically, it could curtail a range of U.S. actions—from strikes to certain advisory, intelligence, and support activities—unless Congress acts, and it raises legal and procedural questions about enforceability and definition of key terms.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The resolution is brief and formulaic: it directs action under the War Powers Resolution to stop U.S. forces from engaging in hostilities against terrorist groups the President has designated, but only when those groups operate within the Western Hemisphere. By invoking section 5(c) of the War Powers Resolution, Congress is signaling that it intends to use the statutory removal mechanism available through a concurrent resolution rather than passing a new law.
Practically, the text leaves several operational gaps that would determine how aggressively the directive changes current military activity. The measure targets "hostilities," a term the bill does not define; that ambiguity matters because modern U.S. counterterrorism work often mixes kinetic strikes, intelligence sharing, advisory activities, and partner-enabled operations.
The resolution also ties applicability to organizations specifically designated by the President, which creates a dependence on executive lists and leaves open questions about organizations designated through other processes.Because the bill is a concurrent resolution (a House-and-Senate action that does not itself amend statute), its immediate legal effect depends on the War Powers Resolution framework and on how the executive branch responds. The resolution contains no operational timeline, no Treasury or appropriation language to compel compliance, and no enforcement mechanism; implementation would likely require coordination between Congress, the Department of Defense, and the National Security Council to translate the directive into orders affecting deployments and missions.
The Five Things You Need to Know
The resolution invokes section 5(c) of the War Powers Resolution (50 U.S.C. 1544(c)) to direct removal of U.S. Armed Forces from hostilities with "presidentially designated" terrorist organizations in the Western Hemisphere.
Its geographic scope is limited to the Western Hemisphere; it does not address operations against similar groups in other regions.
It permits exceptions only where Congress has declared war or enacted a specific authorization for the use of military force against the designated organization.
H. Con. Res. 61 is a concurrent resolution, not a statute; it relies on the War Powers Resolution’s removal mechanism and contains no independent funding or penal provisions to enforce compliance.
The text does not define key terms—most notably "hostilities" and which designation authorities qualify as "presidentially designated"—and it includes no timetable or procedures for how removal would be executed.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Instruction and statutory hook
The resolution’s title and opening lines state the directive and explicitly cite the War Powers Resolution’s removal clause (50 U.S.C. 1544(c)). That citation is consequential: it anchors the directive in an existing statutory framework that purports to give Congress a mechanism to order removal of forces via concurrent resolution, rather than attempting to create a new substantive statutory authorization or a funding prohibition. For implementers, the citation signals reliance on the WPR’s procedures and the political-legal dynamics that accompany them.
Remove U.S. forces from hostilities with presidentially designated terrorists in the Western Hemisphere
This single operative paragraph orders the President to remove U.S. Armed Forces from hostilities with any terrorist organization the President has designated, but only when those organizations are in the Western Hemisphere. The clause is short and categorical, which simplifies the text but increases demands on executive agencies to interpret its operational reach: does "remove from hostilities" require withdrawing all personnel, ending strikes, or halting advisory roles? The absence of definitional detail shifts the burden of operational definition to the executive branch and to implementing guidance from DoD and the National Security Council.
Congressional authorization and declaration of war carve-outs
The resolution explicitly preserves exceptions where Congress has declared war or passed a specific authorization for the use of military force against the named organization. That makes the directive conditional: Congress can override the removal requirement by passing an AUMF or a declaration. From a legislative strategy perspective, this language makes H. Con. Res. 61 a baseline constraint that Congress can lift by affirmative law, rather than a permanent statutory ban.
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
- Residents and civil-society organizations in the Western Hemisphere: The resolution, if implemented, would reduce the likelihood of U.S. kinetic operations in their countries or regions, lowering immediate exposure to cross-border strikes and potential collateral harm tied to counterterrorism missions.
- Members of Congress and oversight committees seeking stronger war-powers oversight: The measure gives Congress a visible statutory pathway to assert authority over regional military actions and forces future debates over specific AUMFs.
- Some U.S. military personnel and units: Units currently exposed to direct kinetic missions in the hemisphere could see reduced combat risk and legal exposure tied to contested operations without congressional authorization.
Who Bears the Cost
- Department of Defense and combatant commands (e.g., SOUTHCOM): Commanders could face curtailed mission sets, sudden operational re-scoping, relocation costs, and complications in partner engagements and intelligence sharing as activities are reclassified or halted.
- Partner governments and security forces in the Americas: Countries that rely on U.S. strikes, targeting support, or direct action against violent groups may lose immediate operational support and face security gaps.
- Executive branch policymakers: The President and national security advisors would lose a degree of unilateral flexibility in responding to emergent terrorist threats in the hemisphere and may need to seek urgent congressional authorizations.
- Intelligence and special-operations elements: Units that provide force-multiplying support (e.g., targeting, persistent ISR, tactical advisory roles) may see programs paused, complicating longer-term counterterrorism campaigns.
Key Issues
The Core Tension
The central dilemma is between congressional oversight of force and the executive’s need for rapid, flexible military action: the resolution strengthens legislative control over regional counterterrorism at the cost of introducing legal ambiguity and potentially reducing the President’s ability to respond quickly to emergent threats; the measure solves one problem—Congressional authorization—while creating operational and constitutional gray areas about who decides and how removals would be enforced.
The resolution raises several implementation and legal questions that the text does not answer. First, the meaning of "hostilities" is central but undefined.
Modern counterterrorism mixes kinetic strikes, advisory support, intelligence sharing, surveillance, and partner-enabled actions; whether the directive covers only lethal strikes or also these supporting activities will determine how disruptive the resolution is to current operations. Second, the term "presidentially designated terrorist organizations" is ambiguous.
Terrorist designations in U.S. practice come through multiple authorities (Executive Orders, Treasury designations, State Department FTO listings), and the resolution does not specify which mechanism or list it means. That ambiguity could create confusion about which groups trigger the removal obligation.
Third, the resolution relies on the War Powers Resolution’s concurrent-resolution removal mechanism rather than using appropriations or statutory prohibition. The enforceability of a concurrent resolution in this context is contested: a concurrent resolution does not itself carry the force of law in the same way a statute does, and the executive branch may challenge the scope or applicability of the WPR’s removal clause.
Finally, the bill contains no timeline or implementation mechanics—no date by which forces must be withdrawn, no requirement for reporting, and no funding consequence for noncompliance—so practical effect depends heavily on the President’s and the Department of Defense’s choices and on possible subsequent congressional actions.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.