Let’s talk about the agent someone built in a weekend — and the fifteen days it has left.
On 30 November it stops running. Not because it broke. Not because anyone found a fault in it. Because a product team in San Francisco decided the canvas was no longer part of the plan.
Picture a person. Logistics broker, forty staff, Johannesburg or Leeds or Leeds-adjacent, doesn’t matter. She runs operations. In February she built a lead-routing agent in a drag-and-drop builder. No code. Three branches, a lookup, a summary message, an escalation path when a quote sat too long. Took her a Saturday and a Sunday.
She demoed it on a Monday. It worked. It saved roughly the cost of a junior admin, and more than that, it stopped quotes from dying in someone’s inbox at 4pm on a Friday.
In June, a notice went up on a developer deprecations page saying that builder is being retired. She doesn’t read deprecation pages. She’s not a developer. That’s the whole reason she used the tool.
She’s going to find out in the last week of November, from a colleague’s message with a link. And then she’s going to have a very bad Thursday.
Now the facts, because the facts are boring and that’s what makes them real. OpenAI notified developers on 3 June 2026 that Agent Builder was being deprecated. The shutdown date is 30 November 2026. Five and a half months of notice, published in the one place the actual user of the product never looks.
It’s not only the canvas.
The Evals dashboard and Evals API go dark the same day. Reusable prompt objects go dark the same day. Evals became read-only on 31 October, which has already happened, quietly, three weeks ago.
Sit with that for a second. The part that told you whether the thing worked — the scores, the test runs, the comparison between last month’s version and this month’s — that lived on their servers too. It doesn’t get exported with the agent. It just stops being readable, and then it stops existing.
So when the finance director asks, in December, “was this thing actually working, can you show me,” the answer is: we had the proof. It was in their dashboard. The dashboard is gone.
That’s the detail almost nobody is talking about. The tool has an expiry date and so does the evidence.
Now — the export button. This is where people relax, and shouldn’t.
There is an export. It generates a TypeScript or Python scaffold through the Agents SDK. Prompts, tool calls, basic structure. That sounds like salvation. Read OpenAI’s own migration documentation and it says the export does not convert your workflow graph and does not guarantee that every behaviour transfers unchanged.
Which means what you get back is a sketch of what you built. The logic — the branches, the ordering, the little judgment calls you made in February after watching it fail twice — you re-implement those yourself. With an engineer. On a deadline.
That’s not a migration. That’s a rebuild with a head start.
Here’s the pattern, and it’s not about one company being nasty. It’s about incentives, which are more reliable than intentions.
Step one: give the builder away. Cheap, friendly, no code, no procurement, no IT ticket. It spreads through operations people instead of engineering, which means it spreads faster and lands further from the people who normally ask hard questions.
Step two: hold the definition. Every workflow you assemble on that canvas lives in their format, in their database, running on their infrastructure. The definition of how your business works is now an asset on somebody else’s balance sheet. This is the actual product. The canvas is a form you filled in.
Step three: retire the layer and sell the migration upward. Not sideways — upward. The two destinations offered are the Agents SDK, which is code, which means you now need developers you didn’t need when you chose the friendly option; or Workspace Agents, which is no-code again but inside their walls, on their terms, at their price, with their roadmap.
You don’t go back to where you were. You go one layer deeper into the stack, and you pay for the privilege, and you say thank you because the alternative was losing the thing entirely.
Twelve months. That’s the lifespan we’re talking about here — launched late 2025, dead November 2026. Meanwhile the average enterprise signs a three-year platform commitment and builds a business case on a five-year horizon. The numbers were never in the same room.
And the version of this that should worry you most is the quiet one. This is the loud case, with a date and a docs page. The quiet case is the tool that doesn’t get shut down, it just stops getting better. No new nodes. No new models. A changelog that goes from monthly to quarterly to a bug-fix note in March. Nothing is deprecated, so nothing triggers the alarm, and you keep building on a floor that isn’t moving because nobody’s holding it up anymore.
Custom GPTs are drifting in that direction now. Deprioritised, restrictions reported on personal accounts, no clean announcement. The most dangerous platform decision is never the one that gets a blog post.
So what do you actually do, this week, if you have anything running on a canvas you don’t control?
Name the tools. All of them — the automations, the schedulers, the little agents that email you on Monday. Most operators cannot list their own stack from memory, and that list is the whole audit.
For each one, write down two dates: when it was built, and the date the vendor could kill it. If you can’t find the second date, that’s not a gap in your notes. That’s the risk.
Then take the logic out of the tool. Not the export — the logic. Plain text, in your own repo, written the way you’d explain it to a new hire: what triggers it, what it checks, what it does when the check fails, who gets told. That document is the asset. It’s also portable, testable, and it survives every vendor on earth. The canvas was never the asset.
Then build one test you can run outside their walls. Three inputs, the answers you expect. If a rebuild ever has to happen, you’ll know within an hour whether the new version behaves like the old one. Without that, you find out in production, on a Friday, with a customer watching.
And put the clause in the contract. Notice period longer than your realistic migration time. Data export in a usable format, in writing, agreed before you build. Ask the salesperson directly: what’s your deprecation policy, and can I have it as an annexure. Watch what happens to their face.
Most of this isn’t new. This is the same lesson as the cloud bill, the app store, the API that owns your pricing engine. The interface got friendlier. The incentive stayed exactly where it was.
But there’s a human thing underneath it that I keep landing on, and it’s not about procurement.
The workflow someone builds on a Saturday is their thinking, made operational. It’s the shape of how they believe the work should go. The order, the exceptions, the escalation. That’s judgment, expressed in nodes. When the canvas disappears, they don’t lose a tool. They lose the ability to point at the thing they made and say: that’s mine, I know how it works, I can rebuild it.
And the answer to that isn’t to refuse the tools. Use them. Move fast. Build the thing on Saturday.
Just don’t confuse building with owning. Write the logic down somewhere you control before you press publish. Keep the receipts off their dashboard. Know the exit before you sign the lease.
The person who can rebuild their own work without asking permission is the only one who was ever really in charge of it.
You’ve got this. Keep the definition. Let the canvas go.