Versions & concurrent editing

Your writing is safe to work on from more than one place, easy to roll back, and simple to version with Git — so inside a project, an experiment or a stray agent run doesn’t cost you a draft.

Concurrent-edit safety

Multiple sessions can work on the same document at once without clobbering each other. Edits compose rather than collide, so collaborating with yourself across windows — or with an agent while you write — stays safe.

History & trash

Inside a project, every write preserves the content it replaced: the last 40 versions of a document, kept for 14 days. Restoring one is itself recorded as a write, so the text you restored over is preserved too — a restore that turns out to be the wrong call is just as recoverable as the change that prompted it.

Deleted files go to a project trash instead of vanishing — the last 50 items, kept for 7 days — and you can put any of them back where they came from.

Both are per project, anchored to the .multilo folder at its root. A file you open from outside a Multilo project has no such anchor, so it gets neither: no history, and deleting it is permanent. Keep work you care about inside a project.

GitHub-backed versions

History is a recent-past safety net; Git is the permanent record. Because a project is an ordinary folder, you can back it with Git and GitHub for full version history — one click away. Commit milestones, branch an experiment, and keep a durable record of how your draft evolved for as long as you like.