We’ve added ways for users to subscribe to individual threads, released an MCP server to speed up development, and made a large improvement to our billing.
Join thousands of companies using Liveblocks ready‑made collaborative features to drive growth in their products.
This April we’ve added new APIs, released an AI tool, and improved our billing.
To use the latest features, update your packages with the following command.
If you were previously on Liveblocks 2.23 or below, make sure to follow our upgrade guides before updating.
When using Comments and Notifications, end users no longer need to be participating in threads to receive inbox notifications. From now, users can choose to subscribe to individual threads meaning they’ll be notified when new comments are added.
Users can also choose to unsubscribe from threads they’ve participated in. After upgrading, you’ll find the new menu option in your threads, as shown above, and in notifications, shown below.
Along with the updated components, we’ve also added corresponding hooks for
thread subscriptions, allowing you to subscribe and unsubscribe from threads
programmatically. Here’s how the new
useSubscribeToThread
hook can be used.
We’ve also updated previous hooks, such as
useThreadSubscription,
simplifying creating your own primitives.
To reduce confusion in our APIs, we’ve updated a number of names to better
reflect their purpose. Any previous methods related to roomNotifications now
refer to roomSubscriptions, learn more in
our upgrade guide.
We’ve created an MCP server for Liveblocks, which allows you to talk to your application in AI tools, such as Cursor and Claude, as you build it. Our server has 39 different tools available, allowing AI to generate rooms, write comments, send notifications, read realtime data, and more.
It’s just one command to install it, find more info in our MCP server documentation.
We’ve rolled out a major improvement to our pricing that makes it easier and more predictable to scale real-time collaboration in your product: you now only pay for users who return after their first session.
To learn more, make sure to read our focused blog post on introducing fairer billing with first day free.
Here’s a list of other improvements in our changelog this month:
@liveblocks/client methods which return threads and their associated inbox
notifications now also return the thread’s associated subscriptions.textMentions in room subscription settings.closeAi Tiptap command to manually close the AI toolbar.triggeredAt for notification webhook events.prepareThreadNotificationEmailAsHtml and
prepareThreadNotificationEmailAsReact functions now avoid duplicated
comments between two emails data.Composer and the emoji pickers in
Comment/Thread.InboxNotification component now uses resolveRoomsInfo for
textMention notifications to make them link to the mentions’ room
automatically if href isn’t set.emojibaseUrl advanced option on LiveblocksUIConfig to allow
choosing where Emojibase’s data used by the Liveblocks emoji picker is fetched
from: another CDN, self-hosted files, etc.withLiveblocksEditorOptions not passing all options to BlockNote.AiToolbar focus behavior in Safari.FloatingToolbar focus behavior in Safari.Symbol.dispose
yet..mutateStorage() and .massMutateStorage() where mutating
storage could potentially corrupt the storage tree.<AnchoredThreads /> threads rendering if the editor's view is
null.To use these latest features, update your packages with:
Contributors include:
9 authors