3.3 · Editing and versioning

How the editor works: autosave, restorable history, and locks so two people cannot collide on a document.

Editing context should feel simple and collaborative, so the editor autosaves everything, keeps history you can restore, and locks documents so two people never overwrite each other. This guide covers the mechanics, then the part that matters more: what happens to your edits after you save.

The editor

Context documents open in a full document editor. Type / for the block menu: headings, lists, task lists, quotes, code blocks, dividers, tables, and images. Changes save automatically (the footer shows Saved or Saving), and Cmd+S saves on demand.

One person edits at a time. If a document is open elsewhere, you'll see who has it and a Take over button to claim it.

AI quick edits

Select any text and choose AI in the floating toolbar to describe a change in your own words, or pick a preset:

Preset	What it does
Humanize	Strips hyperbole and AI clichés, varies rhythm so it reads human
Tighten	Cuts padding and redundancy while keeping every point
Break up the wall	Splits dense paragraphs, adds bullets where they help scanning
Match our voice	Rewrites to follow your brand writing guidelines
Answer first	Leads with the key point, then support
Fix grammar & spelling	Corrects errors only, leaves voice and structure untouched

Quick edits work on style and structure only. As the menu itself says: no research access, so it can't add new facts, stats, or sources. Facts are your job in this area, which is the point.

Version history

On your foundation documents, the History button opens Named Versions. Every change autosaves regardless, and on top of that you can:

Save a named version before a big rework, so there's a labeled point to come back to.

Compare any version against the current draft, side by side.

Restore a version when a rework went wrong. Your current draft is kept in history too, so restoring is itself undoable.

The practical effect: be bold: just save a named version before a big rework, and nothing is lost.

What happens after you edit

Your edits don't sit in a document waiting to be noticed. Context flows downstream in two ways:

Immediately: agents read context documents at the moment they work, so the next opportunity researched and the next draft written start from the calibrated version.
On recalibration: your accumulated context edits get folded into the Writing Profile and refreshed drafts, so the voice and claims stay in sync with what you've calibrated.

This is why stage 3 of the tutorial comes before creating anything. An hour of calibration here quietly improves every one of the hundreds of pages that follow.

Common questions

Can I break something by editing? Not if you checkpoint: History keeps the agent's original plus every version you've named, restore is one click, and restore itself is undoable. Autosaves between checkpoints get pruned over time, so name a version before a big rework.

Should I edit the document or regenerate it? Edit when the document is mostly right. Regenerate (from the document's menu, with a steering note) when it misses broadly, since a rewrite from scratch beats fighting a bad draft paragraph by paragraph.

Does fixing context fix the drafts I already have? No. A context change applies to work generated after it. Drafts already in production keep the facts they were written with until you regenerate them, so if you correct something material, sweep the open briefs that relied on the old version rather than assuming they healed.

Should we keep our context somewhere else and paste it in? No. Edit it here. History, named versions and locking exist so the in-app copy is the safe place to work, and a copy maintained elsewhere goes stale the moment an agent updates something.