Documents that never go stale.

Expand

The editor

The editor is WYSIWYG for prose and block-native for everything else. Open a document and start typing — no setup, no plugins. Formatting options live in the top toolbar; the outline rail on the right updates as you write so long documents never feel lost.

• Toolbar — headings, bold/italic/underline, alignment, lists, tables, code, and block inserts all sit at the top of every document.
• Contents rail — every heading becomes an anchor. Click a heading on the right to jump there, or use it as a live table of contents.
• Media and Data tabs — attachments, uploaded images, and any data files bound to the document live on the right rail, grouped so they're easy to find.

Create with AI

Open the Stable Baseline Agent from any workspace view and ask for a document you want. The agent drafts it end to end — headings, prose, callouts, and inline diagrams — and places it in the right folder so nothing gets misfiled.

Expand

Useful prompts:

• “Draft a runbook for a Postgres failover incident. Include detection, mitigation, and comms sections with a BPMN diagram for the handoff between on-call and SRE.”
• “Create a PRD for the new audit log feature in the Product folder. Link it to the plan PLN-1 and pull requirements from the last customer feedback.”
• “Write onboarding docs for a new platform engineer — what they need to read on day 1, day 7, and day 30.”

Edit with AI — or a bit of a document

With a document open, ask the agent things like “tighten the intro”, “convert the bullet list in §3 into a table”, or “add a callout warning about the deprecated flag”. The agent edits in place, shows you a diff, and waits for you to approve before saving.

• Whole-document rewrites — “turn this into a runbook format” or “rewrite for a non-technical audience”.
• Section edits — select a heading and ask “expand this with examples” or “shorten by half”.
• Targeted patches — “change every mention of ‘login’ to ‘sign in’” or “fix the broken link in the API section”.
• Inline diagrams — “add a sequence diagram under the ‘Flow summary’ heading” and the agent picks a type, generates it, and drops it in.

Formatting options

Everything you'd expect from a modern doc editor, with a few extras that make technical writing easier.

• Rich text — headings (H1–H6), bold, italic, underline, strikethrough, inline code, and links.
• Lists — bullet, numbered, and task lists (check boxes) with nesting.
• Callouts — info, tip, warning, and note panels for drawing the eye.
• Tables — resizable columns, header rows, and alignment per column.
• Code blocks — syntax-highlighted for every common language, with a one-click copy button.
• Keyboard pills — like ⌘K or Ctrl+Shift+P, for runbooks and shortcut guides.
• Highlights and coloured text — for emphasis inside paragraphs.

Diagrams inside documents

Diagrams aren't attachments — they live inline, alongside the prose that explains them. Click Insert Diagram in the toolbar to open three paths into a diagram: AI-generated from a description, freeform sketch, or write the DSL source yourself. See Diagrams for the full breakdown.

Expand

40+ diagram types, all inline

From architecture and sequence to BPMN with swimlanes, Gantt, ERDs, mind maps, and freehand sketches. Pick one and it renders in place — edit the source and the render updates live.

Images and data

Paste a screenshot or drag an image in and it's uploaded and attached to the document automatically. For charts, upload a CSV or JSON data file and bind it to a Vega / Vega-Lite diagram — your chart updates if the underlying data changes.

Folders and hierarchy

Every document sits inside a folder (or at the project root). Folders nest as deep as you like — group by service, by domain, by audience, whatever makes sense for your team. Drag to reorder, right-click to rename or move.

Expand

Friendly IDs

Every document gets a short ID like DOC-12 or ATL-42. Mention the ID in a chat, a pull request, or a commit message and anyone can jump straight to that doc without hunting through folders.

Sharing and permissions

Documents inherit access from their project and workspace. Everyone invited to the project can read and edit unless you scope them to a lower role. Projects can be made read-only for certain viewers — ideal for sharing finished specs with stakeholders outside the build team.

Version history

Every edit to a document creates a version snapshot — no manual saves, no lost work. Open the History panel to browse versions, see who made each change, and restore any past state with a single click.

Search and navigation

• Press ⌘K / Ctrl+K anywhere to open the workspace-wide search. It matches document titles, friendly IDs, and full text.
• The document tree on the left shows the current project's folders. Click to expand; click a document to open.
• Recent activity on the project dashboard surfaces what changed and by whom — teammates, external collaborators, and agents all show up the same way.