FumidamaHow saving relates to history
Save and record (the default) above the document writes the file and records it in Git history. Choose Save only from the adjacent menu to write only the file without recording history. Selecting a mode does not run it; press the button or Command + S / Ctrl + S to run the selected action. Edited text is automatically saved to the file without recording history. Use Save and record or Record all to add it to history. The unsaved indicator can remain after autosave because it also includes changes not yet recorded in history.
If AI has changed several files, use Record all in the top bar and review the affected files to record them together. Resolve unfinished comments or conflicts when prompted. Use saved revisions as checkpoints for later review. History is managed by Git in the workspace; it is not an external backup service.
File saving and recording history can fail separately. After a failure, editing stops while the document and recovery content are retained. Follow the notification to preserve your work and reopen it.
Review external changes
Fumidama detects changes made by another process, such as an AI tool. If they conflict with your unsaved edits, review the comparison instead of overwriting either version.
Choose what to keep for each range and adjust it manually if needed before applying the result.
Read an earlier revision
Open History in the top bar, choose a revision in the right-hand list, and select a document in Explorer on the left. Choose Compare with current to see changes in context. For Markdown, open the same current document before comparing; the comparison includes unsaved edits. Historical content is read-only.
To adjust only part of a document, use the earlier content as a reference while editing the current version, as described in reviewing history with AI.
Check the scope before restoring
Restore this file above the document restores the displayed historical file. Related images and other documents are not restored with it.
Restore entire workspace lists files that will change, be recreated or be deleted, based on the selected Git revision. Files not recorded in Git and empty folders remain. Confirming records the restoration as a new history entry.
Unsaved edits, unfinished comments, conflicts or pending AI proposals can prevent restoration. Save, complete or resolve them as instructed before proceeding.
If the workspace or its Git data is lost, Fumidama may not be able to recover it. Deleting the workspace is different from restoring a document from history.
Organize history
You can combine eligible save commits created by Fumidama. Shared history and tagged ranges are protected. Review the selected scope and result; this is optional, not a required writing step.
Resume previous work
After a restart, Fumidama resumes verified unsaved work and returns to the previously selected document. Safe external changes are merged into the editing state. Resuming alone does not save the file or record history.
Use Previous edits to revisit work that needs a decision, including older recovery data and work kept for another folder. Compare the previous edits with the current file before restoring or confirming discard. Closing the preview keeps the contents. If the file is missing, Save text as… lets you save a copy to a new path while retaining the original recovery data.