Documents

Documents are the durable home for narrative work: reports, memos, plans, briefs. They’re markdown that you and your agents co-author, with comments anchored to passages, suggested edits you accept or reject, and a revision history that records who changed what. Use a document when a deliverable will be read, reviewed, and revised over time.

The review loop is what sets them apart from a file in a session. Without it, feedback on an agent’s draft goes into chat (“the second section is too long, and the churn number looks wrong”), the agent rewrites the whole thing, and nobody can tell afterwards which words were the agent’s and which were approved. On a document you select the churn number, ask the agent about it right there, and its answer lands in the same thread. When it proposes a fix, you see the change as a diff and accept it, and the history credits the agent’s words to the agent.

A quarterly business review might move through its week like this:

Day	What happens
Monday	The analyst agent drafts “Q3 business review” from the revenue data table
Tuesday	Dana comments on the churn figure and sends the comment to the agent
Tuesday	The agent answers in the thread and suggests a corrected paragraph
Wednesday	Dana accepts the suggestion; the revision is credited to the agent
Friday	The document is shared with the workspace and exported as a PDF

Creating documents

There are three ways a document comes to exist:

From the Documents page. Choose New document, give it a title, and tick Private — visible only to you if it shouldn’t be shared yet. It opens ready to edit.
From an agent. Ask an agent to write a document and it creates one directly. The session that produced it shows a card that opens the document, and the document links back to that session.
From a session draft. Markdown an agent wrote as an ordinary work product can become a document with Save as document in its viewer. You choose the title and whether it’s for you alone or everyone in the workspace. The copy is independent: later changes to the draft don’t reach it.

The Documents page lists durable documents alongside session drafts that haven’t been saved yet, marked Session draft, so everything narrative is in one place. Search matches text inside documents as well as their titles, and starring a document keeps it at the top of the list.

Writing and presentation

The editor is markdown underneath. Type / for the block menu: headings, lists, task lists, quotes, tables, code blocks, callouts, and dividers, plus display blocks — Chart, Stat tiles, Cards, and Section band — for figures that a paragraph would bury. Agents use the same blocks, and can also draw Mermaid diagrams.

A document is edited where it’s read, and several people can edit it at once. Each sees the others’ changes as they’re typed, with a named cursor for everyone in the text, and an agent’s edit lands without moving anyone’s caret. Changes save as you type; if your connection drops, what you type is kept on the page and sent when it returns.

Two controls in the header set how the document reads. Voice picks the type: Sans (the default), Serif for narrative and analysis, or Mono for data. Density is Roomy (the default) or Compact, for briefs and status updates. Both apply to the whole document, so an agent never has to choose colors or layout passage by passage.

How agents edit

Each document has a setting for what happens when an agent changes its text:

Agents edit directly — the agent’s changes land as new revisions. This is the default for documents an agent created, so an agent can keep its own reports current.
Agents suggest — the agent’s changes arrive as suggestions for a person to review. This is the default for documents you created, so your words don’t change without your say.

Pending suggestions appear in a banner above the document. Open one to see a line diff against the current text and the agent’s reason for the change, then Accept or Reject it. Only people review suggestions, and only people who can edit the document.

Comments

Select any passage and choose Comment. Threads sit in the margin beside the text they discuss, and the Comments button shows how many are open. Resolve a thread when it’s settled; reopen it if it isn’t.

When the document has an agent responsible for it, the comment box offers Send to that agent, and it’s ticked by default. A sent comment becomes the next turn of a conversation with the agent, which answers in the thread. The thread shows the agent working while it does, and View session in the confirmation opens the conversation behind the answer. Leave the box unticked for a note meant only for people.

Agents ask as well as answer. When an agent made an assumption it wants checked — “I used the September cohort for churn; should this be Q3 as a whole?” — it can leave a comment on the passage in question, and your reply goes back to the conversation that asked.

History and attribution

Version history, in the menu beside the document’s title, lists every revision with who made it. Compare any revision with the current text and restore it if an edit needs undoing; restoring writes the old text forward as a new revision, so nothing is lost, and only people can restore.

Attribution follows the words. A revision an agent wrote directly is credited to the agent. An accepted suggestion is credited to the agent that wrote it and records the person who accepted it, so the history separates whose words they are from who approved them.

Share in the document’s header sets who can open it: only you and the people you add, or everyone in the workspace. People you add get Can view, Can comment (which also lets them suggest edits), or Can edit. When a document is shared with the workspace, members can edit and viewers can read.

The same menu that holds version history exports the document as Markdown or PDF, copies it as Markdown, copies a link, renames it, and duplicates it. A duplicate is private to you and leaves the original’s comments, revisions, and sharing behind. Archive a document to take it out of the list, or delete it along with its history and comments.

Patterns that work

The living report — a recurring assignment keeps one document current instead of producing a new file each week. Leave it on Agents edit directly and read the history to see what changed.
Reviewed deliverable — anything customer-facing starts as a draft you save as a document, set to Agents suggest, so every agent change passes through a person.
Question-driven drafting — ask the agent to flag its assumptions as comments on the draft. You answer the questions in place and it revises, which is faster than briefing it again from scratch.