> For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://docs.mythos.new/features/version-history/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.mythos.new/_mcp/server. # Version history > Preview earlier project versions and restore one without deleting the versions that came after it. Mythos keeps a version history for each project's code. Delivered code changes and successful saves from the [workspace editor](/features/workspace-editor) add versions. A conversation, generated file, or Build that leaves the source unchanged does not need a new code version. Use history to inspect an earlier result, compare it with the current project, or restore a version that worked better. ## Preview an earlier version #### Open History Select the history button at the top of the workspace. The **History** tab lists saved versions with their description and date. #### Choose a version Select an entry to load that version in Preview. This is read-only: viewing it does not change the current project. #### Inspect the result Browse the historical Preview and open its files if needed. Editing remains locked while an older version is selected. #### Return or restore Select **Return to the latest version** to leave without changing anything. To make the older result current, select **Revert to this version** and confirm **Revert**. ## What happens when you revert Reverting creates a **new latest version** whose contents match the version you selected. It does not delete the versions that came later. If you change your mind, open History again and restore the version you were using before. > **Warning** > > Save any open editor drafts before reverting. Version history contains > successful saved results, not text that is still marked as unsaved in the > editor. The published site also remains unchanged until you open **Publish** and select **Update**. Restoring a workspace version does not immediately replace what visitors see. A revert restores project code. It does not undo records written to a database, messages sent through a connector, or other changes already made in an external service. If a revert is still being verified, choose **Check restore status** before starting another one. An unclear result is a reason to check the existing operation, not to repeat it. ## History and bookmarks The history panel has two views: * **History** lists saved project versions. * **Bookmarks** collects assistant results you bookmarked in chat for quick reference. A bookmark helps you find an important conversation result; it does not create or restore a project version by itself. ## Troubleshooting #### I reverted the wrong version Open History again and select the version that was current before the revert. It is still available, so you can restore it in the same way. #### I cannot edit while viewing history Historical versions are read-only. Select **Return to the latest version** before editing or starting another Build. #### My unsaved editor change is missing Only successful saves appear in version history. Save with **Save** or **Ctrl+S** before switching or reverting. ## Related * [Workspace editor](/features/workspace-editor) — make and explicitly save a direct code change. * [Building and editing](/features/building-and-editing) — create the next version with Mythos. * [Publish your site](/publishing/publish) — choose when the public version changes. > Learn how to turn an idea into a working app, improve it in Mythos, and publish it when it is ready.