The Revise SDK hits 1.0
The engine behind Revise is now available as the Revise SDK, and today it reached 1.0. It ships in two surfaces: a React component that opens .docx files inside your app — page-perfect rendering, tracked changes, and multiplayer editing over a Yjs provider you own — and a Node entry point that lets your server read, edit, and export the same documents headlessly, no browser required.
One tool contract, browser and server
The 1.0 milestone is convergence: both surfaces now speak the same canonical tool contract — the same document tools the Revise agent itself uses, with typed inputs and structured results. Wire them to any AI agent and your result-handling code is shared verbatim between web and Node. Malformed model input can't crash your agent loop: expected failures come back as structured results, never exceptions.
Tracked changes are the default posture
Server sessions now propose tracked suggestions by default instead of silently rewriting the document — the same safe stance as the editor. Every mutation reports the suggestion IDs it created, and a new review API lists pending suggestions with authorship metadata and resolves them by ID, so your agent can accept its own work and leave a collaborator's pending edits alone.
The full documentation lives at sdk.revise.io, including a complete backend reference. Building something on it? We'd love to hear from you at sdk@revise.io.