Published on [Permalink]
Reading time: 5 minutes
Posted in:

Ask ChatGPT what DevDay means for you

I have just spent three weeks off grid in the Kimberley region of Western Australia. No feeds, no headlines, no AI news. A proper digital detox.

Then I came home and opened the laptop. OpenAI had used the gap to unload DevDay 2026, and its own recap counts more than 20 major announcements.

Catching up on AI is hard at the best of times. After three weeks away it is harder. After a product dump on this scale it is close to hopeless. A new model, always-on agents, cloud coding environments, plugins that behave like apps, collaborative documents. Every outlet has an explainer, and every explainer is the same list.

It’s getting harder to untangle all of these announcements. But I’ve thought of a better way.

Don’t ask ChatGPT what OpenAI announced. Ask it this:

Given the way I actually use ChatGPT, what should I do differently as a result?

That produces a very different answer.

What changed, briefly

Dots are always-on agents that take responsibility for continuing work rather than waiting for your next prompt. They start on Pro and Business Premium plans.

GPT-6.1 Sol is an upgrade aimed at agentic coding and computer use. OpenAI claims near-Astra intelligence at a fifth of the usual token prices, across the API and every paid ChatGPT plan.

Codex gets reusable cloud development environments and a refreshed command line tool.

Plugins are becoming applications inside ChatGPT, with their own sidebar homes and automations triggered by events in connected software.

Which of those matters depends entirely on who you are. A developer could be transformed by Codex in the cloud. Someone who asks ChatGPT to rewrite emails will barely notice. The Decisions API and AWS Bedrock Managed Agents are significant for enterprises and irrelevant to most subscribers.

Generic coverage flattens those differences. Your own ChatGPT account can put them back.

The prompt

I built this by asking ChatGPT to assess the DevDay announcements against my own rather eclectic use of AI. Paste the whole thing into the account you normally use:

Help me understand what the latest OpenAI announcements mean for the way I personally use ChatGPT.

First, search the web for OpenAI’s latest major product announcements, including the most recent OpenAI DevDay. Prefer official OpenAI sources, documentation and release notes over third-party summaries. Check what is actually available now, what is in preview and what has only been announced.

Then consider what you know about how I use ChatGPT from my previous conversations, memory and connected services where available. Identify the kinds of work I regularly ask ChatGPT to help me with, rather than simply listing everything you know about me.

Explain the announcements in plain English and assess their relevance to my actual usage.

In particular:

  1. Identify the 5 to 10 announcements or capabilities most relevant to me, ignoring announcements that are primarily interesting to developers or enterprises unless they could genuinely change something I do.
  2. For each one, explain:
    • what it is;
    • what has changed;
    • whether it is available to me now;
    • why it matters, or doesn’t matter, for the way I use ChatGPT;
    • one or two concrete examples of how I could use it.
  3. Look beyond individual features. Explain whether I should change my overall way of working with ChatGPT. In particular, distinguish when I should use:
    • a normal ChatGPT conversation;
    • deeper reasoning or research;
    • ChatGPT Work;
    • Codex;
    • plugins and connected services;
    • scheduled automations;
    • persistent or always-on agents such as Dots, if available.
  4. Identify things I currently appear to be doing manually or repeatedly that these new capabilities could do more effectively.
  5. Suggest three new workflows I probably haven’t considered but which fit the way I use ChatGPT.
  6. Tell me which new capabilities I can safely ignore for now.

Finish with a section called “What I would change this week” containing no more than five specific actions, ordered by likely usefulness to me.

Don’t simply promote new OpenAI features. If my existing way of doing something is better, say so. Distinguish clearly between currently available capabilities and announced or experimental ones.

Include links to the relevant official OpenAI announcement, documentation or release notes so I can investigate anything that interests me.

Why your normal account matters

Run it in the account you use every day, not a blank conversation. The model already has context.

In my case, ChatGPT knows that I use it for things including travel planning, photography, vehicle research, writing, website projects and fairly involved comparative research.

Consequently its answer wasn’t simply:

“Codex now has reusable cloud environments.”

It could instead reason:

You build small travel websites and interactive maps. Rather than repeatedly asking ChatGPT to generate revised HTML files, you could increasingly give Codex responsibility for maintaining the project.

That’s much more useful.

Likewise, an announcement about an always-on agent becomes much easier to understand when translated into:

Instead of repeatedly searching for Australian specifications and release information for a car you’re considering, have an agent take responsibility for watching for the information that will affect your decision.

The feature hasn’t changed. The context has changed its value.

The bigger change is how you work

For me the most interesting result wasn’t GPT-6.1. It was my mental model.

For years I’ve treated an AI assistant like a knowledgeable person on the other side of a messaging window. I ask, it answers. That still works, and often it’s exactly what you want.

But there are now more ways to work. Ask a question. Conduct research. Delegate a task. Automate the tasks you repeat. Then the genuinely different one: hand an agent responsibility for an objective over time. Dots are OpenAI’s clearest version of that yet.

That is a bigger shift than a few benchmark points between GPT-6 and GPT-6.1.

Don’t adopt everything

Technology companies release features. Enthusiasts then go looking for problems those features can solve. That’s backwards.

An agent is not automatically better than a conversation. An automation isn’t useful merely because something can be automated. Connecting another service isn’t worthwhile unless it removes friction.

That’s why the prompt ends by asking which capabilities you can safely ignore. It is the most useful line in it.

It took three weeks off grid to miss all of this. It took one prompt to find out which parts I actually missed. Avoid the information overload. Run it in your own account tonight.


Sources:

✍️ Reply by email