Versioning
Local Git History
Inspect built-in page revisions and, if you choose, your own Git history of readable files.
At a glance
01
Wenlan keeps page revisions in its own history; it does not automatically create a Git repository for your readable files.
02
You can maintain a separate Git history of Markdown files yourself if you want to inspect your own commits.
01
What is versioned
Wenlan writes human-facing artifacts under ~/.wenlan, including pages, session handoffs, and current status records. It does not automatically commit them to Git.
Page revisions are available in the app or through get_page_revisions over MCP. They are separate from any Git history you maintain.
02
Inspect history
To inspect built-in page history, open the page in the app or use get_page_revisions over MCP. For Git history, first check whether your pages folder is in a repository and confirm that the reported root is the repository you intend to inspect.
If you have not set up a repository, there may be no Git history to inspect. If you do maintain one, its history contains only what you have committed.
git -C ~/.wenlan/pages rev-parse --show-toplevel
# If the reported root is your intended repository:
git -C ~/.wenlan/pages log --oneline -20 -- .03
Recover with care
Your own Git commits can help you inspect previous Markdown files, but restoring a file is not a full database rollback.
If the durable knowledge is wrong, the safer product path is to capture a correction or forget the memory by ID. That keeps the index and readable artifacts aligned.
04
Use with your other tools
Because pages and sessions are normal files, you can inspect them from editors, terminals, or apps such as Obsidian. Some users symlink the pages folder into an Obsidian vault for reading.
Keep writes disciplined. Wenlan should remain the writer for generated artifacts unless you intentionally edit a human-owned page.
ln -s ~/.wenlan/pages ~/Documents/Wenlan-pages05
Privacy boundary
Page revisions and any Git history you create can retain old private context.
Do not publish, sync, or attach ~/.wenlan blindly. Redact or create minimal reproductions when reporting bugs.
Next
Models and Keys
Choose local memory mode or configure an optional on-device, local server, or cloud model for background language work.
Read next