On 2nd January US forces successfully executed a complex and precise operation to seize the Venezuelan President, Nicolas Maduro. However sophisticated the military operation was, it has caused international controversy about legality and sovereignty. The Chinese Government, for example, has called for Maduro’s release whilst Argentina’s President, Javier Milei, has supported US actions. Keir Starmer has so far refused to be drawn into the controversy surrounding the US operation. Irrespective of how one reads the politics, the seizure of Maduro raises a classic US Government question: what is the president legally allowed to do, militarily, without Congress? A common misconception is that the United States routinely “goes to war” through a formal declaration. In reality, Congress’s last formal declaration of war occurred during the Second World War, after which US conflicts have generally been conducted through authorisations short of a declaration, or through presidents acting first and Congress responding later (or not at all). What does the US Constitution actually say? The US Constitution divides powers in a way that is designed to force shared responsibility. According to Article I, Section 8, only Congress has the power to declare war. Congress also controls critical supporting powers, such as raising and funding the military. Even if Congress does not declare war, it can still shape (or block) sustained military action through legislation, appropriations, and oversight. Article II, however, clearly stipulates that “The President shall be Commander in Chief of the Army and Navy of the United States…” This gives the president operational command and thus the ability to direct the armed forces once they have been deployed. But it leaves open the hardest question: does commanding the military include initiating hostilities without Congress? This is why war powers is best taught as a designed tension: Congress is meant to supply democratic authorisation and long-term legitimacy; the president is meant to supply speed and unity of command. The controversy is where speed ends and where Congress’s authorisation must begin. The tension between those two ideas is not a technical footnote; it sits at the heart of how the United States actually wages war in the modern era. One might postulate that Article II means the president is militarily powerful, but still fundamentally limited. The reality, however, is that modern crises rarely arrive in a neat form that allows time for Congress to debate and vote before force is used. This is why presidents have repeatedly claimed that the Commander in Chief power includes authority to act quickly, especially where they argue American lives, US forces, or urgent national interests are at stake. The modern statute students must know: the War Powers Act (1973) Congress tried to reassert its position after the Vietnam War by passing the War Powers Act (also known as the War Powers Resolution). The statute’s logic is clear: it does not pretend the president can never act quickly, but it tries to force accountability and a decision point. The War Powers Act requires the president to report to Congress within 48 hours when US forces are introduced into hostilities (or situations where imminent hostilities are clearly indicated). It then establishes a 60-day structure for terminating the involvement absent a declaration of war or specific statutory authorisation (with a further period linked to safe withdrawal). This is where the debate becomes politically and legally contentious. Presidents have often complied with the reportinghabit while disputing the idea that Congress can truly force the end of an operation. Congress, meanwhile, has tools within the War Powers Act, such as expedited procedures, to bring war powers measures to the floor quickly. However, Congress does not always use these decisively. What practice looks like The best way to understand presidential war powers is to see how presidents and Congress have behaved when the stakes were real. A crucial early precedent is the Korean War. The UN Security Council authorised a UN-based response, but President Truman did not seek congressional authorisation under domestic law, and Congress did not pass a declaration of war or an Authorization for Use of Military Force (AUMF). Instead, Congress supported the war by passing appropriations bills and the Defence Production Act. These provided the funding and means for Truman to fight the war. Supporters of Truman’s approach argue that presidents must be able to respond quickly to aggression and to meet international commitments; critics point out that Korea helped normalise the idea that major hostilities can begin without a prior vote. The Vietnam War showed a different pattern: Congress quickly granted President Johnson broad permission that later became controversial. The Tonkin Gulf Resolution (1964) is an example of Congress authorising escalation in wide terms via a joint resolution. Here, the constitutional problem was not that Congress was ignored, but rather that Congress arguably handed the president an open-ended mandate and struggled to claw its authority back. The Lebanon episode in the 1980s demonstrates that Congress can, at times, be explicit and legally precise. Public Law 98-119 authorised continued US participation in the Multinational Force in Lebanon and stated that Congress intended it to constitute the “necessary specific statutory authorization” under the War Powers Resolution. That is the War Powers Act functioning as designed: Congress drawing a line and placing an operation on a statutory footing. Post-9/11, the most important legal instrument is the 2001 Authorization for Use of Military Force (Public Law 107-40). Its text authorises the president to use “necessary and appropriate force” against those responsible for the 9/11 attacks and those who harboured them. The enduring controversy is structural: supporters argue the Authorization for Use of Military Force created necessary flexibility against non-state threats; critics argue that broadly worded authorisations can be stretched over time, shifting war decisions away from Congress. Libya (2011) is a modern example of how the executive branch defends unilateral action in limited operations. In an Office of Legal Counsel opinion, the Justice Department argued that the president had constitutional authority to direct the use of military force in Libya because he could reasonably determine that doing so served US national interests, and that prior congressional approval was not constitutionally required for the limited operations considered. This is not proof that the executive is right, but it is strong evidence of how the executive branch constructs legal arguments when it believes speed and limited scope justify presidential initiative. A clear example of War Powers reporting in practice is President Trump’s April 2017 letter to congressional leaders after US strikes on Syria’s Shayrat airfield, which states the communication is made “pursuant to 50 U.S.C. 1543(a)” (the War Powers Act reporting provision). Whatever people think of the merits of the strike, it shows a recurring modern pattern: presidents act, then formally notify Congress under the War Powers Act framework. Courts: often not the referee, but still a useful framework Courts frequently avoid becoming a direct referee in war-powers disputes, but the Supreme Court case of Youngstown Sheet & Tube Co. v Sawyer (1952) provides a valuable way to think about presidential power when Congress is involved. The case itself stemmed from an executive order issued by Truman which directed the Secretary of Commerce to seize and operate the USA’s steel industry. The Court ultimately ruled the seizure unconstitutional but the case was significant because of Justice Jackson’s now famous concurrence. Jackson described “three categories”: presidential authority is strongest when acting with Congress, most uncertain when Congress is silent, and weakest when acting against Congress’s expressed or implied will. For students, this is a practical test: the key question becomes not only “what can the president do?” but “what has Congress authorised, restricted, or left ambiguous?” Applying the thinking to Venezuela Reuters reporting describes the Maduro capture as a military operation framed by the administration as a form of law-enforcement action, while legal experts cited by Reuters criticised that rationale and questioned both the coherence of the justification and the international law basis for using force on Venezuelan territory. International legality and domestic legality are not the same question, and students should be encouraged to keep them separate. Even if an administration claims domestic authority under Article II, it still faces international law arguments about sovereignty, consent, UN authorisation, and self-defence. On the domestic side, the questions are more straightforward. Did the operation trigger the War Powers Resolution reporting framework. Does it fall within existing statutory authorisation? If any further military intervention is needed in Venezuela, will Congress respond by endorsing, restricting, or attempting to terminate or limit further action through legislation and funding? Conclusion The president is not constitutionally meant to have an unlimited personal power to wage war. Yet modern practice shows that presidents can and do initiate military action, sometimes very significant action, without prior congressional authorisation, especially when operations are presented as urgent, defensive, or limited. Congress retains powerful tools: authorisations, oversight and the power of the purse. And the War Powers Act is an explicit attempt to force accountability. But history also shows that Congress does not always use those tools decisively, which is one reason why presidential war powers remain one of the most contested features of the American system.
