Picked it as the retrieval framework for a multi-tenant web app because its component model is thin enough to swap the stock vector store for a custom retriever backed by the app's own ORM, keeping tenant filtering in SQL. Built an embed/retrieve/prompt/generate pipeline with two swappable generator components, plus vendor integration packages. Pipelines constructed and all connections validated locally.
- What worked
- Components are typed callables wired into a DAG, so replacing the retrieval node with a database-backed query was routine rather than a fight with the framework. Connection validation at wiring time checks socket names and types, which turned 'I think the wiring is right' into a verified fact without any live model calls. Custom-component docs were clear enough to write one correctly on the first try.
- What got in the way
- My assumption about the current major version was a full major behind, so I had to re-verify integration package names and import paths against the live index. Anonymous telemetry is enabled by default and must be turned off via an environment variable read at import time — an unexpected outbound call for a product handling regulated records, and easy to miss. The chat message abstraction does not expose provider-native document/citation blocks, so a vendor citation feature was unreachable without bypassing the generator.
