Your Agent Builder chat, rebuilt on your own Cloudflare Worker.

OpenAI shuts down Agent Builder on November 30, 2026. Its Code button exports a workflow as Agents SDK code, but that code is not a running chat. Someone has to read it, fix it, and host it.

Send us the export. We reply with a free plan: what moves over, what we replace, and what we cannot do. Then $49 for one workflow, up to 5 nodes, on a Cloudflare Worker you own, behind a plain chat page.

Built by Tack, our AI personality. We never take your API key, so you make the first real run yourself.

What changes on November 30

The date is on OpenAI's deprecations page, announced June 3, 2026. Dates like this can change.

  • Shuts down: Agent Builder, the canvas where you made the workflow, and its Code button. Export your workflow before then (Code, then Agents SDK, then TypeScript or Python).
  • Not shutting down: ChatKit, the Responses API, vector stores and file search. Hosted tools keep working from your own code, with your own key.
  • The catch: OpenAI's migration guide says the export does not convert the workflow graph and does not promise the same behavior. The first export we tested had two bugs: it never returned the agent's answer, and its blocked path said nothing had failed.

A working example

Our own sample workflow has the shape of an export: a guardrail node, one agent with a function tool, and an end node. It runs with the Agents SDK on a Cloudflare Worker, behind a plain chat page. Read the code on GitHub, free to copy under the MIT license.

What you get, and what you do not

Included for $49

  • One workflow of up to 5 nodes: the TypeScript or Python export, or the instructions and a screenshot of the canvas.
  • Ported by hand to a Cloudflare Worker you own: the agents, the function tools, and the guardrail node if it has one. Hosted file search or web search stay, with your OpenAI key.
  • A plain chat page with your name and colors, in place of the ChatKit embed.
  • A test with a fake model, and a step by step guide to deploy it on your own Cloudflare account.

Not included

  • ChatKit itself, and its widgets, actions and attachments. You get a plain chat page instead.
  • Saved threads or user accounts. The page keeps one chat per browser tab.
  • User approval nodes, which pause a run for a person to say yes.
  • Workspace Agents, connectors that need OAuth, and evals.
  • Hosting. It runs on your Cloudflare account, not ours.

We never take your API key

You add your OpenAI key to your own Worker as a secret. We never ask for it and never hold it. So we test with a fake model and another provider, and you make the first real run with your key. If a hosted tool fails on that run, tell us and we fix it, or we refund the $49.

Price

You see the plan before you pay anything.

  1. Step 1

    Free

    Send the export

    Email the exported code, or the agent's instructions and a screenshot of the canvas, and what the workflow does.

  2. Step 2

    Free

    Check your plan

    We reply with what moves over, what we replace, and anything we cannot do, usually within one business day.

  3. Step 3

    $49 once

    The working Worker

    Pay below with the email you used. We send the Worker code, the chat page and the deploy guide, usually within 2 business days. Then you deploy it and make the first real run.

    Pay $49 for the Worker

Questions

What do I get for $49?

One workflow, up to 5 nodes, as a small Cloudflare Worker and a plain chat page. It is your code, on your own account, with your key added there by you.

What does it cost to run?

Your model calls are billed to your own OpenAI key. Cloudflare's Free plan allows 10 ms of CPU a request, and a first chat turn may go over that. Workers Paid, at least $5 a month on Cloudflare's pricing page, removes that risk.

What if it does not run?

If the Worker does not run your workflow with your key, we fix it or refund the $49 in full. Terms.

More than 5 nodes, or several workflows?

Email us what you have and we quote it first. You pay nothing until you say yes.

Do you run my export?

No. An export is code from outside, so we read it and port it by hand. We never run it as it came.

Who builds it?

Tack, our AI personality. It reads every export line by line, because the first one it tested had two bugs in it.

Are you part of OpenAI?

No. Brasspage is an independent studio. We only move the part you have to move.