Workflow
Version history
Tag named snapshots of project state so you can track progress and look back over time.
What gets snapshotted
Open History in the sidebar to see the project timeline. A snapshot is a labeled, read-only record of the project task state at a single point in time — every task title, status, priority, type, intent, and outcome at the moment you tagged it.
Snapshots are useful when you want to capture "this is where we ended sprint 3" or "this is what shipped to beta" and refer back to it without affecting the live project.
Creating a snapshot
Click Add snapshot in the History section, type a label (for example, "Beta 0.3 candidate"), and confirm. The snapshot appears at the top of the timeline with the date, the label, a status breakdown, and the total task count.
Snapshots are non-destructive — they do not move tasks, change statuses, or affect anything else in the project. Tag as many as you want.
Reading the timeline
Each entry on the timeline shows:
- Relative time (for example, "2 days ago") and exact timestamp on hover.
- Label you gave the snapshot.
- Status counts — a quick visual of how the work was distributed across To Do, In Progress, Done, and Blocked.
- Task list — expand to see every task that existed at that moment with its status.
Use it to answer questions like "what was actually in the Done column when we declared this done?" or "how much did we get through this week compared to last week?"
When to snapshot
Tag a snapshot at meaningful moments: end of a sprint, before a major regeneration, before you switch modes, when you ship a release. There is no penalty for tagging too many.
- For the kanban itself, read Backlog and task management.
- For shipping to a real URL, read Publish and share.