Migrating to AgentsKit

AgentsKit isn't in conflict with the libraries you're already using — but if you're hitting their limits, these guides walk you through the move.

#Choose your migration path

• Coming from a chat-first stack: start with Build your first agent, then migrate the UI and provider seam first.
• Coming from a large abstraction stack: read Architecture at a glance, then replace one layer at a time.
• Coming from an agent-first framework: compare use cases and runtime responsibilities before changing code shape.

#Before you migrate

Read the "When you should NOT use AgentsKit" section of the README. If your use case falls in there, stay where you are — that's the honest answer.

#What stays the same

Regardless of what you're coming from:

• Your prompts — system prompts, few-shot examples, tool descriptions transfer as-is
• Your tool implementations — the functions that do the work (fetch, read file, call API) don't change
• Your provider accounts — same API keys, same billing

#What changes

• The shape of the client library — imports, hooks, class instances, method names
• How tools are declared — AgentsKit uses a ToolDefinition object with schema (JSON Schema 7)
• How the agent loop runs — AgentsKit's createRuntime owns maxSteps, delegation, memory, retrieval

#Philosophy

Migration guides here are honest: we show the before/after, call out what AgentsKit does better, and call out what the other framework does better. If we can't beat the other option on a given axis, we say so.

#Good first landing points

• Build your first agent
• Architecture at a glance
• Use cases