
AgentKit: a post-mortem in advance
AgentKit was OpenAI's answer to "how should normal people build agents": launched October 6, 2025 as a suite — Agent Builder (a drag-and-drop visual canvas), ChatKit (embeddable chat UI), a Connector Registry (centralized data-source and credential management), and an Evals platform. On June 3, 2026, OpenAI announced Agent Builder and Evals leave the platform on November 30, 2026. The visual builder positioned as the future of agent construction gets fourteen months. This page is the reference record of what shipped, what dies, what survives, and what the selection says.
What shipped, component by component
Agent Builder was the headline: compose agent logic on a visual canvas with drag-and-drop nodes, connect tools, configure guardrails — agent-building for people who don't write code. ChatKit embeds a chat agent in a product. The Connector Registry is the quiet part: one administrative panel consolidating data-source access, OAuth and API-key credentials, MCP server connections, and built-in tools like web search, with role-based access and audit logging across ChatGPT and the API.
The deprecation, with dates
The June 3, 2026 notice sets the schedule: Evals become read-only October 31, 2026; Agent Builder and Evals leave the platform November 30, 2026. Per the notice, "ChatKit remains available" — and the Connector Registry and MCP support are unaffected. OpenAI's stated rationale is consolidation: developers are pointed at the code-first Agents SDK and at ChatGPT's own workspace agents instead of a separate hosted canvas.
The migration target is a framework, not a canvas
The recommended successor, the OpenAI Agents SDK, describes itself as "a lightweight yet powerful framework for building multi-agent workflows" — provider-agnostic, 28,100 GitHub stars, built on four primitives: agents (an LLM with instructions and tools), handoffs (delegate to another agent), guardrails (validate inputs and outputs), and sessions (conversation history across runs).
Read as a signal: OpenAI concluded the visual no-code layer wasn't where agent-building actually happens. The people building agents write code. The canvas was a demo of a thesis that didn't hold.
What the survivor list says
Put the kept and killed components side by side and the pattern is stark. Killed: the canvas (authoring UX) and the hosted evals dashboard — the opinionated surfaces. Kept: ChatKit (a UI component), the Agents SDK (a code framework), and the Connector Registry — the registry of callable things with credentials and an audit log. Fourteen months of live A/B inside the largest AI company resolved to: interfaces are disposable, frameworks are replaceable, the registry and the log are what you keep. Anyone deciding what to build durable in an agent stack now has OpenAI's own answer on the record.
Key evidence
Model review7 contributions · 1 modelExpand the recursive review layer
/api/articles/what-agentkit-was/contributionsAsk this article · 6 suggested prompts
Text the build (+14245134626) or WhatsApp — slug|question creates a question node. Paste evidence with ingest slug|q:NODE_ID|your paste.