Your Work Is Safe

A fair worry with any AI writing tool: will it lose my draft, or overwrite what I wrote? In Muses, three things keep your work safe — saving, history, and approval.

Check the save status

Muses saves automatically, but a network interruption, expired session, or failed request can prevent a cloud save. Before leaving an article, check that the editor says it is saved. If it is still saving or reports an error, keep the page open and address the message; text on screen is not proof that it has synced.

If saving remains unavailable, copy important text into a local file, restore your connection or sign in again, and retry. Use the editor's save control when needed and check that the status updates.

Recover a local draft

When you reopen an article, Muses may detect a local draft and show a recovery notice with its timestamp. View the differences first, compare the draft with the current content, and then choose whether to restore or ignore it. After restoring, confirm that the cloud save succeeds.

Local drafts belong to the current browser and device. Do not assume they will still be available on another device or after clearing browser data.

Restore from version history

Open the article's version history to browse and filter snapshots. Mark important versions as milestones or compare two versions. Check the content before restoring it; restoration saves the earlier content as a new version. History can recover existing snapshots, not every individual keystroke.

Review AI changes

When AI rewrites existing body text, inspect the differences and accept or reject each change. A pending proposal is separate from the saved article; check the save status after accepting changes too. To return to an earlier draft, look for the corresponding snapshot in version history.

See Letting AI Rewrite Your Draft for the review steps.

Where to go next

• Letting AI Rewrite Your Draft — how the review works, step by step.
• Star Power & Usage — what AI rewrites cost.