Velt×
LexicalAdd comments and co-editing, plus live presence, to your Lexical editor, for your users and your AI agents. Threads stay pinned to nodes as the document tree updates, and every agent edit lands as a suggestion your users approve, so a comment on a heading never jumps to the paragraph below it.
Free tier. No credit card. First comment in 5 minutes.
The Q3 campaign centers on the migration storyHope: moving from async reviews to live collaborationEthan. Pricing: three usage tiers from $0, no per-seat cost.
live cursors + a comment anchored to the selection · Yjs merges every keystroke
The problem
Your users expect to comment and co-edit in Lexical, and your AI agents need that same editor with a human approving before they touch user work. Comments that survive Lexical's node-tree updates are a multi-quarter build, and the moment anchoring breaks, feedback lands on the wrong node. Co-editing is the harder half: rolled by hand it means overwrites, lost work, and merge conflicts, the "my changes disappeared" bug reports, plus a websocket fleet and offline merge to keep alive. And the harder question is your agents: a useful agent needs to change the work, but an agent with write access to user content is what your buyers' security review blocks, so without a consent step you choose between an agent that is useful and an agent that is safe. Every quarter spent on this is a quarter not spent on your own product.
Velt is the review and collaboration layer built for Lexical: your users and your AI agents work the same editor, with comment threads anchored to the node, and every agent suggestion is a change a human approves before it lands.
Features
Clause 7 omits a liability cap. Suggested fix attached.
// An agent posts a suggestion as a first-class user.
await velt.comments().add({ author: agent, suggestion });
// On approve, the change fires through your webhook.Your AI agent comments and suggests on the editor as a first-class user; a human approves or rejects, and on approve the change fires through your webhook with a permanent record.
@Maya pulled into the thread
2 Repliesimport { VeltComments } from "@veltdev/react";
<VeltComments textMode />Threaded comments on nodes and ranges, with replies, @mentions, reactions, and attachments.
TiptapLexical
CodeMirror
BlockNote
React Flowplus the core library for your own editor, whiteboard, or grid
import { useVeltCrdtExtension } from "@veltdev/tiptap-crdt-react";
const extension = useVeltCrdtExtension({ editorId });CRDT merge across clients on the node tree.
import { VeltPresence, VeltCursor } from "@veltdev/react";
<VeltPresence />
<VeltCursor />Live named cursors and selections in the editor.
Suggested a tighter figure on the rate line.
// Propose changes reviewed like a diff.
<VeltComments suggestionMode />Propose changes as accept-or-reject suggestions, reviewed like a diff.
Maya mentioned you on Q3 forecastmention
“@you can you review before Friday?”
Sarah replied on the Q3 threadreply
forecast.xlsx · cell B12
Ethan requested your sign-offsign-off
contract.pdf · due today
import { VeltNotificationsTool } from "@veltdev/react";
<VeltNotificationsTool />In-app, email, and Slack alerts on every comment and @mention.
“The variance comes from the vendor rate change, see row 18.”
import { VeltRecorderControlPanel } from "@veltdev/react";
<VeltRecorderControlPanel />Pin a quick voice, screen, or video clip in context on the editor.
await velt.versions().save({ name: "Draft v3" });
await velt.versions().restore({ id });Named checkpoints on the document, saved and restored by API.
TiptapLexicalCodeMirrorBlockNoteReact Flowplus the core library for your own editor, whiteboard, or grid
<VeltProvider singleEditorMode>
{/* one editor instance */}
</VeltProvider>Run Velt review on a single editor instance without multiplayer.
a brand-and-compliance agent flags an off-message line or a missing disclosure on the node and suggests the rewrite as a first-class user; a human approves or rejects, and on approve the change fires through your webhook with a permanent record of who allowed what.
Setup
npm install @veltdev/react @veltdev/lexical-crdt-reactimport { VeltProvider } from "@veltdev/react";
<VeltProvider apiKey={API_KEY}>
<App />
</VeltProvider>// Mount Velt on Lexical
<VeltComments />
// + the CRDT adapter for co-editingWhy Velt
Liveblocks syncs people and agents into your app's state; Velt adds the step Liveblocks does not, every agent change on Lexical is a suggestion your user approves or rejects, on the record.
Enterprise
The controls your buyers' security reviews ask for, in writing.
Adding Velt to Lexical does not move that surface's content off your stack. Per-feature data providers keep comment content, attachments, and user PII on your own infrastructure; Velt stores only minimal identifiers.
FAQ
Both. Velt adds threaded comments and conflict-free co-editing on the same Lexical editor.
Yes. Robust anchoring binds each thread to its node, so a comment rides updates and re-renders instead of detaching.
Yes. Velt anchors to any node or range, including custom and decorator nodes.
Yes. An agent posts a suggestion on the node as a first-class user, and a human approves or rejects before it lands.
No. Velt runs without you standing up a websocket fleet or merge backend.
On usage, not seats or integrations: you pay for documents with review activity in a month, with a free tier for development and early production.
Free tier. No credit card.
First comment in 5 minutes.
Slate
PlateJS
Ace Editor
Let's lead with this. Strongest angle we have, @Ethan can you tighten the wording?