Where it fits
Why reph when you already have…
Each of these is good at its own job. reph is where the document work between them happens.
| You already use | Great at | Where the doc falls short | What reph adds |
|---|---|---|---|
| GitHub | Versioning and reviewing code. | Docs get reviewed as source diffs, so people outside engineering rarely weigh in, and nobody edits together live. | Suggestions and threads on the rendered document, live co-editing, and git import that refreshes from the source. |
| Google Docs | Real-time writing for everyone. | Rich text, not markdown. Moving content to or from an agent, a repo or a README means converting it. | Markdown as the source of truth, with the same live editing and comment threads. |
| Notion | Wikis, databases and team spaces. | Pages are blocks. Markdown is an export, and agents work through a block API. | Plain markdown documents with an MCP server, where agent edits arrive as suggestions you accept. |
| ChatGPT / Claude | Drafting, thinking out loud, and rewriting. | The draft lives in a chat thread. Teammates can’t review it, and the next conversation starts over. | Turn the conversation into a durable doc your team reviews, and that the agent can come back to. |
| Cursor | AI editing inside a codebase. | Docs in the repo are for the people who have the repo open. | A shared workspace for everyone else, reachable by the same agents over MCP. |
reph: markdown for the AI age.