LangGraph.js shipped `@langchain/[email protected]` on 2026-09-25 (with `@langchain/[email protected]` and Vue/Svelte twins). `useStream`'s `"enqueue"` multitask strategy can set `queue: "server"` so queued runs hit backend Runs REST instead of an in-memory client queue—surviving reloads, visible across sessions, with server-side cancelQueued/clearQueue. Default remains `queue: "local"`; custom AgentServerAdapter transports are unsupported. For frontends that need durable, collaborative agent queues.

Key Takeaways

  • ✓Shipped: langgraph-sdk 1.12.0 + react/vue/svelte 1.2.0
  • ✓Opt in with queue: "server" on useStream enqueue; local remains default
  • ✓Backend must implement Runs REST create/list/cancel endpoints
  • ✓Docs: useStream React howto + npm package
  • ✓Not supported with custom AgentServerAdapter transports
🔬

In-Depth Technical Analysis

Core Background & Industry Pain Points

Agent chat UIs often enqueue multitask submissions in the browser only—so reloads drop the queue, tabs diverge, and collaborators cannot cancel. Cloud LangGraph already exposes Runs REST; frontends still treated enqueue as a local toy.

Architecture Highlights & Internals

langgraph-sdk 1.12.0 adds queue: "server" for useStream's enqueue strategy, persisting runs via Runs REST create/list/cancel. Default stays local. React/Vue/Svelte 1.2.0 ship in lockstep. Custom AgentServerAdapter transports are unsupported.

Authoritative Benchmarks & Measured Scores

No public queue throughput numbers. Validate cross-tab visibility after reload and server-side cancel; backends lacking Runs REST should fail closed.

Developer Hands-on Guide

Install sdk 1.12.0 + react 1.2.0, set queue: "server", implement Runs REST, follow the useStream React howto.