DocsWriting Studio › Auto-version rules

Auto-version rules

Last updated May 15, 2026 · 4 min read

Slima creates versions in the background — not randomly, but by meaningful rules. This article spells out when auto-versions fire and why those moments specifically.

Slima Writing Studio editor as a visual reference: left file tree / centre editor with format toolbar / right Notes panel

Four moments that trigger an auto-version

Moment What
After you stop editing for a while Pause and stay idle for a bit, and Slima leaves a version (not a fixed every-N-minutes clock)
Before the AI writes The Coach or AI analysis snapshots before it modifies a file
Before syncing to the cloud Right before your changes are pushed up, a local version is kept
Before you leave or close the editor Switching tabs / closing the page snapshots first, so nothing is missed

The logic: leave a restorable point whenever you might regret something — or content is about to be changed or shipped off.


Design principle: tied to key moments, not a dumb timer

Naive version-control tools use a dumb timer — "snapshot every N minutes." Slima doesn't — it ties versions to moments that actually matter to you:

  • You pause for a while (idle) → a version (usually the end of a passage)
  • Before the AI edits your file → a version first (so you can roll back if the AI gets it wrong)
  • Before syncing to cloud / before leaving the page → a version each (capturing the point right before you leave the current state)
  • You're typing fast → no version (it would break your flow, and the text isn't stable yet)

You can also make a named version yourself any time — see Create a manual version and name it.


See the auto-versions

In the version history panel, you'll see two kinds of dots:

  • Big dot — a named version (you made it)
  • Small dot — an auto-version (the system made it)

The panel has a "Show / hide auto snapshots" toggle.

See: Browse version history & diff


Do auto-versions eat a lot of space?

No. Slima versions store diffs — just "what changed since the previous version", not full copies of the book each time. A hundred auto-versions together are usually smaller than the plain text of one book.


Can I turn auto-versions off?

No. Auto-versions are always on and can't currently be turned off — they cost you nothing and save you everything.


Can I bulk-delete auto-versions?

Not (yet). Slima treats versions as a timeline — deleting a section would break the diff chain. You can "hide auto snapshots" for visual cleanup, but not delete.

We're evaluating "compress a date range of auto-versions" for the future.


Related

Was this helpful?