History

Two different things in TaleShard are called history. This page covers both, and the difference matters: one is your session’s undo list, the other is a document’s saved versions.

The History panel

Open it from the clock icon in the header, immediately right of Undo and Redo. It reads History when closed and Hide history when open, and it is the only way in — there is no menu entry and no keyboard shortcut.

Opening it closes the Localization panel, and the reverse.

What you are looking at

A list of steps, newest at the top, for whichever stack your caret is in — the project’s, or an open document’s. Never both at once. The header names it: History for the project, or the document’s own title.

Each row is a sentence rather than a diff:

Renamed tag "Guard"
Renamed variable code "gold" → "coin" and 12 others
Updated entity item "Ryn Zhao" — Description
Deleted tag "Guard" and 12 others
Reordered 5 tags
Moved 3 nodes

Steps on a board also carry the board’s name underneath. A step whose board no longer exists simply drops that line.

When something has no name to use, the row falls back to its area — Canvas change, Entity change, Variable change, Project settings change, and so on.

In a document the vocabulary is shorter: Typing, Paste, Cut, Delete, Formatting. In a spreadsheet it is the operation you performed — Edited cells, Fill down, Insert column, Change column type, Convert to table, AI generation, and the rest.

Reading the list

Two rules divide it:

• Now marks where you currently are. It appears only when there is something above it to redo.
• Session start closes the list, and is always there — including when the list is empty.

Empty, it reads Nothing to undo yet. Your edits show up here as you make them. — or, on a document’s stack, Nothing to undo in “«title»” yet. Edits to it show up here.

The footer states the limit plainly: Session only — this history is cleared on reload and is not shared with collaborators. On a document it adds It covers this document only; the rest of the project has its own history.

Jumping back

Hover a row and it offers Undo to here — or Redo to here, above the Now marker. Click it, or press Enter.

Hovering a board step for a moment also reveals the board it touched, so you can see what a row means before committing to it. The whole range is applied as a single move, so you are not dragged through every intermediate board on the way.

Clicking a row never moves your caret, so the panel cannot accidentally switch which stack it is showing while you use it.

How far back

There is no cap. Nothing trims the list and nothing prunes an old step. The only bound is the session, and reloading ends it.

Saved versions

A document — a lore document or a spreadsheet — has a second, durable history that has nothing to do with undo. Open it from the History button at the top right of the document itself, labelled Version history.

This is the one that answers who changed this, and when.

Saving one

Type an optional name — the placeholder suggests Optional name (e.g. Before refactor) — and press Save version.

Restoring one

Each row shows the name or Auto-save, a relative time — just now, 3h ago, 2d ago, then a date — and the author. Restore asks first:

Restore this version? This will replace the current document content with the snapshot from «time». All collaborators will see the change instantly. You can undo it with Cmd/Ctrl+Z.

Two things in that sentence are worth reading twice. All collaborators will see the change instantly — a restore is not a private preview. And it is undoable, because it is your own write, so a restore you regret is one Ctrl+Z away for as long as your session lasts.

Delete removes a version. Nothing prunes them otherwise; there is no cap and no retention window.

Empty, the panel reads No saved versions yet. Use Save version above to capture the current document.

There is no activity feed