LoginSign Up
← Back to all sparks
L

Liveblocks

INFRA · APIS
Velocity4.4

Liveblocks is rebuilding multiplayer collaboration around AI agents as first-class users.

multiplayerai-agentsreact-flowstorage-engineopen-sourcecollaboration
◆Current state
Liveblocks shipped a six-week run of directional change: a brand-new React Flow SDK for collaborative node-graph editing, a Chat SDK adapter, a Feeds API explicitly framed for "Agent Workflows," a Python SDK for backend use, and v3.18 with breaking changes plus a mutateFlow() API that lets servers mutate diagrams from Node.js. The accompanying blog stream — "AI agents are becoming native users of software," feeds and APIs for agent workflows, n8n nodes — leaves no doubt about where the team is pointing. Underneath, the v1→v2 storage engine migration is in the long tail.
◆Where it's heading
Liveblocks is no longer just "realtime presence and comments for documents." It is positioning itself as the substrate where humans and AI agents share state — diagrams, chat threads, feeds — with the same primitives. The room.history.disable() API for hiding agent-generated writes from the undo stack is the small detail that gives the strategy away: the team is designing for a world where most edits in a room come from agents, and humans need to be shielded from that noise.
◆Prediction
The next two minors should bring more agent-shaped APIs (auth scoping for agents, read-only agent participants, server-driven LiveObjects mutations from non-Node runtimes) and broader framework adapters beyond React Flow and Handsontable. Expect Liveblocks to pitch the Chat SDK adapter as a path off OpenAI's hosted threads when teams want agent conversation state stored on their own infra.

◆Recent moves

  1. 2mo ago

    Week 17

    Migration to the v2 realtime storage engine is in the long-tail phase — most rooms moved, just stragglers left. New get-started guides extend the Handsontable integration. Quiet week of cleanup against the larger agent-platform push.

    View source ↗
  2. 2mo ago

    Week 16

    ⚡ SPARK

    v3.18.2 lands an experimental room.history.disable(fn) API to run storage mutations outside the undo stack — explicitly framed for AI background writes. n8n integration nodes ship in parallel. Together these tell the same story: agents are now a planning concern in the API surface.

    View source ↗
  3. 2mo ago

    Week 15

    ⚡ SPARK

    v3.18.0 is the most consequential release in this window: breaking API changes (LiveMap returns plain objects, legacy methods removed), a mutateFlow() API for server-driven React Flow edits from Node.js, and a coordinated blog drumbeat declaring agents as native software users.

    View source ↗
  4. 2mo ago

    Week 14

    ⚡ SPARK

    Two brand-new packages ship in one week: @liveblocks/react-flow for collaborative React Flow diagrams, and @liveblocks/chat-sdk-adapter for using Liveblocks Comments as a chat-sdk-compatible backend. Feeds — room-scoped message streams with a full hooks and REST surface — also debuts.

    View source ↗
  5. 3mo ago

    Week 13

    A cleanup week: clipboard handling fix for comment text, optional-vs-required body fixes on REST endpoints, and a notable dev server upgrade adding a live socket inspector and a maintenance-mode toggle. "Agent skills" docs page hints at what's next.

    View source ↗
  6. 3mo ago

    Week 12

    v3.15.3 introduces the Python SDK with full sync/async coverage of rooms, storage, threads, comments — opening Liveblocks to Python backends including Django, FastAPI, and the AI/ML tooling that lives in Python. v3.15.4 adds attachment download URLs. The dev server gains ID-token auth and read-only rooms.

    View source ↗