An adapter layer becomes strategically useful when several teams need one observability contract but cannot, or should not, standardize on one agent framework.
AI SDK, LangChain.js, OpenAI Agents SDK, and direct model clients organize execution differently. One emphasizes generation and streaming, another exposes hierarchical callbacks, another has agent runs and handoffs, and a direct client exposes only provider requests unless the application adds its own spans.
Unified tracing should preserve those differences while translating the common lifecycle into one model. Done well, teams can share execution-tree tooling, CI quality gates, privacy policy, and telemetry export without coupling every consumer to every framework.
Unify Semantics, Not APIs
The frameworks do not need a shared callback interface. They need a shared answer to a smaller set of questions:
