Tiptap AI Toolkit

@arnau_gomez_farell Just upvoted. Dev tools usually have the weakest onboarding emails in SaaS, curious if you're treating that as an edge here.

The part that resonates is treating rich text as not plain text - an AI that blindly string-replaces will happily corrupt a table or a live collab cursor. Concretely: are the AI edits applied as ProseMirror transactions/steps so they merge with concurrent user edits through your collab layer, or as a diff that can clobber in-flight changes? And is the model constrained to your schema so it cannot emit invalid nodes, or do you validate and repair after the fact?

Congrats on the launch. The part that stands out to me is the diff engine for structured documents. For AI editing, the trust boundary is usually not the model writing text, but proving exactly what changed and letting humans review it quickly. Are you planning source/intent annotations in the diff view, or is the focus mainly on reliable document operations first?

Now this is something I can genuinely use!

the reconciliation and diff answers cover the single-agent case really well, curious about the multi-agent one: if I've got several different AI agents with different jobs (one summarizing, one restructuring, one fact-checking) all hitting the same doc through the server-side API, is there any way to scope an agent to only certain nodes or sections, or does anything with API access get edit rights to the whole document and you just have to trust your own orchestration to keep them in their lane

Real-time AI edits on a live document are a hard distributed systems problem. You're essentially layering an AI agent on top of CRDT or OT-based sync, and conflicts aren't always commutative. We've thought about this pattern when building structured data capture, and the ordering of writes matters a lot. How does the toolkit handle AI and human edits that conflict on the same node simultaneously?

It's been a few months working on this, so I'm happy for the launch. This is just the beginning though. In the following weeks, we're going to post many videos and demos about what the AI Toolkit can do. Stay tuned for our updates on LinkedIn and our website.And props to @bdbch for working on Tracked Changes. Without it, the AI Toolkit would not be possible.

The server-side editing piece is what grabs me — agents that keep working after the tab closes is exactly the gap in most "AI in docs" setups. Question on document awareness: for a long, structured doc (nested tables, embedded nodes), what do you actually feed the model so it can target "this paragraph" reliably — a semantic/structural map of the doc, or the full serialized content? Curious how you keep that from eating the context window as documents grow.

The AI Toolkit unlocks a new frontier of collaborative working for your users, don’t miss out on the launch and give it a try now 🚀

Plugged it into a side project and had a collaborative doc running by lunchtime. The extension API feels really intuitive compared to other editors I've wrestled with.

Building a content tool on my own editor stack right now, so this hits close. The hard part I keep fighting: when AI edits a document live, how do you make the edit boundaries visible enough that a human reviewer trusts the diff? Curious how you handled that in the toolkit.

Hey PH! When OpenAI shipped the Assistants API in 2023, we built a first prototype of AI agents editing documents. It technically worked, but the agent did things to the document, not with you.Two and a half years later, this is the version where it finally feels like collaboration: agents make precise tracked changes users accept or reject, edits stream in live, and server-side operations keep running after the tab closes. It's headless just like our editor: no UI, no required agent framework. You own your agentic loop and models and the AI Toolkit handles the document operations.If you've tried building this yourself, I'd love to hear about your experience!

Hey Product Hunt! 👋We’re a small team of EU-based developers who work on rich text editor frameworks every day. That's Tiptap.A year ago we hit a problem we couldn't ignore: Everyone wants their AI to work inside documents, not in a chatbot and not with copy-paste. But building that so it actually works is way harder than it looks, because rich text is not plain text. There's a lot going on in how browsers render documents, and one wrong AI edit can break things: complex stuff like tables and charts, interactive stuff like buttons, or just the real-time collaboration happening while people work together.So we spent months building Tiptap’s AI Toolkit to solve it once, properly, so you don't have to.The AI Toolkit gives you:Server-side editing: you don't need an open browser anymore. You can build agents that edit documents even when your users are away, and the changes flow back into their editors through our Collaboration service.Document awareness: you can tell the AI to edit a specific paragraph or sentence and it knows where that is in the document. It can tell a table from a row from a header, and so on.Precise edits: highlight any text in your document and ask the AI to change it.Diff engine: a brand new diff algorithm that can compare structured documents.This is great for anyone building a smart, AI-driven experience for documents (or document-like things) inside their app.Check out our launch post at https://tiptap.dev/blog/release-... for more details, and a chance to get a free promo plan if you want to partner with us and give feedback.Cheers,Philip