Document Versioning
Every change to a brief, skill, or method is tracked over time, so you can see the full history of a document and restore any earlier version.
Overview
Document versioning gives you a complete audit trail of how a document evolved. Versions are created automatically as you edit, and you can also save named checkpoints at any point you consider significant. If a document goes in the wrong direction — or if you need to recover content that was removed — you can restore it to any recorded state.
Versioning applies to briefs, skills, and methods. It runs in the background with no action required from you.
How It Works
-
A baseline version is created automatically — When you first write real content into a new brief or document, a baseline version (version 0) is saved. This captures the initial state of the document.
-
Changes are tracked continuously — As you edit, the system tracks your changes in the background.
-
Versions are created after editing stops — When the document has been idle for a period, a new version is saved automatically with an auto-generated title and description based on the content.
-
Save a named checkpoint manually — At any point, you can save a named version from the document's history panel. Give it a meaningful label like "Approved by stakeholder" or "After kickoff changes" to make it easy to find later.
-
Restore an earlier version — From the version history, select any version and restore it. The document content is replaced with the content from that version, and the restore itself is recorded as a new version — so the history is never destroyed.
Key Capabilities
-
Automatic versioning: You do not need to do anything. Versions are created for you based on editing activity. The system deduplicates versions — if no content has changed, no new version is created.
-
Named versions: Save a named checkpoint at any meaningful moment. Version names can be up to 255 characters. If you save a named version when the content hasn't changed since the last version, the name is applied to the existing version rather than creating a duplicate.
-
AI-generated summaries: Each version automatically receives a generated title and description that summarizes what changed. These appear in the version history to help you find the right version at a glance.
-
Restore without losing history: Restoring a version creates a new "restore" version rather than overwriting the history. The complete record of all prior versions is always preserved.
-
Version numbering: Versions are numbered sequentially starting at 0. The number increments with each new snapshot, giving you a clear sense of how many distinct states the document has gone through.
-
Linked to plan generation: When a plan is generated from a brief, the system records which version of the brief document was used as the source. This lets you trace the brief state that produced any given plan.
Version Types
| Type | When it's created |
|---|---|
| System baseline (v0) | Automatically on first real content write |
| Auto | Automatically after editing activity consolidates |
| Manual | When you explicitly save a named checkpoint |
| Restore | When you restore a document to a prior version |
Tips
- Save a named version before major reviews or before asking someone to make significant edits. Named versions are much easier to identify in the history than auto-generated ones.
- Restoring a version replaces the current document content but does not delete history. You can always restore again to any version, including versions that came after the one you just restored.
- If a document hasn't changed since the last version, saving a manual version will name the existing version rather than create a new one. You'll see a confirmation of this behavior.
- Version history is visible to all members of the team account who have access to the document.
- AI-generated summaries on versions may take a moment to appear after a version is created. They are processed in the background.