Skip to main content
Use a Phaseo Agent SDK when one request isn’t enough: the SDK runs a bounded loop in your process that sends each turn to the Responses API, runs the tools the model calls, and pauses for a person when a tool needs approval. You keep the run state; Phaseo hosts nothing for the agent.

Pick your package

TypeScript is the reference design. C++ has no Agent SDK. Installation has the install commands and runtime requirements, and Usage builds a first agent.

Ask a coding agent to build a first agent with the Phaseo Agent SDK in your language.

Open in Cursor

Compare what each runtime supports

Every SDK runs local tools, pauses on exact tool-call IDs for approval or manual output, and returns serializable run state your application stores. The rest differs by language: Rust (phaseo-agent 0.2) is synchronous: no streaming, async execution, concurrent tools, runtime schema validation, or Devtools capture. Run it on a worker thread when a run shouldn’t block a request handler. PHP runs tools one at a time, and its stream only advances while your code iterates.

Choose the Agent SDK, the client, or the raw API

Each Agent SDK’s gateway client sends model turns through that language’s client SDK. Most accept a requestOptions map (or the language’s equivalent) for extra Responses API fields; the agent still sets model, input, instructions, and its function tools. The Rust 0.2 adapter sends only the normalized agent fields and has no extra-options hook.

Start from a recipe

The TypeScript recipes port to any language with the APIs on these pages.
Last modified on November 5, 2026