← Back to the dossier

23 September 2026 · United Nations

The UN Security Council takes it up

During the General Assembly, the Security Council held a meeting on AI. Sam Altman spoke there. Clément Delangue, the chief executive of Hugging Face, appeared by video. Two months after agents from one company broke into the other, both were at the same table in New York.

PoliticsCheck before quotingOne source, or numbers that are still moving. Read the original before repeating it.

What happened

The Security Council is the body that handles threats to international peace and security. It is not where software bugs go.

This entry is short because the substance is thin so far. What matters is the venue. In January the AI question was a consumer-protection matter for national regulators. By September it was on the agenda of the Security Council, with the chief executives of the company that caused the incident and the company that suffered it both present.

What it points at

Jakub Pachocki asked for exactly this in his essay on 6 September: international coordination as a top priority for governments. Seventeen days later the Security Council met.

Whether anything follows from a meeting is a separate question, and the honest answer is that Security Council meetings mostly produce meetings. But note where Europe is in this picture, which is nowhere in particular. See what Brussels was doing instead.

What we do not know

What was actually said, and whether any text came out of the meeting, is not established here. The UN publishes its own records; link them and this entry becomes worth more.

Editor's notewhat we make of it, kept apart from what happened

Thin entry, useful slide. Eight months from a consumer-protection question to the Security Council is the fastest-moving fact on this page.

Do not imply anything came out of the meeting. Nothing is known to have.

Sources

  1. New York Times: how OpenAI's rogue AI agents tried to trick a robot detectorpress · main sourceThe meeting is reported in the photo captions rather than the body text, which is why this entry is thin.

Read next