04:50
Your agent’s memory, with a history.
Memory History records each change to the memory files your agent writes, from the moment you install it. See what changed. Put an old version back, after a preview.
Install for Claude CodeInstall for Hermes Agent
A separate, open-source plugin for Claude Code and Hermes Agent. It works on its own, with no Bilinc account.
A silent film with captions. In Claude Code, the agent writes a memory note and the history lists every change as a diff. Then the undo puts the earlier version back, and the undo is kept in the history too. The same steps run in Hermes.
Every version, kept.
Claude Code and Hermes Agent rewrite their own memory files as they work. Memory History keeps each version, so you can look back.
- It records. Each time a memory file changes, Memory History keeps that version. History starts when you install the plugin, and the first scan is the starting point.
- It shows. The history command lists the versions, newest first, with a diff for each change.
- It puts back. Undo shows a preview, then writes the old version back after you confirm. The undo is a new version in the history, so you can undo the undo.
Install it in your agent.
Pick your agent.
It tracks Claude’s auto memory and your global ~/.claude/CLAUDE.md. Project CLAUDE.md files stay in git.
Install
claude plugin marketplace add ReARCLabs/bilinc-memory-history
claude plugin install bilinc@bilincRun these in your shell. Python 3.9 or newer must be on your PATH; until it is, the plugin stays quiet and does nothing.
Commands
| Command | What it does |
|---|---|
/bilinc:history | Lists versions, newest first, with a diff for each change. Add a file name to see one file, for example /bilinc:history MEMORY.md. |
/bilinc:undo | Shows a preview, then writes the old version back after you confirm. /bilinc:undo MEMORY.md 2 undoes the second most recent change to that file. |
/bilinc:undo --session | Rolls back everything this session wrote to memory. |
/bilinc:restore | Lists deleted memory files and brings one back. |
/bilinc:status | Shows the journal size and the Cloud state. |
Every command that writes shows a preview first and waits for your confirmation.
It tracks MEMORY.md and USER.md for the profile you enable it for: writes by the memory tool, /memory approve, and edits you make by hand. For a profile, add -p <name> to both commands.
Install
hermes plugins install ReARCLabs/bilinc-memory-history#hermes
hermes plugins enable bilinc-memory-historyIf the Hermes gateway is running, restart it so it loads the plugin:
hermes gateway restartThen start a new session. The first session records the current files as the starting point.
Commands
| Command | What it does |
|---|---|
/bilinc-history | Lists versions, newest first, with a diff for each change. Add MEMORY.md or USER.md to see one file. |
/bilinc-undo | Name the file and the change, for example /bilinc-undo USER.md 1. It shows a preview; add --yes to apply it. |
/bilinc-restore | Lists deleted memory files and shows a preview of bringing one back. Add --yes to apply it. |
/bilinc-status | Shows the journal size and what is recorded for the active profile. |
Hermes loads memory when a session starts, so an undo or restore takes effect in the next session (/new).
How undo works.
The same on both agents.
- It shows a preview first. Nothing is written until you confirm.
- The undo is recorded as a new version, so you can undo the undo.
- A deleted memory file can be brought back with restore.
- Your memory files stay plain Markdown, in the agent’s own folder.
Local by default, and no account needed.
The history is stored on your machine, in ~/.bilinc/memory-history/<agent>/, where only you can read it. The plugin needs no account.
Claude Code: Cloud is opt-in
Cloud moves memory between machines. It is off for every project until you turn it on for that project, and it needs a Bilinc API key. Before anything is sent, you see what would be uploaded. Each version is scanned for secrets on your machine first, and a version that looks like it holds one is never sent.
Hermes: local only
Hermes has no Cloud. Everything stays on your machine.
You can delete the local history whenever you like: /bilinc:wipe-local in Claude Code, /bilinc-wipe-local in Hermes. Each asks you to confirm first.
Works in Claude Code and Hermes Agent.
| Agent | Memory it tracks | Cloud |
|---|---|---|
| Claude Code | Auto memory (~/.claude/projects/*/memory/) and your global ~/.claude/CLAUDE.md | Optional, per project, off by default |
| Hermes Agent | MEMORY.md and USER.md of the profile you enable it for | Not available |
Questions.
What does it record?
The memory files your agent keeps: Claude Code’s auto memory and your global CLAUDE.md, or Hermes’s MEMORY.md and USER.md. Each change after you install it is recorded, and the first scan is the starting point.
Does it send my memory anywhere?
No, unless you turn Cloud on for a project in Claude Code. Cloud is off by default and shows you a preview before anything is sent. Hermes has no Cloud.
Do I need a Bilinc account?
No. The plugin works without one. Only Cloud, in Claude Code, needs a Bilinc API key.
Why not just use git?
Git is the right tool for project files, and Memory History leaves those to it. Memory files sit outside your repository, change while you work, and are rewritten by the agent without a commit. Memory History records each change as it happens and needs no setup.
Does undo change anything without asking?
No. It shows a preview first and writes only after you confirm. In Hermes, add --yes to apply it.
What if I undo by mistake?
The undo is recorded as a new version, so you can undo the undo.
Which agents does it work with?
Claude Code and Hermes Agent.
How long is history kept?
The newest 200 versions of each file are kept. /bilinc:status in Claude Code or /bilinc-status in Hermes shows the journal size.
Is it the same as the Bilinc memory server?
No. It is a separate open-source plugin that keeps a history of your agent’s own memory files. It talks to no Bilinc server unless you turn Cloud on in Claude Code.
Open source, MIT licensed.
The source is on GitHub.