Deprecation notice: Agent Builder
@che.kulhan To answer your direct question: ChatKit itself survives, but the “Recommended integration” you quoted is effectively dead, that path depends on OpenAI hosting the backend from Agent Builder , and Agent Builder shuts down Nov 30. What remains is the “Advanced integration”: ChatKit frontend + your own backend via the ChatKit Python SDK and the Agents SDK.
For a multi-client setup, the economics aren’t as bad as they first look: the backend is the same code for every client, with per-client config (instructions, tools, knowledge) stored as data. You build the loop once, not N times. The real one-way door is timing, exports of existing workflows are only possible while the dashboard is still up.
One trap to avoid while migrating: don’t move workflow prompts into dashboard Prompt Objects, those are also being shut down Nov 30 (see the parallel deprecation notice). Keep config in your own code/DB or you’ll migrate twice.
Discussion in the ATmosphere