01
Start from a real runtime surface
Move beyond one-shot demos with prompts, streaming sessions, tool execution, and file-backed persistence in the same TypeScript runtime.
Run the quickstartOpen Agent SDK
Open-source alternative to Claude Agent SDK. Use it when you want a lightweight runtime with sessions, tools, hooks, subagents, and multi-provider support in a codebase you can inspect and extend.
Claude-style mental model, open implementation, broader provider choice.
npx open-agent-sdk@alpha init my-agentWorkflow
Product teams usually outgrow isolated demos in the same places: session state, tool control, provider churn, and operational safety. This SDK is organized around those failure points from the start.
01
Move beyond one-shot demos with prompts, streaming sessions, tool execution, and file-backed persistence in the same TypeScript runtime.
Run the quickstart02
Permission modes, tool gating, and lifecycle hooks let product teams inspect, approve, and instrument agent behavior before it turns into operations debt.
Review safety controls03
Keep the same mental model while changing providers, extending with MCP servers, or benchmarking real workflows instead of rebuilding your loop.
Browse the API surfaceCapabilities
Keep the repo approachable for local experiments, then extend the same primitives into production workflows, migration projects, and benchmark runs.
Create, resume, and fork long-lived agent runs with storage-backed history so product work is not trapped in a single request cycle.
Session APIUse `default`, `plan`, `acceptEdits`, and `bypassPermissions`, then layer custom tool checks and lifecycle hooks when your surface area grows.
Permissions and hooksShip with bash, file operations, web search and fetch, MCP integration, and subagent task delegation instead of stitching one-off helpers together.
Tool modelReuse local Codex OAuth when it fits, or target OpenAI, Gemini, and Anthropic with explicit provider configuration and migration paths.
Provider and authAdoption paths
The repository now has three jobs: explain the product quickly, move builders into working code, and give evaluators enough surface area to trust the runtime.
Use the SDK and CLI-first workflow when you want one open runtime to own prompts, sessions, tools, and safety policy.
Keep the familiar session and tool-first mental model, then widen the runtime around providers, hooks, and evaluation without a rewrite.
Build with it
Start with docs and API reference, or jump straight into the package if you already know the workflow you want to ship.