AI history and undo

What gets logged

Every time AI proposes a change to your prose, characters, worldbuilding, or any other part of your project, we log a row. The log captures who asked (you, or Penny on your behalf), what model produced the suggestion, the original text, the proposed text, the cost in dollars, the token count, and what you did with it (accepted, rejected, dismissed, or it errored out). This log runs forever. It is your audit trail.

Open the History button in the manuscript editor or the worldbuilder header to see this list. You can filter by surface, status, or scope (this project, this world, or everything across your account). Rows that you accepted show a Restore button.

What can be rolled back

When you accept an AI suggestion, we save a snapshot of the before state alongside the after state. That snapshot is what Restore uses to roll back the change in one click. It puts the prose back exactly as it was before AI touched it.

We keep the most recent 10 of these snapshots per surface per scope. Surfaces are the places where AI can write into your work: the manuscript editor, the worldbuilder, the Editorial Workbench, and Penny chat. Scope is the project or world the change touched. So if you have a project and a world, that is up to 80 restorable AI edits at any moment (10 per surface per scope, four surfaces, two scopes).

When you go past 10 in a given surface and scope, the oldest snapshot drops off. The audit log row stays forever so you can still see what happened, but the one-click Restore button is no longer available for that row.

Why 10 and not unlimited

Every snapshot is a copy of the prose at that moment. If we kept every snapshot forever, your account storage would balloon, and the cost would either come out of your subscription or get billed to you separately. Ten is the number we picked because it covers the realistic case (recent edits you might second guess) without turning into runaway storage. It maps well to how human memory works for recent edits anyway. If you find yourself wanting deeper history regularly, the Editorial Workbench has named snapshots that do not fall off the stack. You can save a checkpoint of the entire project before a big AI pass and come back to it any time.

Where each thing lives

• History button in the manuscript editor and worldbuilder headers opens a slide over drawer with the audit log for the current project or world. Restore shows on accepted rows.
• Undo button next to the History button rolls back the most recent AI edit on this project. Click it again to keep walking back. Stops after 10 steps.
• AI history pane in Account settings shows the same log across every project and world you own. Useful for billing review or for checking what AI did to a project you have not opened in a while.
• Workbench snapshots in the Editorial Workbench let you name a checkpoint of the whole project. Save before a big AI pass and roll the entire thing back later if you change your mind. These do not fall off the 10-step stack. Premium tier.

One more thing about typing

The 10-step stack is for AI changes and other big moves (paste, large delete, AI inject). Regular typing has its own undo stack inside the editor, the same as Word or Google Docs. Press Cmd+Z (or Ctrl+Z on Windows) to step back through your keystrokes. That stack is much deeper and is only constrained by your browser memory. The Pendraic History button is for the AI work; the editor's Cmd+Z is for your hands on the keyboard.