ChatGPT Meetings plugin: from design review to Codex tasks

The ChatGPT Meetings plugin takes notes in the ChatGPT desktop app on macOS without a bot joining the call, and saves a summary with suggested action items to a page in ChatGPT Space. OpenAI launched it at DevDay on 29 September 2026 as a beta for all Pro and Business users, and the Meetings help article covers setup and data handling. For engineering teams, the useful question is how a technical design meeting becomes reviewed work in Codex instead of a page nobody opens again.

What the ChatGPT Meetings plugin records and keeps

Meetings works for online and in-person conversations. Because it uses your Mac's microphone and system audio, nothing joins the call and other participants see no bot. That also means nobody else is told automatically. The help article says you must tell participants and get their consent, and the app's reminder only reminds you.

After the meeting you get a summary and suggested action items on a page. Pages are private by default. When you share one, people get the notes, not the transcript. Audio streams to OpenAI and is deleted from your Mac and from OpenAI's servers once the notes are ready, so a meeting cannot be replayed.

Availability at launch:

Meetings is separate from the older Record feature, so do not assume settings carry over between them.

Set up Meetings on a Mac

1. Open the ChatGPT desktop app on macOS and select Plugins in the sidebar.
2. Install Meetings and complete the onboarding.
3. Allow microphone and system audio access when macOS asks.
4. Optionally connect a calendar through the Google Calendar or Outlook Calendar plugin.

On Business, if Meetings does not appear, ask your workspace admin whether Space and Meetings are enabled.

Run a design review the notes can use

A summary is only as good as what people say out loud. Design reviews often end with a nod and a shared screen, and the decision never gets spoken. That is the part a notes tool misses. A few habits help, and they cost nothing:

• Open by naming the service or repository under discussion, for example the payments API.
• State each decision as a sentence: "We keep the retry logic in the client, not the gateway."
• Name an owner for every follow-up before moving on.
• Say what is out of scope. It is the line Codex needs most later.

Ask for consent at the start, before any of this. The plugin puts that duty on you.

Turn action items into Codex tasks

The help article says one click starts an action item. It does not say what kind of task that starts, or whether it can target a specific Codex Cloud environment or repository. Test it on a low-risk item before you depend on it. ChatGPT Space pages also let you tag Codex, which is another route from the notes to the code.

Whichever route you use, sort the items first. Not every action item is agent work.

Copy the item into Codex with the context the summary lacks. This is our own template:

From the payments design review on 29 September:
Decision: retry logic stays in the client SDK, not the gateway.
Task: move the retry wrapper from gateway/retry.ts into sdk/src/retry.ts.
Out of scope: changing retry counts or backoff values.
Done when: existing retry tests pass from the new location and
gateway/retry.ts is removed. Report the test command and its output.

The decision line matters. It stops Codex from reopening a question the meeting already closed. The out-of-scope line stops a tidy-up from growing into a redesign.

Limits to plan around

Because audio is deleted and the transcript is not shared, the page is the only record. Read the summary within the hour and fix any decision it got wrong while people still remember. A wrong decision in the notes becomes a wrong task in Codex.

The macOS-only beta also means the notes depend on who in the room has a Mac with the plugin. For a team, agree who takes notes, rather than assuming everyone runs it.

We apply the same rule in our Delegate, Review, Own method: the notes are a draft, and a named engineer reviews each task before an agent starts it. For your next design review, name one note taker, get consent at the start, and turn one action item into a scoped Codex task that afternoon.

Further reading

• Meetings in ChatGPT (help article)
• ChatGPT Space
• OpenAI DevDay 2026 recap