What teams building AI features on AI SDK report, with every finding tied to its evidence.
Read the findingsPractitioner sentiment, all practitioners
+36 Positive from 85 sources that take a side
How this figure is madeFrom 83 authors in 79 discussions. Build one pilot agent to measure the glue code and debugging time the framework adds.
Feb 2025 to Oct 2026.
94 sources from practitioners, by month and sentiment.
Across 94 sources the read is positive: 35 positive, 5 negative, 45 mixed, and 8 listed without counting. One API across providers draws the most consistent praise, positive in 16 of 17 sources. Provider translation bugs are raised in 14 and breaking changes in 9.
Positive, mixed and negative sources
The score counts them as 35 positive, 43 mixed and 5 negative votes, one per author. See How the numbers work.
See the evidenceBelow: 4 praise themes, 5 concerns, 3 close to agreement and 1 disagreement.
Counted for All practitioners, from 94 sources. Change group
Every capability practitioners describe positively, ranked by how many sources say so. Open one to read who said it.
Counted for All practitioners.
Positive, 16
Positive
Adam Rackis, Developer writing about their own app
Having Fun with Vercel's AI SDK and AI GatewayPersonal blog post, Master.dev Blog
Calls the AI SDK a slick API with useful output validation; through AI Gateway each generation cost US$0.03 to US$0.05, and the response carries its cost.
Positive
ojr, Hacker News commenter
Comment on: Gemini 3.1 ProHacker News comment
Uses the AI SDK so the product can switch models, running on Gemini without OpenAI or Claude credits.
Positive
cg_stewart, Reddit user
Comment on: For your AI app, you use VercelAI SDK or direct API?Reddit comment, r/nextjs
Called the Gemini API directly at first, then refactored onto the AI SDK, and notes the monthly US$5 of gateway credit before billing starts.
Positive
Luca Becker, aicommits maintainer
aicommits v1.0.0: Six Months of AI-Assisted Development Come Full CirclePersonal blog post, luca-becker.me
Moving aicommits to AI SDK v5 replaced every custom provider integration, so adding AWS Bedrock became a short task, though Ollama support dropped until a community provider appeared.
"While migrating to Vercel AI SDK v5, Ollama support was temporarily dropped."
Positive
Matt Pocock, TypeScript educator
AI SDK v5: A Crash Course | Matt Pocock at React Universe Conf 2025Conference talk, YouTube (Callstack)
Presents the AI SDK as the one library for AI apps in TypeScript: one API across providers, one-line model swaps and type-safe Zod tool calls.
"…trying it out perspective. It means there's just one thing to learn, right? Which is really attractive when you're just getting into the space for the first time. You don't need to learn the weirdnesses with every single LLM provider and what…"
Positive
matt_cogito, Hacker News commenter
Comment on: Best Practices for Building Agentic AI SystemsHacker News comment
Recommends the AI SDK as the right level of abstraction for building agents: more would hide how agents work, less ties you to one provider's API.
Positive
yujonglee, Hacker News commenter on the Hyprnote team
Comment on: Launch HN: Hyprnote (YC S25) - An open-source AI meeting notetakerHacker News comment
Hyprnote runs an OpenAI-compatible local server in a Tauri plugin and calls it from the TypeScript frontend through the AI SDK.
Positive
gorbypark, Hacker News commenter
Comment on: ChatGPT agent: bridging research and actionHacker News comment
Ran the OpenAI Agents SDK on Claude through the AI SDK's Anthropic provider, which made non-OpenAI models a one-call change.
Positive
Zachary Proser, Applied AI at WorkOS
The Vercel AI SDK: A worthwhile investment in bleeding edge GenAIPersonal blog post, zackproser.com
Says the SDK takes time to learn but is worth it: switching from Claude to Gemini takes a few characters in a pull request without touching the prompt.
Positive
bearjaws, Hacker News commenter
Comment on: Use the Gemini API with OpenAI Fallback in TypeScriptHacker News comment
Has loved using the AI SDK to swap their apps between models, including local ones, and says it handles file attachments well.
Mixed
Dapper-Turn-3021, Reddit user
Is Vercel AI SDK actually good for building real AI agents?Reddit post, r/vercel
Finds the chat UI, streaming, and model switching clean, but building an agent means wiring orchestration, memory, tool routing, and feedback by hand.
Positive
MaxGfeller, Hacker News commenter, OpenHarness author
Comment on: OpenHarness - Composable TypeScript SDK for building powerful agent harnessesHacker News comment
Built OpenHarness on AI SDK 5 after finding the Claude Agent SDK, Codex and OpenCode too heavy to embed, so it works with any SDK-supported model.
Positive
bri-_-guy, Reddit user
Claude Agent SDK vs OpenAI Agent SDK vs Vercel AI SDKReddit post, r/vercel
Moved a five-agent hobby project from the Claude Agent SDK to the AI SDK for more model options, and later decided to stay on it.
Mixed
elpakal, Hacker News commenter
Comment on: Launch HN: Onyx (YC W24) - Open-source chat UIHacker News comment
Values easy setup, streaming, model agnosticism, chat persistence and blob support on Vercel's AI chatbot stack, but dislikes the vendor lock-in.
Positive
Richard Gill, Engineer at Xata
Writing an LLM Eval with Vercel's AI SDK and VitestEngineering blog post, Xata blog
Xata runs its agent's tool calls across models through the AI SDK and builds evals in Vitest from the SDK's response objects, which hold almost everything needed.
"To make sure that Xata Agent still works well after modifying a prompt or switching LLM models we decided to test it with an Eval. Here, we'll explain how we used Vercel's AI SDK and Vitest to build an Eval in TypeScript."
Positive
SparkyMcUnicorn, Hacker News commenter
Comment on: Show HN: Mastra - Open-source JS agent framework, by the developers of GatsbyHacker News comment
Uses the AI SDK without ever touching Vercel's servers and sees no lock-in: it is a unified interface over providers.
Mixed or negative, 1
Mixed
consumer451, Hacker News commenter
Comment on: Microsoft to Use AI from Anthropic in Partial Shift from OpenAIHacker News comment
Uses the AI SDK to stay provider-agnostic but finds each prompt still needs per-model tuning, so switching models means redoing prompts.
GILD's fact checks, which don't count as sources
Checked Oct 12, 2026.ai-sdk.dev lists 46 first-party provider integrations, AI Gateway among them, and 58 community providers; AI Gateway is the default global provider for plain model strings. AI SDK providers
Open them in the recordCounted for All practitioners.
Positive, 10
Mixed
Dapper-Turn-3021, Reddit user
Is Vercel AI SDK actually good for building real AI agents?Reddit post, r/vercel
Finds the chat UI, streaming, and model switching clean, but building an agent means wiring orchestration, memory, tool routing, and feedback by hand.
Positive
Pedro Teixeira, Helpmaton
Real-Time AI Streaming in Production: What We Built at HelpmatonEngineering blog post, metaduck.com
Helpmaton runs its production AI streaming on Lambda with the AI SDK's streamText on the server and useChat on the client. It lets the SDK carry tool calls and results over the stream.
"TL;DR: We kept the same foundation (Lambda Function URLs, AI SDK, Architect) and added production-ready patterns: multi-path streaming with secret-in-path auth, a credit system for cost protection, and subscription-based throttling for our REST API."
Positive
seafoodghost, Reddit user
Comment on: For your AI app, you use VercelAI SDK or direct API?Reddit comment, r/nextjs
Started on direct provider API calls, switched to the AI SDK and likes it: less boilerplate, streaming handled for them, and AI Elements for the interface.
Mixed
elpakal, Hacker News commenter
Comment on: Launch HN: Onyx (YC W24) - Open-source chat UIHacker News comment
Values easy setup, streaming, model agnosticism, chat persistence and blob support on Vercel's AI chatbot stack, but dislikes the vendor lock-in.
Positive
Felipe Cadavid, Software engineer at BrainGrid
Migrating to AI SDK v5: A Story of Tool Streaming, Caching, and Type SafetyEngineering blog post, BrainGrid blog
Migrating 14 tools to AI SDK 5 took renames and a type overhaul, then cut frozen-UI tickets to zero, sped tool execution 17% and trimmed tool-definition cost 7%.
"We migrated BrainGrid's core AI infrastructure from AI SDK v4 to v5. Here's how it went."
Positive
pgte, Hacker News commenter, author of the post
Comment on: Building Real-Time AI Streaming Services with AWS Lambda and ArchitectHacker News comment
Built a streaming AI service with tool execution on AWS Lambda and Architect using the AI SDK, outside Vercel's own hosting.
Positive
social_quotient, Hacker News commenter
Comment on: Mayo Clinic's secret weapon against AI hallucinations: Reverse RAG in actionHacker News comment
Uses the AI SDK's simulateReadableStream to keep a streaming feel after a guardrail check forces the app to wait for the full answer.
Positive
djyde, Hacker News commenter
Comment on: Show HN: I wrote a browser AI assistant without requiring loginHacker News comment
Builds a browser AI assistant on both AI SDK Core and AI SDK UI, bridging requests through a background script that speaks the SDK's stream protocol.
Mixed
Umesh Malik, Independent developer
Vercel AI SDK in Production: Streaming, Tool-Calling & the Gotchas Nobody Tells You (2026)Personal blog post, umesh-malik.com
The SDK collapses a week of streaming plumbing into an afternoon, but aborts, loop limits, retries, rate limiting and cost attribution remain your job.
Mixed
Busy_Zucchini6284, Reddit user
How are you persisting useChat history across redeploys? The tool-call part is what got meReddit post, r/vercel
useChat history lives only in the browser, and saving flattened text broke tool-call replay; storing the parts array and validating it on load worked.
Mixed or negative, 2
Mixed
kollerp, GitHub user
Azure OpenAI is still Slow To StreamGitHub issue
With AI SDK 5 and Azure OpenAI gpt-5, chunks arrive server-side but useChat shows nothing until well after the message finishes.
Mixed
zknill, Hacker News commenter
Comment on: Go LLM SDK for streaming, tool-calling AI backends (plus frontend React lib)Hacker News comment
Finds the AI SDK easy to drop in but hard to build resilient systems on, citing no resumable streaming after a dropped connection or multi-device support.
GILD's fact checks, which don't count as sources
Checked Oct 12, 2026.AI SDK UI ships useChat, useCompletion, and useObject for React, Vue, Svelte, and Angular, with SolidJS support from the community. AI SDK UI overview
Open them in the recordCounted for All practitioners.
Positive, 6
Positive
jodysalt, Hacker News commenter
Comment on: What's the best programming language for coding agents?Hacker News comment
Recommends TypeScript with the AI SDK for building coding agents and calls it really nicely written.
Positive
Konstantin Komelin, Independent developer
AI Framework Comparison: Vercel AI SDK, Mastra, Langchain and GenkitPersonal blog post, komelin.com
Building the same examples in four frameworks, found AI SDK and Mastra calls the cleanest, with the AI SDK a single function call.
Positive
Rafael Saraceni, Independent developer
What I learned building my first AI agent, part 1Personal blog post, saraceni.me
After finding LangChain over-engineered and confusing, switched to the AI SDK and had a working chatbot quickly.
Positive
Matt Pocock, TypeScript educator
AI SDK v5: A Crash Course | Matt Pocock at React Universe Conf 2025Conference talk, YouTube (Callstack)
Presents the AI SDK as the one library for AI apps in TypeScript: one API across providers, one-line model swaps and type-safe Zod tool calls.
"…trying it out perspective. It means there's just one thing to learn, right? Which is really attractive when you're just getting into the space for the first time. You don't need to learn the weirdnesses with every single LLM provider and what…"
Positive
Felipe Cadavid, Software engineer at BrainGrid
Migrating to AI SDK v5: A Story of Tool Streaming, Caching, and Type SafetyEngineering blog post, BrainGrid blog
Migrating 14 tools to AI SDK 5 took renames and a type overhaul, then cut frozen-UI tickets to zero, sped tool execution 17% and trimmed tool-definition cost 7%.
"We migrated BrainGrid's core AI infrastructure from AI SDK v4 to v5. Here's how it went."
Positive
bearjaws, Hacker News commenter
Comment on: Use the Gemini API with OpenAI Fallback in TypeScriptHacker News comment
Has loved using the AI SDK to swap their apps between models, including local ones, and says it handles file attachments well.
Mixed or negative, 4
Mixed
joachimbulow, GitHub user
generateObject and generateText with output bursts CPU usage of tslanguageserver to 150%GitHub issue
Using generateObject, or generateText with an output schema, pushed the TypeScript language server to 150 to 200% CPU in the editor.
Mixed
niels-bosman, GitHub user
AI sdk v5 has insanely slow TypeScript performanceGitHub issue
On an M3 MacBook Pro the type checker could not keep up in files that import the AI SDK 5 beta.
Mixed
nanolookc, GitHub user
Memory leak with aisdk 5.19-5.20 and zod 4GitHub issue
Defining a tool with Zod 4 on AI SDK 5 drove the TypeScript server to about 8 GB before an excessively-deep type error; Zod 3 was fine.
Mixed
SirCameron, GitHub user, self-described
Type instantiation is excessively deep and possibly infinite.GitHub issue
Defining a tool on the AI SDK 5 beta triggered a TypeScript excessively-deep type error that version 4 did not, and the version 4 install docs were unhelpful.
Counted for All practitioners.
Positive, 4
Positive
Jordan Hindo, developer building Asset Hatch
Part 4: The Pivot - 3 Hours to SalvationPersonal blog post, jordanhindo.dev
After CopilotKit tool execution failed, Jordan Hindo moved Asset Hatch to AI SDK v6 in about three hours and got tools working, while docs still showed v4 message patterns.
Positive
bnchrch, Hacker News commenter on the Output.ai team
Comment on: Show HN: Output.ai - OSS framework we extracted from 500+ production AI agentsHacker News comment
Output.ai's LLM package is a thin wrapper around the AI SDK, using its tool-call retries, with durable workflow steps on Temporal.
No opinion stated
Thibault Le Ouay Ducasse, openstatus
How We Built Our Slack AgentEngineering blog post, openstatus blog
openstatus built its Slack incident agent on the AI SDK with Claude Sonnet and six tools, where every mutation tool returns a draft that a person must approve.
"We use the Vercel AI SDK with Claude Sonnet. The agent has 6 tools:…"
Positive
thomasfromcdnjs, Hacker News commenter
Comment on: Show HN: tpmjs - npm for ai sdk toolsHacker News comment
Uses the AI SDK heavily and built tpmjs, a registry and playground for AI SDK tools.
Mixed or negative, 8
Mixed
rpinckne, GitHub user
WorkflowAgent approval resume fails after intervening user media, after an approved tool already executedGitHub issue
When a user sends media while a tool waits for approval, WorkflowAgent runs the approved tool on resume and then fails with a missing tool results error before the next model call; ToolLoopAgent handles the same turn.
Mixed
hrithikbluelabel, GitHub user
HarnessAgent rewrites every tool input and result by plain substring replacement of the work directory, corrupting paths such as .github/workflows, with no way to switch it off.
Mixed
koonaso, GitHub user, self-described
With signed tool approvals enabled, every user-approved tool call fails on resume because addToolApprovalResponse drops the signature.
Mixed
wkusnierczyk, GitHub user, self-described
generateText() silently swallows AbortError in multi-step tool loopGitHub issue
generateText silently returns when an abort signal fires during a multi-step tool loop, so callers cannot tell the run was cut off.
Negative
cheriot, Hacker News commenter
Comment on: Agent design is still hardHacker News comment
Calls agent SDKs including the AI SDK and LangGraph flawed for hard-coding assumptions with no lower-level primitives to recompose.
Mixed
aron_snow, Reddit user
Comment on: Is Vercel AI SDK's vision to compete with LangGraph?Reddit comment, r/vercel
Likes the SDK for fast prototypes, but once flows stopped being linear it hit timeouts and bloated context, and LangGraph's graph model fit better.
Mixed
Dapper-Turn-3021, Reddit user
Is Vercel AI SDK actually good for building real AI agents?Reddit post, r/vercel
Finds the chat UI, streaming, and model switching clean, but building an agent means wiring orchestration, memory, tool routing, and feedback by hand.
Mixed
NicolaiHerforth, GitHub user
[Bug] Anthropic extended thinking: reasoning blocks lost during multi-step tool callsGitHub issue
With Anthropic thinking models, multi-step tool calls lose reasoning signatures, and onFinish drops 75% of reasoning blocks.
GILD's fact checks, which don't count as sources
Checked Oct 12, 2026.ToolLoopAgent stops after 20 steps by default; WorkflowAgent applies no default step limit, so a durable agent needs an explicit stop condition. Loop control
Open them in the recordEvery concern practitioners raise, most raised first.
Counted for All practitioners.
Raised as a concern, 14
Mixed
rhamnett, GitHub user
A Bedrock provider update moved Claude structured output to native mode, which padded output to the token cap; on the team's eval, length failures rose from 0 to about 10 of 20.
"On our internal drafting eval (20-item golden dataset, blind 3-vote LLM judge, identical prompts/schemas), moving from @ai-sdk/amazon-bedrock@4.0.112 to 5.0.29 took length-failures from 0/20 to ~10/20 and dropped judge scores from 0.75 to 0.48."
Mixed
plutonium-94, GitHub user
problemtic default value of max_tokens for unknown modelsGitHub issue
Anthropic-format calls to models newer than the installed SDK silently get max_tokens set to 4096.
Mixed
Igal Mazor, GitHub user
A Bedrock provider fix for Claude Opus 4.7 and 4.8 introduced a regression where a share of agentic runs combining tools with structured output end without an object.
Mixed
tim-inkeep, GitHub user
The author measured structured output on Claude arriving as one 3,197-character chunk after 20 or more seconds of silence. The documented workaround silently disables parallel tool calls, a regression from @ai-sdk/anthropic 2.0.2.
Mixed
sneefle, Hacker News commenter, solo founder
Comment on: Show HN: AI Applyd - a bot that applies to jobs for youHacker News comment
Found that @ai-sdk/openai 2.x breaks on a second request to a non-OpenAI endpoint through OpenRouter, so they switched clients.
Mixed
leojcyou, GitHub user
Anthropic structured outputs through the AI SDK return 400 errors on valid Zod schemas because unsupported JSON Schema keywords pass through unsanitized.
Mixed
tea-artist, GitHub user
When Claude called web search and an application tool in the same turn, the Anthropic provider rebuilt the message in an order the API rejects, so the next agent step failed.
Negative
koakuma-chan, Hacker News commenter
Comment on: GPT-5.3-CodexHacker News comment
Objects that the AI SDK fakes structured output on Anthropic by putting the JSON schema into a tool call, which confuses the model.
Mixed
NicolaiHerforth, GitHub user
[Bug] Anthropic extended thinking: reasoning blocks lost during multi-step tool callsGitHub issue
With Anthropic thinking models, multi-step tool calls lose reasoning signatures, and onFinish drops 75% of reasoning blocks.
Mixed
Armin Ronacher, founder of Earendil
Agent Design Is Still HardPersonal blog post, lucumr.pocoo.org
Ronacher's team adopted only the AI SDK's provider abstractions and drives the agent loop itself; Anthropic's web search tool routinely broke message history through it, and caching is easier on Anthropic's own SDK.
"For instance, the web search tool from Anthropic routinely destroys the message history with the Vercel SDK, and we haven’t yet fully figured out the cause."
Mixed
abhi-slash-git, GitHub user, self-described
anthropic api error: tool_use ids were found without tool_result blocks immediately afterGitHub issue
Valid message history with a tool call sent through the Anthropic provider fails with an error about tool_use ids lacking tool_result blocks.
Mixed
iborqe, GitHub user
Item 'rs_...' of type 'reasoning' was provided without its required following itemGitHub issue
Tool calls with an OpenAI reasoning model through openai.responses() fail with a reasoning-item error; the chat API avoids it but loses reasoning streaming.
Mixed
yonatanlavy, GitHub user
@ai-sdk/google stopped working with function calling in productionGitHub issue
Gemini function calling through @ai-sdk/google stopped working in production overnight with no code change, failing schema validation on a new response field.
Mixed
kollerp, GitHub user
Azure OpenAI is still Slow To StreamGitHub issue
With AI SDK 5 and Azure OpenAI gpt-5, chunks arrive server-side but useChat shows nothing until well after the message finishes.
Discussed without concern, 1
Positive
Luca Becker, aicommits maintainer
aicommits v1.0.0: Six Months of AI-Assisted Development Come Full CirclePersonal blog post, luca-becker.me
Moving aicommits to AI SDK v5 replaced every custom provider integration, so adding AWS Bedrock became a short task, though Ollama support dropped until a community provider appeared.
"While migrating to Vercel AI SDK v5, Ollama support was temporarily dropped."
Counted for All practitioners.
Negative
Kevin Peckham, Principal at Lightning Jar
A Deprecated Accessor That Still Typechecks Broke My Benchmark (and Maybe Your Agent)Engineering blog post, Lightning Jar
In AI SDK 7, response.messages silently became final-step only; the harness dropped tool history, causing 114 failed follow-ups until it switched to responseMessages.
Mixed
Pablo de Castro (pablodecm), GitHub user
uiMessageChunkSchema strict validation breaks backward due to providerMetadata additionGitHub issue
A patch release added a field to stream events, and users whose browsers held the previous client bundle got AI_TypeValidationError on every affected stream.
Mixed
bshzzle, Hacker News commenter on the Sourcebot team
Comment on: Show HN: Sourcebot - Self-hosted Perplexity for your codebaseHacker News comment
Sourcebot's self-hosted LLM support waits on the community Ollama provider, which did not yet support AI SDK 5, the version Sourcebot runs.
Positive
Felipe Cadavid, Software engineer at BrainGrid
Migrating to AI SDK v5: A Story of Tool Streaming, Caching, and Type SafetyEngineering blog post, BrainGrid blog
Migrating 14 tools to AI SDK 5 took renames and a type overhaul, then cut frozen-UI tickets to zero, sped tool execution 17% and trimmed tool-definition cost 7%.
"We migrated BrainGrid's core AI infrastructure from AI SDK v4 to v5. Here's how it went."
Mixed
rhamnett, GitHub user
A Bedrock provider update moved Claude structured output to native mode, which padded output to the token cap; on the team's eval, length failures rose from 0 to about 10 of 20.
"On our internal drafting eval (20-item golden dataset, blind 3-vote LLM judge, identical prompts/schemas), moving from @ai-sdk/amazon-bedrock@4.0.112 to 5.0.29 took length-failures from 0/20 to ~10/20 and dropped judge scores from 0.75 to 0.48."
Mixed
Igal Mazor, GitHub user
A Bedrock provider fix for Claude Opus 4.7 and 4.8 introduced a regression where a share of agentic runs combining tools with structured output end without an object.
Mixed
tim-inkeep, GitHub user
The author measured structured output on Claude arriving as one 3,197-character chunk after 20 or more seconds of silence. The documented workaround silently disables parallel tool calls, a regression from @ai-sdk/anthropic 2.0.2.
Positive
Jordan Hindo, developer building Asset Hatch
Part 4: The Pivot - 3 Hours to SalvationPersonal blog post, jordanhindo.dev
After CopilotKit tool execution failed, Jordan Hindo moved Asset Hatch to AI SDK v6 in about three hours and got tools working, while docs still showed v4 message patterns.
Mixed
SirCameron, GitHub user, self-described
Type instantiation is excessively deep and possibly infinite.GitHub issue
Defining a tool on the AI SDK 5 beta triggered a TypeScript excessively-deep type error that version 4 did not, and the version 4 install docs were unhelpful.
GILD's fact checks, which don't count as sources
Checked Oct 12, 2026.AI SDK 7 requires Node.js 22 or later and ships ESM only. Vercel provides automated migration scripts for the v6 to v7 upgrade. Migration guide: AI SDK 7.0
Open them in the recordCounted for All practitioners.
Mixed
Rohit Singh (Notoriousbrain), GitHub user
Stream resumption doesn't work when users switch tabs or background the appGitHub issue
useChat stream resumption recovers only on a page reload, so streams stay broken when users switch tabs or background the app on mobile.
Mixed
mattpocock, Matt Pocock, TypeScript educator
In useChat in @ai-sdk/react, state sent via transport#body is always staleGitHub issue
State passed to useChat through the transport body is always stale in @ai-sdk/react 2.0.5, so updated frontend state never reaches the server.
Negative
caleb-russel, Reddit user
Vercel AI SDK silent failure - mismatched maxSteps between useChat and streamText breaks tool executionReddit post, r/nextjs
Spent two hours finding that tools silently stopped running because maxSteps differed between useChat and streamText, with no error or warning.
Negative
jerrygoyal, Hacker News commenter
Comment on: Show HN: Mastra - Open-source JS agent framework, by the developers of GatsbyHacker News comment
Left the AI SDK for a native implementation in a production app after too many bugs and slow UI hooks; says the rewrite was little work.
Mixed
sebaFP, GitHub user
useChat: Infinite re-renders when using messages as useEffect dependencyGitHub issue
Using useChat's messages as a useEffect dependency caused infinite re-renders and a maximum update depth error.
Mixed
mdnanocom, GitHub user
@ai-sdk/langchain: reused toolCallId across LangGraph steps loses the later tool lifecycleGitHub issue
When a later LangGraph step reused a tool-call id, the LangChain adapter suppressed the second call's start, so the interface showed the earlier tool's name and input for it. Fixed five days later.
Mixed
zjjaxx, GitHub user
Streaming a LangGraph agent and its subagents into useChat, Vercel's LangChain adapter dropped each subgraph's namespace and closed every open text and reasoning part at each step, so the live interface broke mid-answer. Fixed a day later.
Mixed
mahan-fk, GitHub user
In a CommonJS backend such as NestJS, the ESM-only LangChain adapter did not recognize LangGraph's message chunks and silently dropped every text delta, so the chat showed only an ellipsis. Fixed five days later.
Counted for All practitioners.
Raised as a concern, 8
Mixed
robertyates, GitHub user
WorkflowAgent run has no root span: each model call becomes its own agent root in the traceGitHub issue
A durable WorkflowAgent run has no span covering the whole run, so trace viewers such as Arize, Phoenix and Langfuse show each model call as its own run, while ToolLoopAgent produces one run span.
Mixed
zknill, Hacker News commenter
Comment on: Go LLM SDK for streaming, tool-calling AI backends (plus frontend React lib)Hacker News comment
Finds the AI SDK easy to drop in but hard to build resilient systems on, citing no resumable streaming after a dropped connection or multi-device support.
Mixed
Umesh Malik, Independent developer
Vercel AI SDK in Production: Streaming, Tool-Calling & the Gotchas Nobody Tells You (2026)Personal blog post, umesh-malik.com
The SDK collapses a week of streaming plumbing into an afternoon, but aborts, loop limits, retries, rate limiting and cost attribution remain your job.
Mixed
Busy_Zucchini6284, Reddit user
How are you persisting useChat history across redeploys? The tool-call part is what got meReddit post, r/vercel
useChat history lives only in the browser, and saving flattened text broke tool-call replay; storing the parts array and validating it on load worked.
Mixed
Intrepid_Frosting_66, Reddit user
Comment on: Is Vercel AI SDK actually good for building real AI agents?Reddit comment, r/vercel
In a financial app, lets the AI SDK pick the tool and its parameters but runs every tool on the backend itself, for safety and traceability, at a higher token cost. Memory and retrieval are still unsolved, so each session starts cold.
Mixed
the_mitsuhiko, Hacker News commenter
Comment on: Absurd Workflows: Durable Execution with Just PostgresHacker News comment
Uses the AI SDK or Pydantic AI for provider independence, but neither has built-in durable execution, so they drive the agent loop themselves.
Mixed
rpinckne, GitHub user
WorkflowAgent approval resume fails after intervening user media, after an approved tool already executedGitHub issue
When a user sends media while a tool waits for approval, WorkflowAgent runs the approved tool on resume and then fails with a missing tool results error before the next model call; ToolLoopAgent handles the same turn.
Positive
sinatrastan, Reddit user
Comment on: Is Vercel AI SDK actually good for building real AI agents?Reddit comment, r/vercel
Runs a Lovable-style app builder on the AI SDK in production and says it works well for its users, though the author had to handle much of what a framework would usually cover.
Discussed without concern, 2
Positive
PrivateMTD, Reddit user
Comment on: Claude Agent SDK vs OpenAI Agent SDK vs Vercel AI SDKReddit comment, r/vercel
Builds on the AI SDK and enjoys it, while OpenAI's newer session auto-compaction and managed containers through the Responses API look tempting.
Positive
Kristian, Independent developer
Mastra vs AI SDK: I Built Production Apps With BothVideo, YouTube
After shipping production apps with both, frames the AI SDK as the model-interaction layer and Mastra as the infrastructure layer built on top of it.
"…layers. AI SDK focuses on model interaction, where Mastra focuses more on application infrastructure. But here's the important part is that every single feature that Mastra provides, you absolutely can build yourself. Because the question isn't whether you want to…"
GILD's fact checks, which don't count as sources
Checked Oct 12, 2026.AI SDK 7 adds WorkflowAgent, which persists agent state across steps on Workflow DevKit and resumes after restarts; ToolLoopAgent runs in memory and loses progress on a crash. WorkflowAgent
Open them in the recordCounted for All practitioners.
Mixed
safaiyeh, GitHub user
Per-byte base64 encoding of a 14 MB PDF out-of-memory killed a 2 GB production container within a minute, taking about 100 requests with it.
"On 2026-09-01 this OOM-killed one of our production API tasks (AWS Fargate, 2GB memory limit) in ~40 seconds: a single 14,078,689-byte PDF sent as a Uint8Array file part. The task went from a flat ~640MB to a hard kill at the container limit inside one minute, taking ~100 requests with it (94× ALB 502s) before ECS replaced it."
Mixed
DeJeune, GitHub user
readUIMessageStream deep-clones the whole accumulated message on every chunk, so allocation grows quadratically with turn length in ai 7.0.62.
Mixed
matthew-gizmo, GitHub user
streamText textStream tee path retains large streaming outputs in memoryGitHub issue
streamText's textStream buffers long outputs through a stream tee, causing memory-limit breaches in a Cloudflare Worker; the team added a production bypass.
Mixed
CharlesOural, GitHub user
Memory leak using Experimental downloadGitHub issue
A production app using @ai-sdk/google with experimental_download crashed out of memory, traced to how the SDK holds downloaded images.
Mixed
wong2, GitHub user, self-described
Poor performance when using Gemini image output with streamTextGitHub issue
Gemini image output through streamText took tens of seconds to a minute, while generateText and a direct API call returned within seconds.
Statements this group's sources agree on, then the ones close to agreement.
Close to agreement: each needs 19 supporting sources
Developers build frameworks, registries, and products on top of the AI SDK.
10 supporting sourcesThe AI SDK lets a team switch model providers without rewriting application code.
8 supporting sourcesTeams use the AI SDK's UI or model layer with another runtime, such as Mastra, LangGraph, Google ADK, Bedrock AgentCore, or Temporal.
5 supporting sourcesQuestions the sources split on, with the count on each side.
Evidence remains split
The SDK is enough, 2 sources
Some run their agent systems on the SDK's own loop, ToolLoopAgent, and stop conditions.
Needs a runtime around it, 8 sources
Others drive the loop themselves, move to a fuller agent SDK, or add Temporal for durable steps.
The three groups, then every practitioner by the context they work in, and how emphasis changes with scale.
Three groups drawn from the same sources. Choose a group to select whose experience counts. Within that group, each author counts once in the practitioner sentiment, with their latest view. Signals open on All practitioners. Teams and leaders have 18 accounts; GILD prints their sentiment from 20.
26 sources. Named product teams and leaders describe their choice of the AI SDK and their experience shipping features and agents.
68 sources. Individual developers describe AI SDK features, chat apps, and agents in their own projects.
94 sources. This group combines named teams with solo developers and GitHub bug reports. Their needs and source biases differ.
94 sources from practitioners, by the context they work in. Filled rows count for this group.
Emphasizes Provider switching, TypeScript ergonomics, and provider bugs
Emphasizes Shipping AI features fast, and what replaced the SDK where it fell short
Emphasizes Upgrades between majors and production memory incidents
Emphasizes Building agent frameworks on the SDK and owning the agent loop
What changes with scale. Individual developers praise the provider API and TypeScript design. They file most provider translation and type-checking bugs, and several run tool execution and memory outside the SDK. Named teams describe major-version migrations and memory failures on large files. They also build products and libraries on the SDK, sometimes using Temporal for durable steps.
Where this group's sources were published.
Counted for All practitioners, from 94 sources. Change group
106 sources for this group, 12 of them documentation
Earlier evidence remains when it still applies. Records tied to fixed or changed behavior carry Needs a recheck.
See sources by originWho each source is, how it knows, whether it still applies and what it counts toward.
Newest first, on its own page. Every count above opens its sources there.
Read all 106 sourcesAbout this read
A running review of what teams building AI features on AI SDK report, from individual builders to technical leaders. Each finding links to its sources, and each conflict shows both sides.
Counts cover only the sources GILD reviewed.
Choose a group to select whose experience counts. Within that group, each author counts once in the practitioner sentiment, with their latest view. GILD files each source in a group from how the account describes its author. A role or employer marked self-described is what the source states about themselves. Documentation checks facts for every group and never counts toward sentiment.
A source's date and whether it still applies are separate: a recent post can describe an old version, and an old one can still hold.
Flagged for a recheck, of the sources that take a side: teams and leaders 4 of 18, individual builders 16 of 67, all practitioners 20 of 85.
Each row opens its sources for the group you are reading.
| Finding | Teams and technical leaders | Individual builders | All practitioners | Sources |
|---|---|---|---|---|
| Current readCurrent sentiment | 8 positive, 9 mixed, 1 negative | 27 positive, 36 mixed, 4 negative | 35 positive, 45 mixed, 5 negative | Sources |
| PraiseOne API Across Providers | 2 of 2 positive (under the minimum) | 14 of 15 positive | 16 of 17 positive | Sources |
| PraiseStreaming Chat & Generative UI | 3 of 3 positive (under the minimum) | 7 of 9 positive | 10 of 12 positive | Sources |
| PraiseTypeScript Design & Types | 1 of 1 positive (under the minimum) | 5 of 9 positive | 6 of 10 positive | Sources |
| PraiseAgent Loop, Tools & Approvals | 2 of 2 positive (under the minimum) | 2 of 10 positive | 4 of 12 positive | Sources |
| PraiseTelemetry & Run Visibility | 2 of 2 positive (under the minimum) | 1 of 2 positive (under the minimum) | 3 of 4 positive (under the minimum) | Sources |
| PraiseSpeed | 1 of 2 positive (under the minimum) | 0 of 2 positive (under the minimum) | 1 of 4 positive (under the minimum) | Sources |
| ConcernBreaking Changes Between Majors | 6 of 6 raise it | 3 of 3 raise it (under the minimum) | 9 of 9 raise it | Sources |
| ConcernProvider Translation Bugs | 4 of 4 raise it (under the minimum) | 10 of 11 raise it | 14 of 15 raise it | Sources |
| ConcernDurability & Production Gaps | 0 of 0 raise it (under the minimum) | 8 of 10 raise it | 8 of 10 raise it | Sources |
| ConcernUI Hook Reliability | 0 of 0 raise it (under the minimum) | 8 of 8 raise it | 8 of 8 raise it | Sources |
| ConcernMemory & Performance | 3 of 3 raise it (under the minimum) | 2 of 2 raise it (under the minimum) | 5 of 5 raise it | Sources |
| ConcernLock-In | 0 of 0 raise it (under the minimum) | 1 of 3 raise it (under the minimum) | 1 of 3 raise it (under the minimum) | Sources |
| ConsensusStay provider-neutral | 0 supporting (under the minimum) | 8 supporting (below threshold) | 8 supporting (below threshold) | Sources |
| ConsensusPair it with an agent backend | 0 supporting (under the minimum) | 5 supporting (below threshold) | 5 supporting (below threshold) | Sources |
| ConsensusA foundation for other tools | 4 supporting (under the minimum) | 6 supporting (below threshold) | 10 supporting (below threshold) | Sources |
| ConsensusSome replace it | 2 supporting (under the minimum) | 1 supporting (under the minimum) | 3 supporting (under the minimum) | Sources |
| ConsensusBuilt for web apps | 0 supporting (under the minimum) | 1 supporting (under the minimum) | 1 supporting (under the minimum) | Sources |
| DisagreementCan the AI SDK alone run a production agent? | The SDK is enough 1, Needs a runtime around it 3 (under the minimum) | The SDK is enough 1, Needs a runtime around it 5 (under the minimum) | The SDK is enough 2, Needs a runtime around it 8 | Sources |
| DisagreementDoes the AI SDK tie a team to Vercel? | Independent of Vercel 0, Pulls toward Vercel 0 (under the minimum) | Independent of Vercel 3, Pulls toward Vercel 1 (under the minimum) | Independent of Vercel 3, Pulls toward Vercel 1 (under the minimum) | Sources |
| Current readEvidence mix | 38 sources | 80 sources | 106 sources | Sources |
GILD's checks of claims against official documentation, kept apart from the source counts.
