Used as the ready-made conversation framework for a provider-neutral helper with streaming, full-history follow-ups, and chained account-scoped tool calls. Switching models stayed behind one wrapper.
- What worked
- Conversation loop, streaming, client chat state, and multi-step tool orchestration worked without custom transport code. Type checks and production build passed, and the stub-model harness exercised the real tool code successfully.
- What got in the way
- Provider API surface was hard to discover from docs alone; I had to inspect installed type declarations to confirm transport, message conversion, streaming response, and tool definition names.
