Who commands Iran's war? Coordination is on the record. Command below the top is not

The finding

On 8 April 2026, about two hours after the United States President announced a two-week ceasefire, Iran’s state broadcaster read a statement. The war had not ended, it said, “but all military branches should follow the Supreme Leader’s order and cease their fire”. Iran’s Supreme National Security Council confirmed that it had accepted the ceasefire and would negotiate in Islamabad.

That one sentence is the clearest piece of evidence in the public record about who commands Iran’s war — and it shows something narrower than it seems to. It shows that the authority to stop the war sat with the Supreme Leader, and that the order was addressed to every branch at once. It does not show how the order travelled to the forces, whether one military headquarters passed it to both of Iran’s armed forces, or whether each received it through its own chain.

Iran fights with two armed forces: the Islamic Revolutionary Guard Corps and the regular army, the Artesh. Two forces acting toward one objective do not automatically mean two independent wars. Nor do they mean that one headquarters commands both. Coordinating two organisations and commanding them are different things, and the evidence for each is different. This Note tests where Iran’s public wartime record actually meets the higher bar. The short answer is that it meets it at the top and stops below it. Command is on the record where the Supreme Leader acts. Coordination is on the record beneath him. A single operational chain commanding both forces is not on the record at all.

Iran has two armed forces

The Artesh is Iran’s national military: a ground force, a navy, an air force and an air-defence force, with a mission framed around defending the country’s territory. The Revolutionary Guard was created in 1979, months after the revolution, as a second military to defend the revolution itself. Over four decades it built its own ground forces, its own navy and its own aerospace force — and acquired the capabilities this war has turned on: the ballistic missile and drone programmes, and the asymmetric naval mission in the Gulf.

So Iran has two navies in the same waters, two sets of missile and drone forces, and two command structures that meet only at the top. That is why the command question matters for everything else this module analyses. Who can order a strike on a Gulf energy target, whose ceasefire binds, and whether a ship attack in the strait was a decision of the state or of a unit are all questions about where the two chains converge.

The top of the system is clearer

Iran’s constitution leaves no doubt about the summit. Article 110 makes the Leader the holder of “supreme command of the armed forces”, gives him the declaration of war and peace, and gives him the appointment and dismissal of the chief of the joint staff, the commander of the Revolutionary Guard and the commanders of the armed forces. Article 176 gives the Supreme National Security Council, chaired by the president, the task of determining defence and security policy within the Leader’s framework — and its decisions take effect only once the Leader confirms them.

The war has shown that authority being used. The Supreme Leader killed on the war’s first day, Ali Khamenei, was succeeded by his son Mojtaba, selected by the Assembly of Experts and announced on 8 March. On 10 August the new Leader issued decrees filling the senior military posts: a chief of the General Staff and his deputy, the Guard’s commander-in-chief, its deputy, its naval commander and the head of the Basij. And the 8 April order was issued in his name.

The president, by contrast, is not in the military chain. On 7 March President Masoud Pezeshkian apologised to Iran’s neighbours and said they would no longer be targeted unless attacks came from their territory; the Revolutionary Guard answered the same day with a warning of “crushing strikes” on American and Israeli bases and interests, and the strikes did not stop. That is not evidence of insubordination. It is the constitution working as written: political authority over the forces sits with the Leader, not with the elected government.

Certainty begins to fall one level down.

The headquarters in the middle

Two bodies sit between the Leader and the two forces.

The Armed Forces General Staff was created in 1988, in the last weeks of the war with Iraq, to coordinate the two militaries the revolution had left running side by side. The US Defense Intelligence Agency, in the most detailed public description by a foreign government, calls it Iran’s senior military body, setting military policy and strategic guidance, and records that both service commanders report to its chief. In the same pages it records that the two militaries “usually conduct operations independent” of each other.

The Khatam al-Anbiya Central Headquarters is the body whose title suggests the answer. The same report says that in 2016 it was separated from the General Staff as a standing command “responsible for operational command and control” — before then it was stood up only in wartime. It must not be confused with two other bodies carrying the same name: the joint air-defence headquarters and the Revolutionary Guard’s construction conglomerate.

What is documented about the Central Headquarters is its existence, its commanders and its voice. Its first commander after 2016, Gholam Ali Rashid, was killed on the opening day of the June 2025 war, and his successor within days. In the 2026 war its spokesman has announced Iran’s operations as those of “the armed forces”: on 2 April he set out the ninetieth phase of the strike campaign Iran calls True Promise 4; on 8 June the headquarters declared an end to operations against Israel; on 2 September it described the missile and drone attacks on American bases after the United States strikes and warned states that help American forces to “accept the dangerous consequences”.

What is not documented is the authority its title implies. No Iranian statute or published order setting out its command over the two forces has been found. The Defense Intelligence Agency’s description is a foreign government’s account of the structure in 2019, not a record of how it worked in 2026.

Coordination is not command

The strongest evidence of joint activity in this war is real, and it is evidence of coordination.

Iran’s strikes on Israel, on American bases and on the Gulf states have been announced in two ways. The Revolutionary Guard numbers each wave of True Promise 4 and claims it through its own public relations office — the sixty-fourth wave on 10 June, among dozens. The Artesh claims its own drone strikes, under its own operation name, Sa’eqeh, through its own public relations office: on 24 July state media carried its claim to have hit American facilities in Bahrain, Jordan and Kuwait in the operation’s twenty-fourth and twenty-fifth phases, without reference to the Guard or to the Central Headquarters. Two campaigns toward one objective, each run and claimed by its own service, with a joint spokesman speaking over both, is what coordination looks like. It is also what command could look like from outside. The record cannot tell the two apart.

