We've added collaborative .docx editing with SuperDoc, automatic re-ingestion of AI knowledge sources, shipped a complex AI spreadsheet examples, and shared our vision for how humans and AI will work together.
Join thousands of companies using Liveblocks to build multiplayer experiences for people and agents.
This June, we’ve added collaborative .docx editing and new AI features.
To use the latest features, update your packages with the following command.
If you were previously on Liveblocks 3.17 or below, make sure to follow our upgrade guides before updating.
SuperDoc is an open-source editor that runs in the
browser and works directly with .docx files, the format used by Microsoft
Word.
With Liveblocks, you can add a realtime collaboration layer around SuperDoc, handling shared document state, presence, and conflict-free syncing so teams can build collaborative Word editing without having to engineer the multiplayer infrastructure from scratch.
Our Collaborative SuperDoc editor example
The collaborative editor uses Liveblocks-powered Yjs, and supports rich-text formatting, multiplayer undo/redo, and a suggestion mode, allowing owners to easily accept/deny changes from other users.
To get started, we’ve published guides for five frameworks: Next.js, React, JavaScript, Svelte, and Vue.js. There is also a live example you can download and try out.
AI Copilots allows you to create advanced singleplayer AI chats with a ready-made React component. In minutes, you can import a chat into your application, that can understand context, take actions, and interact with your front end.
Our AI Dashboard Reports example highlights many different features.
One of its key features is knowledge, which allows you to submit websites and files to your AI, enabling it to accurately answer questions using your own information.
You can now re-ingest web knowledge sources automatically on a set interval, so a copilot’s answers stay current as the underlying pages change—for example, re-crawling your docs or pricing page every day. Additionally, we’ve also reworked the dashboard UI, making it easier to manage copilots and reuse knowledge sources across multiple copilots.
Opening a copilot, enabling a knowledge source, and setting daily re-ingestion.
You can also trigger re-ingestion manually at any time, by clicking the “Re-index” button.
Triggering re-ingestion manually.
You can find the new UI in the dashboard, or get started with a new project.
We’ve added two new examples showing how to build realtime AI apps with feeds and Vercel AI Elements. These examples demonstrate exactly how to add these features to your product, and are a solid starting point for your own projects.
In our new AI Spreadsheet example, an AI agent can read and edit cells alongside you, in realtime. Each cell is synched to Liveblocks Storage, meaning state is fully multiplayer, for both humans and agents.
Our AI Spreadsheet example
As the AI works, you can see its presence in the UI as it modifies cells. Additionally, you can leave comments on table cells, and trigger AI by tagging it inside a thread.
You can find the example in our gallery, under AI Spreadsheet.
Our Realtime AI Elements Chats example shows how to build a multiplayer AI chat with AI Elements, where multiple users share and follow the same conversation in realtime.
Our Realtime AI Elements Chats example
Messages update live for all connected users, including as they stream in. You cnn also create new chats, and switch between them.
You can find the example in our gallery, under Realtime AI Elements Chats.
This June, we published a new post on how humans and AI will work together in the next generation of apps—our perspective on where collaborative software is heading as AI agents become active participants alongside people.
It details how you can integrate AI agents into your product as active participants.
Read blog post
initialStorage, causing data
loss. Thanks for reporting @watemerald!LiveList and LiveObject divergence and reconnection issues:
concurrent LiveList.push() calls settling out of order, a LiveObject key
deleted while offline reappearing on reconnect, redundant update notifications
on reconnect, and the removed value (deletedItem) missing from change
notifications.LiveList divergence after reconnects, where a pending
push could still diverge under specific timing conditions despite the
earlier 3.19.4 fix.*:read or
*:write base, then grant or deny access per resource—Storage, Comments, and
Feeds—using new permission strings like storage:none or comments:read.session.FULL_ACCESS and session.READ_ACCESS in
@liveblocks/node in favor of ["*:write"] and ["*:read"] respectively.room.getStorageSnapshot() in favor of room.getStorageOrNull().LiveList reconnect fixes (v1.6.1).To use these latest features, update your packages with:
Contributors include:
7 authors