What OpenAI DevDay 2026 means for designers

OpenAI DevDay 2026, held on 29 September 2026, was not a design event. It was a platform event. But for designers it may be the most important launch of the year, because it changes where your product's interface lives. According to OpenAI's DevDay 2026 recap, ChatGPT is being opened up "as a shared surface where humans and agents can collaborate", and developers can now build native experiences inside it.

The short version: your product is about to have three front doors instead of one. People will use it in your own app, inside ChatGPT through plugin extensions, and through always-on agents that act for them without opening any interface at all. Designers who plan for all three will shape how their product is experienced. Designers who only design the app will find that more and more of the experience is being designed by someone else.

This piece covers what was actually announced, what is hype and what is real, and what to change in your design practice this quarter.

What OpenAI announced that matters for design

OpenAI listed more than 20 announcements. Most are about models, pricing and developer tools. Five of them change design work directly.

Plugin extensions. OpenAI is opening the platform it uses to build ChatGPT features. In OpenAI's words, plugin extensions let a plugin have "a home in the sidebar" and "interactive panels where people can work alongside the conversation", plus viewers for the file types your product supports. The recap lists this as available to all plans. That is a new surface for UI: a panel next to a conversation, not a full-screen app.

Dots. Dots are always-on agents inside ChatGPT that learn what matters to a person and work on their behalf. The recap lists them as available on Pro and Business Premium in eligible markets, with a beta for Enterprise, Edu and Healthcare workspaces that admins can enable. For designers, dots are the clearest sign yet that a large share of product usage will come from agents, not people tapping buttons.

Pages and ChatGPT Space. Pages are a new document type built for human and agent collaboration, where people can write, research, generate charts and create images. Space is a shared home for a team, ChatGPT and a dot. This matters because it sets a new baseline for what a "document" is expected to do.

Sites can host plugins. Supported plugins can be added to the Sites people build in ChatGPT, for Business, Enterprise, Healthcare and Edu plans. Your product can now appear inside someone else's internal tool.

Figma in the OpenAI Marketplace. OpenAI named Figma among the first partners in its new Marketplace, listed for creative work, alongside Adobe for customer experience. Enterprise buyers will increasingly choose design tools inside AI platform budgets.

Hype vs reality: what actually changes

The hype reading is "apps are dead, everything happens in ChatGPT now". That is not what was announced, and it is not what will happen in the next year.

The realistic reading is narrower and more useful. ChatGPT is becoming a distribution surface with its own interface rules, the same way the iPhone home screen, the browser tab and the Slack sidebar each became one. Your product does not disappear. It gets a smaller, more contextual version of itself that lives next to a conversation, and a headless version that agents operate.

The Three Surfaces Test

Use this test on every feature you design from now on. For each feature, answer three questions.

1. In your app: what does the full experience look like when the user has time, context and a large screen?

2. In a panel: what is the smallest useful version of this feature that could sit beside a conversation? What must it show, and what can it leave out because the conversation already holds the context?

3. As an action: if an agent performs this for the user, what inputs does it need, what does it return, and what must the user approve before it happens?

If you cannot answer the second and third questions, your feature is only designed for one of three surfaces. That was fine last year. It will look like a gap by next year.

What to change in your design practice

Design panels, not just pages. A ChatGPT side panel is narrow, sits next to text, and is used mid-task. It should open on the one thing the user came for, reuse the conversation's context instead of asking again, and hand back to the chat cleanly. This is closer to designing a widget than a website. If your team has not practised compact, contextual UI, start now.

Treat permissions as a core flow. OpenAI says users choose which plugins to use and approve the access each one receives. That approval moment is now part of your onboarding. A vague permission request will lose users before they ever see your interface. Write it like a product promise: what the plugin reads, what it can change, and how to undo it.

Design for the agent as a user. A dot that works for someone will use your product through actions and data, not through your beautiful layout. That means clear, well-named actions, predictable results and readable errors. The patterns in agentic UX and in making your SaaS agent-ready with an MCP server apply directly. OpenAI also said plugins will support the proposed MCP Events specification, so events in your product can trigger automations.

Design the waiting. Always-on agents and panels that call your service mean more moments where something is working in the background. Status, progress and "done while you were away" summaries become first-class UI. Motion design for AI covers how to make those states feel intentional.

Keep your own app excellent. When a light version of your product lives in ChatGPT, the full app has to justify the switch. That is where depth, brand and craft still win.

The fear: does this make designers less necessary?

It is a fair question, and the honest answer is that it moves the work rather than removing it. When a platform like ChatGPT provides the frame, a lot of visual decisions are made for you: spacing, typography, container behaviour. That can feel like a loss of control.

But look at what is left. Someone has to decide what the smallest useful version of a feature is. Someone has to design the permission request that earns trust. Someone has to define the actions an agent can take and what the user sees when it gets them wrong. Those are harder design problems than choosing a button radius, and they are exactly the problems that separate products people trust from products they uninstall. The longer argument is in will AI replace UX designers.

The designers at risk are the ones who only produce screens. The designers who gain are the ones who design behaviour across surfaces.

How to try it this week

• Read the DevDay 2026 recap and list which announcements touch your product.

• Pick one core feature and run the Three Surfaces Test on it with your team.

• Sketch a narrow side-panel version of that feature at a realistic width, next to a block of chat text.

• Write the permission copy a user would see if your product became a plugin.

• List the three actions an agent would most likely take in your product, and what each should return.

If you want help turning that into a real product plan, Digcy works on exactly this layer as an AI product development partner and a UI/UX agency in Casablanca serving teams globally.

FAQ

What did OpenAI announce at DevDay 2026?

OpenAI announced more than 20 updates on 29 September 2026, including dots (always-on agents), GPT-6.1 Sol, plugin extensions for ChatGPT, ChatGPT Space and pages, collaborative slides, Codex updates, an Agents API with computer use, a Pro 500 plan and an OpenAI Marketplace that includes Figma.

What are ChatGPT plugin extensions?

Plugin extensions let developers build their own experiences inside ChatGPT: a home in the sidebar, interactive panels that sit alongside the conversation, and viewers for their file types. OpenAI lists them as available on all plans.

Will ChatGPT plugins replace apps?

No. They add a new surface, they do not remove the old ones. Expect a compact, contextual version of many products to live inside ChatGPT, while the full app remains where deeper work, brand and complex tasks happen.

Is DevDay 2026 overhyped for designers?

Parts of it are, especially claims that interfaces no longer matter. The real change is that interfaces now appear in more places and are sometimes operated by agents, which makes interaction design, permissions and product behaviour more important, not less.

What should designers learn after DevDay 2026?

Compact contextual UI for panels, permission and trust flows, designing actions and results for agents, and background status and progress states. These skills carry across ChatGPT, other assistants and your own product.