The strait shows the same pattern in the open. On 28 September Rear Admiral Habibollah Sayyari, the Artesh’s coordination deputy, said the western part of the Strait of Hormuz, the strait itself and the Persian Gulf are under the full control of the Guard’s navy, and the eastern part and the northern Indian Ocean under the Artesh navy. That is deconfliction by geography: two navies given separate waters so that they do not interfere with one another. It is not, by itself, evidence that one headquarters commands both.

The exception is air defence. On 8 March the Central Headquarters’ spokesman said — in a statement read here through a Yemeni outlet’s relay, not at its Iranian source — that air-defence systems belonging to the Artesh ground forces, the Artesh air-defence force and the Guard had engaged drones “under the command” of the country’s joint air-defence headquarters. That body has existed since 1992 to coordinate the two militaries’ air defences and was given command of the Artesh’s air-defence units in 2008. The statement is Iran’s own account of its own operations, and it is the only one found in this war that places units of both forces under one command. With that institutional history, it makes air defence the one domain in which Iran states a joint command — and it carries no claim about any other domain, which makes the absence everywhere else easier to see.

The pattern runs in one direction. Shared objectives are documented everywhere. A single voice is documented for most of what the Guard does. Coordination is documented where it can be seen — in the sky and on the water. Tasking by one headquarters across both forces is documented nowhere outside air defence. Shared timing is not shared command; a common objective is not a common commander; a joint statement is not operational control; and keeping two navies apart is not ordering them.

What would command look like in evidence?

Command leaves a different trace from coordination. It shows as an order that crosses a chain:

• Task — one headquarters assigning a mission to a Guard unit and an Artesh unit in the same operation.
• Redirect — the same headquarters changing that mission once under way.
• Countermand — cancelling an operation one service had planned.
• Allocate — moving scarce means between the forces: missiles, aircraft, air-defence systems, surveillance.
• Set rules of engagement — one set of rules binding both.
• Impose restraint — an order to stop that both obey, and that the record shows both obeying.

The public record holds one of these clearly, and at the top rather than the middle: the 8 April order to all branches. It went out through the national security council in the Supreme Leader’s name, not through the Central Headquarters, and no separate acknowledgement by the Guard or the Artesh has been found. Gulf states reported launches on the day itself, and when each was fired relative to the order is not established. Rules of engagement are on the record only for one force and one domain: in May the Guard’s navy was reported to have announced new rules for the waters off Iran’s coast, and the Guard’s commander to have said that any ship passing without authorisation was a legitimate target. Nothing published says who allocates missiles or air defence between the forces.

The record also holds evidence pointing the other way, and it is graded where it stands. On 1 March, with much of the senior command dead, Iran’s foreign minister, Abbas Araghchi, said Iran’s military units were “now independent and somehow isolated”, acting on general instructions given in advance. That is a reading in which neither live command nor live coordination describes the war’s opening, because the orders the units acted on had been issued before it. A New York Times investigation published in September, read here only through other outlets’ relays, reported on unnamed officials’ accounts that the Guard’s commander had neither authorised nor known of the attacks on ships in the strait on 7 July, and that an official outside the formal chain had ordered them. Vigil records that account as reported, and the argument does not rest on it.

Leadership changed. Did the system?

The war has replaced almost every senior officer in Iran’s command. The chief of the General Staff, Abdolrahim Mousavi, and the Guard’s commander-in-chief, Mohammad Pakpour, were both killed on 28 February; the Guard’s naval commander was killed in March. The Artesh’s commander-in-chief, Amir Hatami, has spoken publicly since.

The two posts were refilled at very different speeds. The Guard’s commander was named the day after his predecessor’s death — before a new Supreme Leader had been selected, by an authority the public record does not establish — and confirmed by decree in August. The General Staff had no published chief for five months, until the August decree appointed Ali Abdollahi, reported to have commanded the Central Headquarters since June 2025. Operations continued throughout. A war fought for five months without a published head of the General Staff is consistent with the readings that place operational authority in the services or in instructions issued in advance. It does not prove them.

Most of these changes are personnel change: new officeholders in the same offices. One is not. The August decree instructed the new chief to complete the integration of the General Staff and the Central Headquarters, on directives attributed to the late Supreme Leader. That is a change to the institution itself, ordered in the middle of a war. It shows that the two bodies were still separate five months in, and that Iran’s own leadership chose to alter how its command is organised while fighting. The form of the merged body, whether the integration is complete and who now commands the Central Headquarters are not published. The merged headquarters is now the observable most likely to put the relationship between the joint command and the two services on the record.

What we can actually say

The model the public record supports has four parts.

Command converges at the top. The Supreme Leader holds formal command of both forces, appoints their commanders, and issued the war’s clearest order to stop. This is documented.

Below him, the two forces are coordinated. A joint headquarters speaks for both; the strait is divided between them; retaliation is announced in the name of “the armed forces”. This is documented as coordination, and it is the thing a reader most easily mistakes for command.

The services run their own campaigns. Each numbers, announces and claims its own strikes. Whether a joint headquarters tasks those campaigns is not established.

One domain is integrated. Air defence runs under a joint command, on Iran’s own account and on an institutional history going back to 1992.

That is closest to the second of the three models this question is usually framed in — central coordination over parallel chains — with a top that is firmer than that model implies and an exception in air defence. It is not proof that no unified operational command exists. Iran publishes no command instruments, a state at war does not publish its orders, and a gap in the public record is graded no higher than the visibility of the thing. What can be said with confidence is narrower and more useful: the public record establishes coordination more clearly than command, it shows exactly where the evidence stops, and it names what would move it.