OpenAI DevDay Exchange 2026: Eight Cities, One Application Deadline

OpenAI is taking DevDay on the road. On August 18, 2026, @OpenAIDevs announced DevDay Exchange 2026 — eight standalone developer events spread across Asia, Europe, and Latin America, starting in October. The tweet put it plainly: "OpenAI DevDay is going global. Starting this October, DevDay Exchange is bringing builders together to swap build notes, share real projects, and meet the teams building OpenAI tools."

It's the first time OpenAI has run DevDay as a distributed city tour rather than a single flagship keynote. If you build with the OpenAI API, Codex, or ChatGPT tooling and live near one of the eight stops, here's what's actually on offer, how to apply, and a couple of honest observations worth knowing before you do.

TL;DR: DevDay Exchange 2026 at a glance

The full city-by-city schedule

Per the official DevDay Exchange 2026 page linked in OpenAI's announcement, here are all eight dates in order:

Every event starts at 2pm local time. OpenAI's own copy is explicit that venue details and the full program are shared only "following application approval" — so the public listing is intentionally light on logistics until OpenAI has vetted who's coming.

The Bengaluru stop isn't happening in isolation — explainx.ai already flagged it in passing while covering Build What Moves India, the Varun Mayya-led civic UX hackathon that's a separate initiative running in the same city and season. This post is now the fuller writeup of the DevDay Exchange side of that pattern.

What's actually covered at each stop

OpenAI lists four things attendees should expect, straight from the event page:

1. Technical sessions with OpenAI product and engineering teams — not marketing talks, per OpenAI's framing, but working sessions with the people who build the tools.
2. Real-world projects and Codex workflows from top founders and developers — case studies from builders already shipping with Codex, not hypothetical demos.
3. Hands-on guidance for your projects — bring what you're building and get direct feedback, closer to office hours than a keynote.
4. Open conversations with the OpenAI team and leading builders — unstructured time with both OpenAI staff and other attendees.

OpenAI's own description frames it well: "Each event is shaped by its city — creating a space to exchange ideas, share what they're building, learn from one another, and connect directly with OpenAI teams." That's a deliberate departure from a one-size-fits-all touring keynote — expect a Tokyo session to look different from a São Paulo one, tuned to what each local developer community is actually building.

How to apply, and what to watch for

Applications go through events.openai.com, and the deadline is the same across all eight cities: September 4, 2026. A few practical notes worth flagging before you submit:

• Space is limited at every stop. OpenAI states this directly, and given eight cities are launching simultaneously with one shared deadline, expect selective admission rather than first-come-first-served registration.
• Approval comes before details. You won't see the venue or the exact program until OpenAI approves your application — plan travel and calendar holds conservatively until that confirmation lands.
• One deadline for all eight cities, even though the events themselves are staggered nearly a month apart (October 16 to November 11). Applying early for a later date doesn't appear to buy any advantage in the public messaging — the cutoff is the same regardless of which city you're targeting.

What's missing: no US city, and a signup rough edge

Two things are worth calling out plainly, both sourced to reactions under OpenAI's own announcement tweet rather than to any OpenAI statement.

No US city made the list. All eight DevDay Exchange stops are international — Bengaluru, Tokyo, Seoul, Berlin, Paris, London, São Paulo, and Mexico City — and at least one reply under the @OpenAIDevs tweet pointed this out directly. OpenAI hasn't explained the omission publicly. The likely reasoning is that this specific series is meant as an international expansion layered on top of the existing US-based flagship DevDay, but that's a reasonable inference, not something OpenAI has confirmed.

A minor comms gap, per at least one attendee. Another reply under the announcement noted that the international DevDay site previously had a "notify me via email" signup option — and that, for them at least, it apparently didn't fire when the Exchange announcement went live; they found out from the tweet itself rather than an email. This is anecdotal, sourced to a single reply, not a documented or widespread failure — but it's a small, honest data point if you'd been counting on that notification list to know when applications opened.

Neither point should stop anyone eligible from applying. They're the kind of rough edges that show up whenever a company launches a first-of-its-kind global event series simultaneously across eight markets — worth knowing, not worth over-reading.

Why this matters beyond the eight cities

This is part of a broader pattern of OpenAI investing directly in regional developer communities rather than running everything through one US-centric event. It lands the same month as OpenAI-backed regional initiatives like Build What Moves India in Bengaluru, and follows reported leadership changes inside OpenAI that make the company's public-facing developer relations work worth watching closely this year.

Four of the eight cities — Berlin, Paris, London, and, adjacently, the wider European sovereign-AI conversation — sit inside a region explainx.ai has covered in depth from the regulatory side: see the Europe AI landscape guide covering the EU AI Act and sovereign compute build-out, and the UK AI landscape guide on the UK's AISI and pro-innovation regulatory stance. A US foundation model vendor running hands-on developer events inside that regulatory environment is itself worth watching — expect DevDay Exchange sessions in Berlin, Paris, and London to field real questions about EU AI Act compliance and data residency, not just feature demos.

On the Bengaluru side, DevDay Exchange sits alongside India's own sovereign-AI push — see explainx.ai's coverage of Sarvam's Epoch announcements from Bengaluru for the local model-layer context that a US-vendor developer event doesn't replace.

If you build agent workflows with Codex and want a structured deep dive before an Exchange stop, explainx.ai's Codex slash commands reference guide and Codex plugin for Claude Code guide are good prep reading — sessions covering "real-world Codex workflows" are exactly the kind of content those guides already document hands-on.

Related on explainx.ai

• Build What Moves India: OpenAI Hackathon — the Bengaluru civic-tech hackathon running the same season
• Sarvam Epoch 2026 announcements from Bengaluru — India's model-layer context
• Europe AI landscape: sovereign compute and the EU AI Act
• UK AI landscape: pro-innovation stance and AISI
• Codex slash commands complete reference guide
• OpenAI Codex plugin for Claude Code guide
• OpenAI leadership and safety team changes, August 2026
• explainx.ai workshops — live, instructor-led sessions if you want structured practice before an Exchange stop

Official sources: DevDay Exchange 2026 application page · @OpenAIDevs announcement on X

This post reflects OpenAI's public DevDay Exchange 2026 announcement and application page as of August 19, 2026. Dates, application requirements, and city details are controlled by OpenAI and may change — check events.openai.com directly before finalizing travel plans.