Week 29 Examples
- Updated the AI Slideshow Generator example to support multiple slides, drag-and-drop, and double-click to edit text.
Documentation
- Added links to examples at the top of relevant get started guides.
- Added links to guides in overview pages.
- Added more info on comments metadata throughout.
Website
New blog post: Comments: private threads and a natural home for AI.
Dashboard
- Added a button to download a room's Liveblocks Storage as JSON from the dashboard's room detail view.
Week 28 Examples
- New example: AI Slideshow Generator.
Documentation
- New section on rendering custom components inside threads.
- Updated all pages in the pricing section, increasing clarity.
Week 27 v3.21.0
-
Add support for public and private threads. Threads now have a
visibilityproperty that is"public"by default but can be set to"private"when created. Permissions can be used to decide which threads a user has access to, and threads can also be queried by their visibility to create filtered views. -
Add scoped comments permissions such as
comments:public:writeandcomments:private:none. -
Breaking: Remove
typeandkindfields fromHistoryVersiontype. The backend no longer returns these. -
Add
visibilitytocreateThread. -
Support querying by
visibilityingetThreads. -
Add
visibilitytouseCreateThread. -
Support querying by
visibilityinuseThreads. -
Add
useHistoryVersionYjsData()hook to retrieve raw Yjs binary data for a given version. DeprecateuseHistoryVersionData()in its favor. -
Add
visibilitytocreateThread. -
Support querying by
visibilityingetThreads. -
Add a
visibilityprop toComposer. -
Prevent
Composerfrom collapsing after focusing and blurring unless it was explicitly meant to support a collapsed state.
Documentation
- New guide: How to add private commenting to your app.
- New guide: How to use public and private threads.
Examples
- Update Linear-like Issue Tracker_to use latest Next.js caching features.
Website
- New blog post: What's new in Liveblocks: June 2026.
-
Week 26 v3.20.1
- Fix a bug where sending a too large WebSocket message could sometimes
overwrite a room's top-level storage key with
initialStorage, causing data loss. Thanks for reporting @watemerald!
Dashboard
- Added support for manual and automatic re-ingestion of (web) knowledge sources at specified interval.
- Streamlined display of knowledge sources and linking/unlinking of knowledge sources and copilots.
- Fix a bug where sending a too large WebSocket message could sometimes
overwrite a room's top-level storage key with
Week 25 v3.20.0
-
Add support for new resource-specific permissions. You can now start from a
*:reador*:writebase, then grant or deny access per resource (storage, comments, feeds) using new permission strings likestorage:noneorcomments:read. -
Deprecate
session.FULL_ACCESSandsession.READ_ACCESSin favor of["*:write"]and["*:read"]respectively. -
Deprecate
room.getStorageSnapshot()in favor ofroom.getStorageOrNull().
Examples
- New example: AI Spreadsheet.
- New example: Realtime AI Elements Chats.
- Added “?” button to various examples, featuring a pop-up that explains how to use them.
-
Week 24 v3.19.5
- Fix a
LiveListdivergence after reconnects: a pendingpushcould under specific timing conditions during a reconnect still cause a divergence between clients, despite the fix from 3.19.4.
Liveblocks dev server (v1.6.1)
- Fix a
LiveListdivergence after reconnects: when a client re-sends a pendingpushop whose node the server had already stored (the original ack got lost in the disconnect)
- Fix a
Week 23 v3.19.4
- Fix
LiveList.push()so concurrent pushes from multiple clients no longer settle out of order. - Fix a bug where a
LiveObjectkey deleted while a client was offline would reappear on reconnect, preventing the two clients from reconverging. - Fix a bug where reconnecting would emit too many update notifications for
LiveObjectkeys whose values had not actually changed. - Fix a bug where deleting a nested live value from a
LiveObjectomitted the removed value (deletedItem) from the change notification.
Examples
- New example: Collaborative SuperDoc editor.
Documentation
- New guide: Get started with SuperDoc and Next.js.
- New guide: Get started with SuperDoc and JavaScript.
- New guide: Get started with SuperDoc and React.
- New guide: Get started with SuperDoc and Svelte.
- New guide: Get started with SuperDoc and Vue.js.
- Updated get started guides for Liveblocks Storage, featuring more hook examples.
Website
- New blog post: How humans and AI will work together in the next generation of apps.
- New blog post: What's new in Liveblocks: May 2026.
Liveblocks dev server (v1.6.0)
- Update internal storage format of dev server. Note that your local dev rooms are not automatically migrated and will appear as empty rooms after the upgrade.
- Fix
Week 22 Documentation
- New guide: Get started with AI Presence.
- New guide: Get started with AI agents in React Flow.
- New guide: Get started with AI agent notifications.
- Updated Notifications get started guide to use secret key.
Showcase
- New item: AI slideshow editor.
- New item: AI replies in comment threads.
- New item: Multiplayer AI comment feeds.
- New item: AI generates slides with presence.
- New item: AI suggestions dropdown.
- New item: Conflict-free multiplayer editing.
- New item: AI comments bot with Chat SDK.
- New item: One AI bot for Slack and comments.
- New item: AI and humans editing together.
- New item: Multiplayer sync for custom UIs.
- New item: Agents work simultaneously.
- New item: Multiplayer React Flow at 60fps.
- New item: AI builds a flowchart with presence.
- New item: React Flow comment pins.
- New item: Multiplayer undo in React Flow.
- New item: Handsontable realtime editing.
- New item: AI presence highlighting changes.
- New item: AI comments like Linear.
- New item: Inline AI comments.
- New item: Liveblocks n8n nodes.
- New item: Mention notifications inbox.
- New item: AG Grid comment pins.
Liveblocks dev server (v1.5.0)
- Add
--random-port(-P) flag toliveblocks dev: bind a random free port instead of an explicit port number. With--cmd(-c), the chosen port is exposed to the command viaLIVEBLOCKS_DEV_SERVER_PORT. Ideal for CI (no port collisions ever). - Fix
LiveList.push()so concurrent pushes from multiple clients no longer settle out of order.
Week 21 v3.19.3
- Fix unexpected disconnects that could happen while receiving large or long-running streaming responses from the server (e.g. when loading a large initial storage state).
v3.19.2
- Fix: clients that have
backgroundKeepAliveTimeoutenabled will no longer disconnect before any pending Yjs updates have been synced to the server.
Examples
- Added AI comments, buttons, and presence to Linear-like Issue Tracker. It can read and edit issue content and properties.
- Added AI comment pins to Collaborative Flowchart AI. It can read and edit flow state.
- Added AI comments to AI Dashboard Reports. It can answer questions on the app's data.
- Added markdown AI replies to AI Comments and improved how the final comment is shown.
Liveblocks backend
- Storage chunking has been improved for slightly faster initial load times.
Documentation
- All get started guides now have a "Copy prompt" button for use in Cursor, Claude Code, more.
- New guide: Get started with AI replies in Comments using Liveblocks and Next.js.
Website
- New AI button and prompt on liveblocks.io homepage, allowing you to get started with one click.
Week 20 v3.19.1
- Update providers to support newer models up to GPT-5.5 variants, Sonnet 4.6, Opus 4.7, and Gemini 3/3.1 variants.
Infrastructure
- We have fully completed the internal migration of all rooms to our new v2 realtime data storage engine! Learn about the benefits.
Documentation
- New integrations section, featuring info on how to integrate Liveblocks into a number of new products.
- Integrations pages include Bolt, Claude, Codex, Cursor, Lovable, Neon, PlanetScale, Reply, Supabase, v0.
- Updated old guides and pages related to n8n, PlanetScale, Supabase.
- New copy page dropdown for copying markdown into various AI tools.
- Get started markdown homepage for AI.
- New breadcrumb UI on docs pages.
Examples
- Add AI features to Linear-like Issue Tracker example. Tag AI in comments and it can edit the document, links, properties, and show AI presence as it makes changes.