OpenAI’s September 29 recap covered Dots, GPT-6.1 Sol, Ultrafast, Decisions API, Agents API computer use, plugin extensions, MCP events, ChatGPT Space, team tasks, and more. These are separate products and availability varies.
A focused guide to the agent, app, model, and workspace changes announced at DevDay 2026. Think of this as a small research or drafting assignment. Source, date, uncertainty, and a review point make the outcome usable.
Editorial route
Treat the recap as a map, not a single release
DevDay brought together announcements for different audiences. A person deciding whether to use Dots, a team configuring Space, and a developer evaluating an API should not receive one generic "available" answer. Each child guide names its intended role and a bounded way to test relevance. For implementation or purchase details, follow the current official documentation because preview access and plan limits can change after the recap.
Choose a route
Guides in this section
Pick the specific page that matches the work in front of you. Each guide has a flat URL, a concrete review point, and links back to this overview. If the request spans several guides, finish one bounded piece before adding the next.
No matching guide. Try a broader word.
Define the task
How to use this section
For this job the raw material is announcement topic and your intended use. Explain which part is authoritative and which part is only background, then state what to do when they disagree.
A useful deliverable
A route to the relevant guide and official source. Where there are several options, show the tradeoff that would make each one sensible.
Worked situation
How this plays out in practice
The announcements span consumer agents, developer interfaces, models, plugins, and team collaboration. A reader who needs Dots access has a different next step from a developer evaluating Decisions API. The decisive information is easy to overlook in a generic task. Require it to appear in the output before moving to an action.
Sort every announcement by audience, availability, and the official documentation that governs implementation. Treat the recap as a dated starting point. The result should remain useful when someone checks it with the original document or account open.
A practical sequence
Run a bounded first pass
Collect announcement topic and your intended use and mark any sensitive material that does not need to leave its current place.
Read each announcement in the context of who can use it today: consumer, developer, team admin, or preview tester. Follow the official source from a child guide when the detail matters. Require the answer to show its assumptions before it recommends a next step.
Check the current status, then enforce do not mix a devday api with a dot feature. Repeating a task should not repeat a completed action.
Editorial judgment
Where a plausible answer can fail
A preview announcement and a generally available feature should not share an unqualified "available now" label. Check each child page before acting. Look for a silent assumption about date, identity, or scope. Name it before the workflow continues.
A recap is a snapshot. Check current docs before purchasing a plan or implementing an API. A smaller answer that accurately marks uncertainty is still progress: it tells you what to check next.
Where to go next
Connect this result to the right follow-up
If you are new to the product, Get Started & Trust helps establish the account and permission basics before you use this section as a working plan. The related guides below provide a deliberate second step after you inspect this result.
For a closely related outcome, open ChatGPT Space: Pages, Files and Team Collaboration. That guide focuses on understand ChatGPT Space as a shared surface for people and agents. It may use some of the same context, but you should confirm the source and the decision point again. If your next question is about a different angle, GPT-6.1 Sol Explained is a better fit: what GPT-6.1 Sol adds for coding and professional work. A new deliverable should have its own date, owner, and acceptance check.
Before you reuse this result elsewhere, look at Get Started & Trust for the wider product or review boundary. Take forward the verified facts and leave behind any assumption that was specific to this example. If the source has changed since the draft was made, update the relevant claim first. The purpose of the link is to make the next step more precise, not to imply that every connected guide is needed for every reader.
Adapt this
Build your own task brief
Edit the bracketed information and any sentence that does not fit your account. This is a suggested workflow, not a promise that your dot has access to a particular app or feature.
Your review
Check before moving on
Tick what you have actually checked. Your progress stays on this device for this page and can be cleared at any time.
0 of 4 checked
Questions
Frequently asked questions
Which guide should I open first?
Open the child guide closest to the result you need: a route to the relevant guide and official source. Start with its inputs and review gate, then come back to this overview for adjacent tasks.
What information matters most for devday 2026 & related openai releases?
Start with announcement topic and your intended use. OpenAI’s September 29 recap covered Dots, GPT-6.1 Sol, Ultrafast, Decisions API, Agents API computer use, plugin extensions, MCP events, ChatGPT Space, team tasks, and more. These are separate products and availability varies. Give the exact source or account where a decision depends on it.
How do I combine two related workflows?
Define separate results and approval points. A recap is a snapshot. Check current docs before purchasing a plan or implementing an API.
What would a useful result look like here?
A route to the relevant guide and official source. It should make assumptions visible and leave a trail to the source, especially for dates, prices, permissions, or changing product details.
What is the common failure in this situation?
A preview announcement and a generally available feature should not share an unqualified "available now" label. Check each child page before acting. Review that issue in the actual output instead of treating a polished presentation as proof.
Where can I check the current details?
Follow the official source linked below and inspect your account where access matters. This page was revised in October 2026; availability, terms, and product behavior can change.
Source for current product details: official OpenAI documentation or announcement ↗. The worked situations and briefs on this independent site are editorial examples. Confirm current access and details in your account. Editorial policy.
