A place for important writing.
Write with your team and an AI assistant in the same document. Discuss the draft in comments, see what the AI changed, and ask for a review when it is ready. Your coding agents can read and edit it over MCP, too.


Edited 2 minutes ago1 of 2 readyRFC: Presence over Reverb
Problem
Awareness updates currently fan out through the Hocuspocus provider, which means presence dies whenever the connection drops even though the Reverb channel is healthy.
Proposal
Move cursor state onto Reverb, maybe. Keep Yjs for document state.
Cursors and selections move to the existing document.{id} channel. Yjs keeps document state only.
LivemarkFailure modes
- Reverb down, Yjs up: editing works, presence blank.
- Yjs down, Reverb up: cursors move over stale text.
Livemark 2 minutes ago
PendingMove cursor state onto Reverb, maybe. Keep Yjs for document state.
Cursors and selections move to the existing document channel. Yjs keeps document state only.
The tradeoff was implied but never stated.

Alex Lund about 1 hour ago
AppliedScoping the fallback here so it stops being an open question.
Draft from your notes and files. Add them to a project so the assistant can use them. Review the draft with your team and work through changes in comments.
What gets written here
Write specs, design docs, proposals and blog posts.
Specs and RFCs
Draft from project files and meeting transcripts. Get the spec reviewed, then let your coding agents read it over MCP.
Design docs and plans
Discuss the design in comments on the draft. Save a version before a big rewrite so you can return to it.
Proposals and policies
Ask the people who need to sign off to review the document. See who is ready and who still has concerns.
Essays and blog posts
Ask the assistant for feedback on your draft or help with a rewrite. Download the finished post as Markdown for your blog.
Writing your own posts
How it works
Start with a document.
- 01
Create a document
Start writing, or add files, transcripts, notes or images for your agent to use.
- 02
Draft
Write a first draft yourself or ask your agent to draft from what you added.
- 03
Revise
Work with your agent in Livemark or over MCP to revise the draft.
- 04
Review
If you have reviewers, ask them to mark it Ready or Not yet.
- 05
Build
Give your coding agent access to the document over MCP.
What Livemark does
Suggestions
See exactly what the AI changed.
Each AI edit shows what changed and who made it, next to the passage it changed. Undo an edit from its card, or ask for a suggestion to accept or reject before it applies. Agents cannot overwrite text someone changed after they read it.
Reviews
Approved means every reviewer said Ready.
Choose who needs to review the draft. Each person marks it Ready or Not yet. The document is Approved when everyone on that list has said Ready.
Ready
Ready
Not yetChats
Ask the assistant, then decide what to keep.
Ask questions about the document or get help revising it. The assistant can read your project files and connected tools. Type / to run a skill your team has added.
MCP
Your agents work from the same documents.
Claude Code and any MCP client connect over OAuth and get 31 tools to work with your documents and files. They can read drafts, leave comments and make edits you can review. Use the read-only endpoint to give an agent access without letting it make changes.
Read the document
Commented on Proposal
Proposed an editwaiting
Projects
Keep the project files with the draft.
Group related documents and files in a project. Connect Linear, GitHub or Notion so the assistant can read what you have access to. These connections are read-only.
retro.txt
board-update.pdf
survey.csv
Editor
Write it together, in one document.
See each other's cursors as you write and leave comments on specific passages. Add tables, code blocks or Mermaid diagrams. Save a version before a rewrite and restore it later. Download any document as Markdown.

Latest guide ·
How much spec does an AI coding agent need?
Decide what an AI coding agent needs before it builds, with a CSV export example showing scope, permissions and acceptance cases.
David Hemphill