For more than two centuries, the division of war powers between Congress and the president has remained a subject of intense debate. When the framers of the U.S. Constitution gave Congress the authority to declare war and the president the responsibility to command the military, they lived in a time when warfare moved slowly, and communication was limited. Today, with modern military technology and instantaneous communication, those same constitutional lines are often tested — especially when presidents act without consulting Congress. The issue was reignited recently when President Trump ordered airstrikes on Iranian nuclear facilities without first seeking congressional approval, drawing swift criticism from lawmakers who view the move as a violation of their constitutional role.
Senator Mike Kelly, a Democrat from Arizona, acknowledged on NPR’s Morning Edition that there is little Democrats can do to compel the administration to follow proper channels, but he emphasized the importance of respecting constitutional tradition. “The administration should comply with the Constitution,” Kelly said. “Traditionally, presidents have done that. I know recently that sometimes, with certain actions that are viewed as protecting the safety of our country, presidents can act, and then they should be able to notify us.” Senator Tim Kaine, a Democrat from Virginia, took a more forceful stance during his appearance on CBS’s Face the Nation, stating: “The United States should not be in an offensive war against Iran without a vote of Congress. The Constitution is completely clear on it. And I am so disappointed that the president has acted so prematurely.”
What the Constitution Says – and What Presidents Actually Do
The U.S. Constitution makes clear distinctions: Article I grants Congress the power “to declare War, grant Letters of Marque and Reprisal, and make Rules concerning Captures on Land and Water.” Article II names the president as “Commander in Chief of the Army and Navy of the United States.” This structure was designed to ensure that while the president can direct military action, it should only come after Congress has authorized conflict. Rebecca Ingber, a law professor at Cardozo Law School, says the framers intended war-making decisions to come from Congress. “I think it’s pretty clear that the framers thought that any time we were going to be making the decision to go to war with another country, that was going to be a decision for Congress,” she says.
However, history shows that presidents have long operated in gray areas. One early example was the Quasi War between the United States and France in the late 1700s. Despite the hostilities, no formal declaration of war was ever issued. Stephen Griffin, a constitutional law professor at Tulane Law School, notes that such practices became more common after World War II. The development of nuclear weapons and the speed of modern warfare made immediate presidential responses more practical. “The creation of the atom bomb changed the game,” Griffin explains. Unlike the early days of the republic, where it could take months to move troops, modern scenarios may require immediate action.
The founding of the United Nations also influenced American legal thinking. With the U.S. playing a key role in establishing the U.N. in 1945, the international framework shifted the discussion from declarations of war to the “use of force,” especially since the U.N. Charter allows military action only in self-defense or with Security Council approval. As a result, U.S. presidents increasingly sought legislative approval in the form of Authorizations for Use of Military Force (AUMF) rather than formal war declarations. “The constitutional requirement is about legislative approval,” Griffin explains, “not literally picking up a document that says ‘Declaration of War’ and signing it.”
