Skip to main content
Every planspace produces a document — a spec that the agent maintains and updates with each turn. You, your team and your agent have the ability to edit documents. Edit history and attribution is continuously recorded so that you can navigate to any previous version, see what changed, who changed it and why. The document is always connected to the conversation and reasoning that shaped it.

​
Editing

The document editor by default prefers to use markdown with:
  • Rich text — headings, bold, italic, lists, links
  • Code blocks — syntax-highlighted, language-aware
  • Mermaid diagrams — rendered inline from Mermaid syntax
However, it is very flexible and its default tools can be adjusted in user settings. Planspaces also view prototype code references as first class primitives to enable clarity of design and provide reviewers and agents concrete material reference in their reasoning. You can edit the document directly at any time. Your edits are saved as a draft at the current branch tip. When the agent responds next, your manual edits are incorporated into the new version and you can easily inspect which edits were done by who.

​
Semantic diffs

When the agent updates the document, Scott generates a semantic diff — a structured summary of what changed:
Change typeMeaning
AddedNew sections, concepts, or requirements introduced
ModifiedExisting content refined or updated
RemovedContent deleted from the previous version
Diffs appear as badges in the conversation and can be expanded for detail.

​
Version navigation

Every document version is accessible through the context flow:
  • Use the title dropdown to jump to the latest version or branch tip
  • Switch to the Versions tab in the left panel to see the full DAG
  • Click any node in the context flow to view that version’s document
You can reply from any version to create a new branch. When a version is ready for sign-off, request a review.

​
Inline comments

Select text in the document and leave a comment anchored to that selection.