Change history

Every agent turn and every explicit save in the editor produces a commit — a snapshot of your project at that moment. Change history gives you a timeline of those commits, with metadata about what changed and the ability to use them as context for new prompts.

Where to find it

In the editor:

• Click the ≡▾ hamburger menu (top-left) → Change history.

The modal opens with a commit list, newest first.

What each commit shows

• Latest — the most recent commit. Always one of these.
• Live — the commit currently shown in your preview iframe.
• Published — the commit currently served on the public URL.
• Not published — every commit ahead of "Published" but not yet pushed live.

Two kinds of commits

• Agent turns — every time the agent finishes work. Commit message is a short summary of the changes.
• Editor saves — every Cmd+S / Edit→Play / Publish. Commit message reads Editor save or includes a count of changed entities.

Silent auto-saves (every ~10s in Edit mode) do NOT create commits — they're disk-only drafts. Only explicit saves promote to commits.

Using history with the agent

There's no "press here to revert" button. Instead, you describe what you want to the agent and reference the commit context:

The coin-pickup behavior I had two turns ago felt better. Roll
back to that.

Or more specifically:

At commit "Added enemy slime", the wizard could still walk through
trees. After "Wired tilemap collision" it was fixed. Bring back the
slime but keep the collision fix.

This is more powerful than a literal revert — you can ask for selective roll-back, hybrid combines, "undo just the visual changes from this turn", etc.

If you really want a clean revert to one specific commit:

Revert the project to exactly the state at commit "X". Drop all
changes since.

The agent diffs and applies.

Why history matters

Because Umicat is agent-driven, sometimes the agent makes a change you don't immediately notice. Maybe it tuned a value, refactored something, added a feature you didn't ask for. History is how you find that.

If something feels different and you don't know why:

1. Open Change history.
2. Scroll back to when things felt right.
3. Compare the commit messages between then and now.
4. Ask the agent to undo the specific thing.

What's not in history

• Silent auto-saves — by design (drafts only).
• Asset uploads and deletions — assets live in a separate store, not the commit history. The commit references the asset by id; deleting an asset doesn't show up in history but breaks any commit that referenced it.
• Settings changes (title, description, tags) — these are project- level metadata, not commits.
• Chat history — separate, viewable in the chat panel scroll.

Limits

• The last 1000 commits are kept. Older commits are pruned periodically. In practice this is 6+ months of active development for most projects.
• You can't push commits between projects. Forking ("save this as a new game") is not yet supported.

Next steps