Skip to main content

Review changes & recover

Nebula Writer separates three related ideas: pending agent changes, agent action history, and saved document versions. Use the right surface for the kind of recovery you need.

Review pending changes#

After an agent edits a file, inspect the editor before accepting the result. The review surface depends on the format:

FormatWhat to inspect
Markdown and LaTeXAdded, removed, or replaced source text
DOCXOperation summary and the rendered paged document
SpreadsheetAffected cells, formulas, sheets, formatting, and warnings
PPTXAffected slides or objects and the complete rendered slide

Choose Accept All only when the source values and visual result are correct. Choose Discard All when the scope or source was wrong. Where individual decisions are available, keep only the operations you have verified.

Warning: DOCX and PPTX agent operations can update a backed-up working file before the review decision. Discard All restores that backup; it is not always declining an unapplied preview.

Inspect the rendered result#

A diff cannot show every consequence of a document edit. Check the native surface for:

  • Text that wraps or overflows after a font or size change
  • Tables, images, or slide objects that moved
  • Formulas whose references changed
  • Headers, footers, page breaks, and speaker notes
  • Citations or claims that no longer match their source

For consequential work, save a copy before a broad edit and ask the agent to work in one section, sheet, or slide batch at a time.

Use agent action history#

Action history records agent operations separately from document version history. Open it with Cmd/Ctrl + Shift + H to understand or reverse recent agent work. The app also provides shortcuts for undoing and redoing agent actions.

Action history is useful when the current document is still open and you want to step back through recent agent operations. It is not a permanent project backup.

Compare or restore a saved version#

Version history supports saved versions for Markdown, LaTeX, DOCX, PPTX, and spreadsheet files. Depending on the file and available history, you can inspect a version, compare it with the current document, or restore it.

Version history with saved states, comparison controls, and restore actions

Before restoring:

  1. Save or copy the current file if you may need it again.
  2. Check the version time and document name.
  3. Compare the content where comparison is available.
  4. Restore, then reopen or reload the editor if prompted.
  5. Inspect the rendered document and save it.

Restoring one document does not rewind unrelated files in the project.

Recover from a bad result#

Use the smallest recovery that solves the problem:

  1. Pending review: discard the unapproved review session.
  2. Recent agent action: use agent action history.
  3. Older saved state: compare and restore a document version.
  4. Deleted project file: use the short delete undo while it is available.
  5. External or broad loss: recover from your normal backup or version-control system.

After recovery, narrow the next request:

Prompt
Edit only the Risks table on page 2. Preserve the row order, all numbers, and every other section. Stop and ask if the table cannot be updated without changing its structure.