Wire
21:47ZNOELREPORTUkrainian forces attack Russian port of Novorossiysk, Russian air defenses respond21:46ZPALESTINECIran links Strait of Hormuz reopening to ending conflicts in Gaza, Lebanon21:46ZAMKMAPPINGClashes reported in Hadramaut Governorate, Yemen21:46ZAMKMAPPINGTwo explosions reported in Ma'rib, northwestern Yemen; Ansarallah claims strike21:45ZAMKMAPPINGUkraine conducting massive drone attack on Novorossiysk, Russia; Pantsir-1 and S-300/400 air defense systems…21:44ZAMKMAPPINGHamas members cross Yellow Line in Gaza, take Israeli engineering equipment overnight21:43ZAMKMAPPINGRussia ballistic missile threat issued for Kyiv area in coming hours21:40ZDISCLOSETVU.S. District Judge Indira Talwani blocks USPS from implementing part of Trump's executive order
  • S&P 500 ETF 0.02%
  • Nasdaq 0.60%
  • Nasdaq 100 0.33%
  • Dow ETF 0.06%
Terminal ↗
← The MonexusMena

Pezeshkian calls contact with Khamenei 'very difficult' as Hormuz draft reportedly awaits sign-off

On 5 August 2026, AP reporting relayed via Telegram said Iranian and Omani negotiators have finalised a Hormuz reopening draft pending the supreme leader's sign-off. The same day, Iran's president publicly described communications with Khamenei as 'very difficult'.

On 5 August 2026, AP reporting relayed via Telegram said Iranian and Omani negotiators have finalised a Hormuz reopening draft pending the supreme leader's sign-off.
On 5 August 2026, AP reporting relayed via Telegram said Iranian and Omani negotiators have finalised a Hormuz reopening draft pending the supreme leader's sign-off. @thecradlemedia · Telegram

At 19:15 UTC on 5 August 2026, the monitoring channel GeoPWatch relayed an AP wire reporting that Iranian and Omani negotiators had finalised a draft agreement to reopen the Strait of Hormuz, with the text awaiting the final sign-off of "Iran's supreme leader." The same GeoPWatch post carried a second AP item in which Iranian President Masoud Pezeshkian described interactions with the supreme leader's office as "very complicated." Separately, France 24 identified that office-holder as Mojtaba Khamenei and reported Pezeshkian's framing that communication with him is "very difficult," citing the leader's reported wounding in the June US-Israeli strike.

Two facts now sit on the public record, and they do not, on the evidence available here, fit together as a single causal story. A draft exists. A bottleneck exists. The cited reporting does not establish that one caused the other.

What the AP relay says

The GeoPWatch post carries two distinct AP items. The first reports a negotiated text awaiting the supreme leader's sign-off; the second carries Pezeshkian's "very complicated" formulation. AP itself is named as the originator; GeoPWatch functions as the relay channel. The cited item identifies the signatory only as "Iran's supreme leader" and does not, in the post itself, attach the name Mojtaba Khamenei to the Hormuz sign-off requirement. France 24, in a parallel wire, supplies the name. The most defensible reading is that Pezeshkian's own remarks, plus France 24's identification, establish the office, while the AP-side framing of the bottleneck rests on the office's identity rather than on any explicit on-the-record confirmation that Khamenei personally is the hold-up.

The same AP reporting does not specify the substantive terms Iran and Oman have agreed, the date by which sign-off is expected, or what questions remain live beyond the final approval. Senior diplomatic sourcing cited elsewhere on 5 August has reportedly described "one or two issues" as still unresolved between Tehran and Muscat; that material does not appear in the cited thread items and is therefore not load-bearing here. Monexus flags it as a contradictory reading worth testing, not as a settled fact.

What Pezeshkian said, and what he did not

Pezeshkian's remarks, circulated by the monitoring accounts Open Source Intel and ClashReport and posted in parallel by OSINT613 on X, form the day's second data point. He said "communicating with Mojtaba Khamenei is very difficult now," while insisting that Khamenei's presence remains "a significant source of strength" allowing the system to "maintain the process." In the same cluster of remarks, posted to X and relayed by Open Source Intel, the president said: "No matter how much I think about it, I cannot find any logical reason why they killed our Leader, our commanders, and our scientists."

A separate set of remarks, circulated by both Open Source Intel and ClashReport, addressed Iranians living abroad. Pezeshkian said the "martyred Leader" had agreed that Iranians abroad "should not face any problems if they returned," and added that "even if someone had an issue, we should tell them to come back." The Open Source Intel post carrying these remarks is timestamped 19:31 UTC on 5 August 2026; the ClashReport post carrying the same excerpt is timestamped 18:55 UTC the same day. The available source items do not specify whether the diaspora remarks were delivered in the same venue or address as the Khamenei comments, or whether they preceded or followed the AP relay on Hormuz. Monexus reads the remarks as a domestic signal aimed at Iranians weighing whether to return in the current security environment; that reading is Monexus analysis, not a sourced conclusion.

Two limits on the day's reporting deserve naming. First, Pezeshkian's "very difficult" formulation establishes a communications constraint. It does not, on the cited evidence, establish that this constraint is the specific reason the Hormuz draft has not moved. Second, the remarks about the strike, as quoted in the cited inputs, do not include any operational reference to retaliatory posture. The cited inputs contain no such reference; this article has not independently established whether one exists in other reporting.

Monexus assessment: a constrained system, not a collapsed one

Monexus reads 5 August as a day that put two facts on the same page without connecting them. A reopening text exists, per AP via GeoPWatch. Pezeshkian says his supreme leader is hard to reach, per France 24, Open Source Intel and ClashReport. The headline question, whether the access problem is the cause of the delay or merely coincident with it, is the question the day's reporting cannot answer.

Three variables will move the file. An Omani read-out clarifying whether Iranian counterparts retain authority to initial the text, or whether substantive issues remain open between the two sides. A public appearance by Khamenei that resolves, even partially, the question of his operational capacity. Or, in the other direction, continued silence on Khamenei's condition, a draft that does not move, and no mediator confirmation of authority. In that scenario the bottleneck starts looking more like a substantive gap than an access problem, and the leverage Tehran accumulated after the June strike looks more brittle than the daily briefings suggest.

For now the operative facts are narrow and verifiable, and the connection between them is not.

This piece was assembled from France 24 wire reporting, AP reporting relayed by GeoPWatch on Telegram, and Pezeshkian transcripts circulated by Open Source Intel and ClashReport, with parallel posts by OSINT613 on X. Where the cited items do not specify a detail, the supreme leader's condition, the text's terms, the question of acting authority, this article has said so rather than infer.

Wire provenance

This editorial synthesis draws on the following public wire/social posts:

  • https://www.france24.com/en/middle-east/20260805-iran-president-says-contact-with-supreme-leader-is-very-difficult
  • https://t.me/GeoPWatch/38211
  • https://t.me/osintlive/562167
  • https://t.me/osintlive/562166
  • https://t.me/osintlive/562171
  • https://t.me/ClashReport/91620
  • https://t.me/ClashReport/91616
© 2026 Monexus Media · AI-native reporting from public-source material