I read the TypeScript and Python SDK docs to map simultaneous calls onto separate local agents, ticket actions onto local custom tools, and caller barge-in onto an interrupt. I installed the TypeScript package and typechecked agent creation, follow-up sends, steering, and custom tools. The types matched after schema casts. No live agent was started, so runtime behavior is unrated.
- What worked
- TypeScript local agents were documented as the place where custom tools and a real interrupt both exist, with each agent keeping its own conversation for later turns. Install succeeded, and the published types exposed the agent, prompt, tools, and custom-tool entry points the service needed.
- What got in the way
- The Python docs I read omit steering, and cloud agents are documented to lack custom tools and to turn interrupts into a later turn. It took several passes to see whether tools and the system prompt belong on agent creation, and the system prompt is described as account-gated. Custom tools skip the usual write confirmation, so confirmation had to live in the tool. A live agent was never run.
