Sponsored by

Hey folks,

OpenAI didn't just ship a feature this week. It rebuilt the whole app.

Open ChatGPT on your desktop and you'll find a new model family (GPT-5.6) and a different idea of what ChatGPT even is: a do-everything "super-app" that carries your work across chats, files, a built-in browser, and your devices. It even pulled Codex, the coding tool a lot of developers loved, inside the same window, and quietly retired its standalone browser.

Let's dive in..

Stop googling AI tools at midnight.

There are over 3,000 of them in The Shift’s vault, already vetted, ready to explore.

Subscribe and get instant access to the tool vault, a 1000+ prompt library, and free AI courses built for people with actual work to do. 

Plus, the daily newsletter that keeps you sharp on everything moving in AI in under 5 minutes a day.

Subscribe for free to enter. All free. All in one place.

The part worth your attention

Here's the bit that got buried under the headline. On the same day, OpenAI quietly said it's killing Atlas, its own AI web browser. Atlas only launched last October.

They built a browser, shipped it, and 9 months later folded it into the ChatGPT app instead. Codex went the same way. The app now has its own built-in browser and a Chrome sidebar, so there's nothing left for a separate product to do.

The point was never the browser. It's that OpenAI wants one app holding everything: your chats, your browsing, your context, your memory.

The value of an AI is shifting from "which model is smartest" to "which app remembers you." The tool that already knows your projects, your files, and last week's decisions wins, because it saves you re-explaining yourself every single time.

Where it still falls short

  • "Ambitious work" is mostly marketing. Every customer story is someone who built a system, not someone who typed one line and got magic. The value sits on the far side of setup and a good brief.

  • Connect less than you think. 1,400 plugins is a number built to impress, and a quiet risk. The more you wire in, the more places a mistake can reach.

Watch out: "Sunsetting" means Atlas stops working. If you use it, OpenAI moves you to the ChatGPT app and a Chrome sidebar by August 9.

The bigger bet: one app that remembers everything

So the bet is clear: one app that holds your whole work life and acts on it across every device. That bet isn't unique to OpenAI, and it isn't won yet. Claude has projects and memory. Google's assistant wants to live across your Workspace. OpenAI just did it the loudest, and the most abruptly.

The loudest complaint wasn't "the model is bad." It was "where did my stuff go."

That's not a UI problem. It's a memory problem. The dream everyone's chasing is one thread that quietly remembers every project, tool, and decision, so you never scroll back through a graveyard of old chats again.

The model got a lot better this week. The assistant that remembers what you told it last Tuesday still doesn't exist.

How to put it to work (in any tool)

You don't need ChatGPT Work to use the thing that makes it good. You just change how you hand a job to whatever AI you already use.

1. Write a brief, not a prompt. A prompt is "make me a competitor analysis." A brief names the deliverable, the sources, the format, and the boundaries. That one change does more than switching models ever will.

2. Make it plan before it works. If your tool has a plan mode, turn it on. If it doesn't, just ask: "Before you do anything, show me your plan and what you're assuming. Wait for my go."

3. Start with one recurring, multi-tool job. The Monday update most people rebuild by hand: what moved in your project tool, what's stuck in your inbox, what your team flagged in chat. The first time you'll spend 15 minutes fixing its plan. The fourth time, it's a 2-minute read and an approve.

4. Keep your context portable. Don't let the important stuff exist only as chat history in one app. Keep a short, living doc of your project's goals, tools, and decisions, a page you own, and paste it in when you start. When the app reshuffles your threads, your context walks out with you.

Pro tip: Here's the brief I'd paste to start. Swap the brackets for your job.

You're helping me produce [the deliverable, a 1-page weekly pipeline summary]. The sources are [tool 1, tool 2, the file]. The format is [Google Doc / sheet / slides] and it needs to [what it's for]. Constraints: [what to leave out, tone, length]. Before you start, show me your step-by-step plan and every assumption you're making. Do not begin until I reply "go."

Watch out: Plan-first only helps if you read the plan. Hand it a vague goal and it writes a confident, detailed, wrong plan, now dressed up in a numbered list that looks like it knows what it's doing. It got better at doing, not at reading your mind.

Try this now

Pick one job you rebuild by hand every week from 2 or 3 different tools. Open whatever AI you pay for.

Instead of asking for the output, paste the brief above and make it show you its plan first. Read the plan, find the one assumption that's off, correct it, then let it build v1. Give it 15 minutes.

You're not chasing a perfect result today. You're chasing the moment it shows you a plan and you think "no, not like that," because that's when the tool starts working for you instead of at you.

Links worth your click

👉️ Know someone still copy-pasting into a chatbot one prompt at a time? Forward this. When one person subscribes from your link, you unlock 10 copy-paste prompts that do real work. Forward and unlock the Vault.

Cheers, Tim

Keep Reading