// news · agents · tools2026-05-28source: langchain / vercel / github

LangChain releases langchain-perplexity 1.3.0 with use_responses_api flag — Vercel AI SDK ships parallel patch update May 27

LangChain released langchain-perplexity 1.3.0 on May 27 with a new use_responses_api flag that switches the integration onto the Responses API surface, and the Vercel AI SDK shipped a parallel patch update the same day. The dual release is consistent with broader agent-framework convergence on the persistent-and-multi-turn execution patterns that the responses-API surface enables, and it lands in the same week as Google's Gemini Spark and Anthropic's enterprise agent expansion.

The Responses API surface adoption is the technical substance. Through 2024-2025 the dominant LLM-API surface for agent frameworks was the chat-completions pattern — turn-by-turn requests with the framework managing state externally. The Responses API pattern, originally introduced by OpenAI and now adopted across the major labs in varying form, lets the framework hand off state management to the model provider while still preserving the agent-framework's orchestration role. The use_responses_api flag in langchain-perplexity 1.3.0 is the LangChain side of the migration; the Vercel AI SDK patch update is the parallel move on the JavaScript-tooling side. Both releases are incremental — minor-version updates rather than major-version pivots — but the cumulative direction across the agent-tooling ecosystem is toward the Responses-API pattern as the default.

The release timing matters in context. Google's Gemini Spark launch the same week is the consumer-side parallel — a persistent agent running 24/7 across the Google ecosystem. Microsoft Agent Framework's release updates ship on the enterprise tooling side. The agent-platform layer is consolidating on the persistent-execution and multi-turn-state-managed patterns simultaneously across consumer, enterprise, and developer-tooling surfaces. For agent-platform users, the practical implication is that the framework choices that looked equivalent in 2024 are now diverging on architectural commitments — and the Responses-API-versus-chat-completions distinction is one of the durable axes of differentiation.

See our analysis →

LangChain — langchain-perplexity 1.3.0 release notes May 27 2026 → · Vercel — AI SDK patch update May 27 2026 → · Hacker News — Agent framework ecosystem May 2026 →