The best OpenAI ChatKit alternatives in 2026
What to use instead of OpenAI ChatKit now that Agent Builder is shutting down, with licences and prices from each product's own site.
Quick answer
OpenAI's Agent Builder shuts down on 30 November 2026, and ChatKit stays available. If you like ChatKit, the smallest change is to keep it and run it against your own server with OpenAI's Python SDK. If you want to leave it, CopilotKit (MIT, with a hosted tier) and assistant-ui (MIT, with an optional cloud) are the closest chat frontends, and the Vercel AI SDK (Apache-2.0) is the most flexible toolkit. If the chat was an assistant inside your product, Verb gives you that agent without building it.
A bias first: I build Verb, one of the options below. I have tried to say plainly what each of the others is good at and who should pick it over Verb.
OpenAI's docs say Agent Builder is scheduled to shut down on 30 November 2026, and that ChatKit remains available. If you put a ChatKit chat on your site with a workflow hosted in Agent Builder, the chat itself can stay. What has to move is the agent behind it. That makes this a good moment to ask whether ChatKit is still the right frontend, or whether something else fits better.
Every claim below about another product comes from its own site, read on 20 November 2026. The pages are listed at the end.
If you only need the steps to get off Agent Builder, the Agent Builder migration guide covers them one by one.
0. Keep ChatKit, run your own server
What it is. OpenAI calls ChatKit "the best way to build agentic chat experiences". It handles the chat interface, file attachments, tool calls and widgets. Its guide now describes two paths: the Agent Builder-hosted one, which existing users can keep during the transition, and a custom server that you run yourself, which OpenAI recommends for new work.
What it takes. The custom path uses OpenAI's openai-chatkit Python package: a ChatKitServer you extend, a store that keeps threads, messages and files in your own database, and helpers that connect it to the Agents SDK. Both chatkit-js and chatkit-python are Apache-2.0.
Who it suits. Teams happy with ChatKit's interface who are building on OpenAI and can run a Python service. It is the smallest change.
1. CopilotKit
What it is. In its own words, "the open-source stack for putting AI agents in front of real users". You bring an agent built on any framework and it adds chat, generative UI, shared state and human-in-the-loop, in React, Angular, Vue, React Native, Slack and Microsoft Teams. It connects to agents over AG-UI, an open protocol it maintains.
What it costs. The code is MIT-licensed. Its paid platform has a free Developer Edition for non-production use, a hosted free tier of 1,000 interactions a month per organization, Pay as you go at $49 a month for the first 10,000 interactions, and custom annual plans.
Who it suits. Teams with an agent already built, on OpenAI or not, who want more than a chat box: the agent reading and changing what is on screen, and approvals in the interface.
2. assistant-ui
What it is. "An open-source TypeScript/React library to build production-grade AI chat experiences fast." It renders tool calls as your own React components, collects inline human approvals, and works with many backends, including the Vercel AI SDK, LangGraph, the AG-UI and A2A protocols and your own data stream.
What it costs. The library is MIT and free. Its optional Assistant Cloud, for thread history, telemetry and file storage, is free up to 200 monthly active users, then Pro at $50 a month for 500 plus $0.10 for each one after, and custom Enterprise.
Who it suits. Teams who want the closest thing to ChatKit's polished chat, but in their own React code and not tied to one model provider.
3. Vercel AI SDK
What it is. "The TypeScript toolkit for building AI applications and agents." It covers model calls across providers, tools and structured output, and UI hooks such as useChat for React, Svelte and Vue.
What it costs. Free, Apache-2.0. You pay your model provider. One thing to know: Vercel's AI Elements component library says it will be deprecated at the end of November 2026 as it moves to shadcn/ui, so plan your chat components with that in mind.
Who it suits. TypeScript teams who want full control and will build the interface themselves.
4. Verb
What it is. An AI agent that sits inside your product and does the work your users ask for, as the signed-in user, through the API your product already has. You describe what it may do, try it on a test copy of your app, and add one script tag. It is integrated in under an hour in most cases.
What it costs. It starts with a free 30-day pilot. I set it up with you, we measure the requests it handles and the time it saves, and agree a price from those numbers.
Who it suits. Teams whose ChatKit chat was meant to be an assistant inside their product, and who would rather have that agent working than rebuild one. It does not suit a team whose agent is the product itself and who wants to own every line; one of the toolkits above is the better fit there.
The verdict
- Happy with ChatKit, building on OpenAI: keep it and run your own server.
- Agent already built, want it to act on screen: CopilotKit.
- Want polished chat components on any backend: assistant-ui.
- Want the lowest-level toolkit: the Vercel AI SDK.
- Want an agent inside your product without building it: Verb.
For a closer look at three of these side by side, see CopilotKit vs assistant-ui vs the Vercel AI SDK.
Sources
Each read on 20 November 2026.
Frequently asked questions
Is OpenAI ChatKit being shut down?
No. As of 20 November 2026 OpenAI's docs say Agent Builder is scheduled to shut down on 30 November 2026 and that ChatKit remains available. What changes is where the agent behind it runs: OpenAI points new work at a custom server built with its ChatKit Python SDK.
What does OpenAI recommend instead of Agent Builder?
Its deprecations page lists the Agents SDK or ChatGPT Workspace Agents. Agent Builder can export a workflow as Agents SDK code in TypeScript or Python, though OpenAI notes that this does not convert the workflow graph or guarantee every behaviour transfers unchanged.
What is the best open-source alternative to ChatKit?
For a chat frontend, CopilotKit and assistant-ui, both MIT-licensed React libraries. For the lowest-level toolkit, the Vercel AI SDK, which is Apache-2.0 and gives you hooks such as useChat. ChatKit's own JavaScript and Python packages are Apache-2.0 too, so staying on ChatKit with your own server is also an open-source option.
Is there a ChatKit alternative where I don't build the agent?
Yes. The toolkits here expect your team to write and run the agent. Verb is the agent: you describe what it may do in your product, it does that work as the signed-in user through your existing API, and it is integrated in under an hour in most cases.

Vishnu, founder of AskVerb @itsvishnups
Building the AI agent that lives inside a SaaS product and does the work its users ask for. Writing down what I learn along the way, including the parts I got wrong first.