Trust
Local Git History for AI Memory Artifacts
Why Wenlan versions readable memory artifacts in a local git repository under ~/.wenlan/.git.
Article packet
Concepts
Developers who want memory changes to be auditable
5 min read
01
Readable memory artifacts are not invisible mutations.
02
Wenlan commits local artifacts into ~/.wenlan/.git.
03
Git history makes diffs and recovery familiar.
01
Quick answer
Wenlan uses real local git history so readable pages, session logs, and project status Markdown can be inspected over time instead of silently changing. Raw memory captures remain in the daemon database.
Wenlan uses a familiar developer primitive for auditability. The memory database powers retrieval, while git history makes local artifacts easier to inspect and recover.
02
When this problem appears
AI memory often changes in ways users cannot inspect. That is risky when memory steers future coding, product, or client decisions.
03
Inspect memory changes
Use git when the timeline matters.
- Run git -C ~/.wenlan log --oneline for the local artifact timeline.
- Run git -C ~/.wenlan diff when you need to inspect readable artifact changes.
- Inspect page and session changes as normal diffs.
- Use correction before destructive deletion when history matters.
- Back up git history with the rest of ~/.wenlan.
04
What to check next
Do not edit daemon-owned state behind Wenlan's back. Git history is an inspection and recovery surface, not a replacement for memory APIs.
Try the local memory loop
Install Wenlan, connect your AI client, and verify that capture, recall, and handoff work on your machine.
FAQ