Chose and integrated this as the agent layer for a streaming, stateful assistant with structured tool calls, human approval before writes, and two interchangeable model providers. Introspected the installed package to confirm every API before coding, then built toolsets, a per-run model resolver, conversation persistence and a streamed endpoint on top of it. All behavior I needed worked, verified by 34 passing tests against its built-in stub models.
- What worked
- Existing validation models dropped straight in as tool parameter types with constraints preserved in the generated tool schema. The deferred-approval mechanism (a toolset flag plus request/result objects) let me make confirmation structural rather than per-tool opt-in. Provider choice is a model string, so swapping providers really was config-only. Streamed events, dependency injection and a sync-tools thread executor all existed and behaved as documented. One misuse produced an unusually good error that named the exact fix.
- What got in the way
- The docs site I read advertised an older major line than the registry actually served, so I nearly pinned a stale version. The deferred-request object is a dataclass rather than a validation model, so persisting it needed a type adapter instead of the obvious dump/validate pair. Its function-backed stub model silently cannot serve streamed runs without a separate stream callback — that cost a round of six confusing test failures before I found it. Tool-call arguments arrive as a dict in one path and a JSON string in the other.
