Build a support assistant

The path

Chapter	What you add	How you know it works
1. Answer a question	Instructions and a model	The assistant asks for an order ID
2. Look up an order	A validated tool	ORD-1042 is reported as arriving Friday
3. Remember the conversation	A stable session ID	A follow-up can name the earlier order
4. Answer from policies	Retrieval with source IDs	The answer cites the return policy
5. Ask before a refund	A human approval callback	Denial leaves the simulated refund count at zero
6. Stream and inspect a run	Text streaming and tool events	Text arrives incrementally; tool use is visible
7. Serve an HTTP API	An explicit local router	A curl request returns an agent response
8. Prepare to ship	An application-specific deployment plan	Ownership, failure behavior, and evaluation have checks

Each chapter is a standalone program, rather than the next revision of one cumulative application. Save its code as support.ts and replace the previous checkpoint. Chapters isolate the new capability so you can inspect it; the retrieval and approval checkpoints do not silently carry over every earlier tool. Once the pieces work, compose the tools your application needs.

The examples use a fictional order and an in-memory refund record. They never connect to a payment provider. Model wording varies, so verify the underlying tool result and state as well as the text.

What is checked

The TypeScript examples are embedded from source files in this docs repository and checked against the sibling SDK’s built public declarations. This checks API usage, not a provider’s behavior or the quality of its answer. Run the verification prompts in your own environment before shipping.

Begin with one request

Create the support Agent, inspect its result, and close it.

Start here