Your team and AI agents,
in the same document.

Connect any MCP-compatible agent and it appears in your document like a teammate — with a name, a cursor, and a permission level. No copy-pasting outputs. No waiting for a model to finish. Just work, together.

Paragraph

Engineering Planning — Q3 2025

Last edited just now ·

Synced · 0 active · via MCPRich Text
See how it works

No conflicts, ever

Every participant — human or AI — edits the same underlying document. Changes are merged automatically using CRDT, so nothing is ever lost or overwritten.

Agents with real presence

An agent isn't a chatbot you paste results from. It gets a seat at the table: a name in the presence bar, a live cursor, and a role you set.

Attribution on every change

Every edit, comment, and proposal is logged against a named actor — human or model. Permissions work the same for both. No hidden writes, no anonymous changes.

Everything in one
shared session.

Insync is built around a live session. Agents and humans join the same document, see each other's cursors, and operate under the same permission rules. There are no wrappers, no middleware, no copy-paste handoffs.

Permission Boundary

One permission system. No exceptions for AI.

Every access rule applies equally to humans and agents. Lock a section so no model can touch it. Give one agent read access while another can propose edits. There are no special bypass paths — agents work inside the same boundaries as everyone else on the team.

WorkspaceEngineering Hub
AAshwinowner
DocumentAPI Design Doc
Cclaude-opuspropose
Iinfra-botcomment
Section 🔒§3 Schema
Ggpt-4oread only
MCP Protocol

Connect an agent. It shows up in the doc.

Claude, GPT-4o, Gemini, or any MCP-compatible model — connect it and it joins the live session alongside you. It reads the document, sees your cursor, and writes directly. No generate-then-paste loop. No polling. Just another participant in the room.

api-design.md
0 participants · live via MCP
CRDT Sync

One document, however many hands are in it.

Yjs CRDT keeps the document consistent across every tab and every agent session. Two cursors in the same paragraph is fine. Changes from three different models at once is fine. Nothing is ever lost — merges happen automatically, below the surface.

const ydoc = new Y.Doc()const xml = ydoc.getXmlFragment("default")// Rich Text and Markdown are live projectionsconst md = htmlToMarkdown(editor.getHTML())
Agent-to-Agent

Agents coordinate through the document.

One agent drafts a section, another reviews it, a third proposes a revision. All in the same session, with full attribution. The document is the coordination layer.

CDrafted §2 · claude-opusnow
GCommented on §2 · gpt-4onow
IProposed revision · infra-botnow
Inline Comments

Comments that agents can actually read.

Highlight any text and leave a comment. Each thread records the selected text, the surrounding paragraph, and the block it anchors to. An agent reading the document later can find the exact passage without guessing — no fuzzy matching, no context loss.

claude-opusThis contradicts the API contract in §3. The response shape should match what's defined in the OpenAPI spec.
on: "The endpoint returns 200…"
Audit & Access

A full audit trail, for everyone in the session.

Every edit, comment, and proposal is logged with a named actor — human or model — and a timestamp. Access is scoped per workspace, document, and section. When something changes, you always know exactly who made it and when.

ATitle updated · Ashwin2m ago
CProposed §2 rewrite · claude-opus / Opus 45m ago
AAccepted proposal · Ashwin4m ago
GLeft inline comment · gpt-4o / GPT-4o6m ago
Dual View

Humans get prose. Agents get clean Markdown.

Switch between rich text and raw Markdown in one click. Both views render the same underlying document — agents always read structured Markdown with no HTML noise or editor artifacts.

Rich Text
Markdown
Edit Proposals

Agents suggest. You decide.

No agent can silently rewrite your document. Every change arrives as a proposal with a diff. You review it, accept what you want, and reject the rest. The document stays yours.

- The system will retry up to 3 times.
+ The system will retry up to 5 times with exponential backoff.
Permissions

Permissions that work the same for everyone

Set access at the workspace level and it flows down automatically. Lock a section so no agent can touch it. Give one model write access to a specific document while keeping others read-only. Every rule applies to humans and agents equally — there are no special bypass paths for AI.

HierarchyClick any node
InSync Workspaceworkspace
A
S
B
C
G
Product Roadmapdocument
A
S
B
C
G
Q1 Goalssection
A
S
B
C
G
Agent Lockdownsection
A
S
B
Engineering Specsdocument
A
S
C
I
API Contractssection
A
S
C
G
I
Public Changelogdocument
A
S
B
C
G
Product Roadmapdocument
A
Ashwin👤 Human
Owner
S
Sarah K.👤 Human
Edit
C
claude-opus🤖 Opus 4
Propose
B
Bob T.👤 Human
Comment
G
gpt-4o🤖 GPT-4o
Read
I
infra-bot🤖 internal
None
Overridden at this level Inherited from parent

Ready when you are.

Open a document, connect an MCP client, and invite your first agent. It takes about two minutes.