SDK and app-building tooling
Developer-facing primitives for teams building AI features rather than only using AI coding assistants. This lane separates app-surface concerns such as streaming and tool calls from deeper agent control concerns such as state and branching. Useful for deciding when simple product plumbing is enough and when an agent framework is justified.
lane decision read
operator question
Is the team building AI product surfaces, agent systems, or both?
decision rule
Use this lane when the decision is between app primitives and heavier agent-control architecture.
avoid when
Avoid this lane when the problem is repository assistance, review automation, or protocol integration rather than product UI delivery.
compare by
Compare by abstraction level, UI delivery speed, provider flexibility, and control-plane needs.
tradeoff
SDKs speed product delivery, but they do not replace deliberate decisions about state, tools, safety, and workflow ownership.
ordered operator lane
Curated tools with metrics artifact signals
frontend-only composition
Vercel AI SDK
VAISDKvercel/ai
signal
The AI SDK is most useful when the problem is shipping an AI product surface rather than researching agent control. It standardizes streaming, provider adapters, tool calls, and UI state so teams can move faster at the app layer. It does not replace decisions about memory, orchestration, permissions, or evaluation; compare it against agent frameworks when behavior needs durable control paths.
workflow fit
Best for TypeScript product teams shipping AI interfaces, streaming UX, tools, and structured output.
watch out
It supplies app primitives, not a complete agent operating model; architecture choices still belong to the product team.
LangGraph
LGFAgent Frameworklangchain-ai/langgraph
signal
LangGraph matters when an assistant flow has become product architecture. The operator value is explicit control: states, branches, interrupts, retries, and human review points can be named and tested. The tradeoff is surface area. Reach for it when failures must be governed; avoid it when a direct SDK call or small workflow script would be easier to operate.
workflow fit
Best for product teams building stateful agent flows with explicit steps, branching, retries, and supervision.
watch out
Overkill for simple assistant features where a small SDK call or direct workflow script would be easier to operate.