OpenAI DevDay 2026: All 25 Announcements and Who Gets Them

OpenAI’s DevDay recap contains 25 product announcement entries. They do not all describe features you can use immediately. This table preserves the published access distinctions so a team can identify what to evaluate now, what needs setup and what remains a preview or future release.

Editorial note: Prepared October 1 as a September 29, 2026 dispatch, using the dated announcements cited below. Later product developments are outside this article’s scope.

The enumeration follows OpenAI’s September 29 recap in order. The linked announcement names lead to primary evidence. “Available” records the announcement’s status, not a successful login test. “Mixed” means an available component is paired with a another announced maturity or surface stage. Entries only in preview or beta keep that label, even when broader access is planned. October 1 documentation caveats do not change this announcement-status coding. “Interest” means the source invites eligible customers to express interest rather than establishing a general self-service release.

The snapshot date and collection date differ. We collected the material on October 1 and checked linked implementation guidance then. Where those living docs state a narrower restriction, the table preserves it. This is especially relevant to plugin surfaces and preview access. It does not establish that every later documentation detail was present on announcement day.

The audience column preserves the source’s named plans. A plan missing from one row is not automatically excluded from the entire product family; it is simply not added to that row without evidence. Likewise, “all plans” should not erase a platform or configuration restriction stated in the implementation guide.

Sixteen entries are coded Available, four Mixed, two Preview, one Coming soon, one Beta and one Interest. These counts sum to 25. They describe how this census labels the announcement entries; they are not adoption figures, performance measurements or a count of capabilities enabled in a particular account.

A mixed entry stays mixed even if its most prominent feature is available. Astra Ultrafast and forthcoming Sol Ultrafast belong to one recap entry, for example. Splitting them would change the unit of collection and inflate the headline count. The same rule keeps Private Intelligence and the plugin creation bundle intact.

Start with a workflow and identify which announcement changes its feasibility. A team that needs unattended coding work should inspect cloud-environment setup. A team that needs a browser inside an application should inspect origin approvals and action boundaries. A team that needs persistent personal delegation should review dots’ permissions and usage treatment.

The detailed guides on dots, Agents API computer use and Codex workflows explain the acceptance questions for those paths. The pre-event preparation guide remains historical context.

Use the source row that matches the decision you are making. An announcement can establish that a capability was introduced; a setup guide can establish the requirements described when it was read. Neither proves that your organization has access or that a workflow will meet its quality standard. Those questions require a check in the intended account and a task-specific evaluation.

For implementation context, see AI transformation. This census remains an event record rather than a product recommendation.