Browse / Software development / Second brain / agent-memory-kit
agent-memory-kit
awrshift
Built-in memory decides what to remember.
Open awrshift/agent-memory-kit → Does not match the four rules.
agent-memoryagent-orchestrationagents-mdai-agentai-memoryai-toolsclaude-codeclaude-code-plugincodexcontext-engineeringcontext-managementcursor
Built for OpenCode
ships .opencode CLAUDE.md and nothing for other agents.
In its own words
This one asks. Agent memory as plain files in your folder: the agent proposes, you approve, every line dated. Injected on Claude Code, Cursor & OpenCode; skills on Codex & Copilot. One memory per client, session handoffs, promotion into knowledge and rules on your yes, plus orchestration and QA layers.
Built-in memory decides what to remember. This one asks.
Your agent proposes, you say yes, it writes a dated line into plain files in your own folder. One memory per client, readable by every agent you run, nothing remembered without your yes.
"I wake up already knowing where we left off." — the agent this kit builds.
Install
Three commands in Claude Code, inside the folder where you work. Any folder will do; git is optional, and only needed if you want the wiki and rules to carry their history.
That is the technical part, and it happens once. From then on you only talk: work as usual, and say /memory-kit:close-session when you are done for the day. No database, no service, no extra cost. Setup reads what your folder already has and proposes before writing anything; your CLAUDE.md stays yours. Other agents install from the same repository, see Works with your agents.
Upgrading later, two commands, and the second needs the full id
Restart the session to apply. Upgrades never touch your files. Memory, handoffs and knowledge live in your folder, not in the plugin.
The repository's own description, then 13% of its README. Read the rest on GitHub ↗
Read from the repository's git tree on 2026-08-17.