Built-in memory decides what to remember. This one asks. Agent memory as plain files in your folder: the agent propos...
Copy the install, test the workflow, then decide if it earns a permanent slot.
Fresh repo activity plus visible builder pull. This is the kind of tool people test before it turns obvious.
Copy the install, test the workflow, then decide if it earns a permanent slot.
You can test this quickly and remove it cleanly if it misses.
GitHub health unknown. no security policy. Fresh enough repo health and manageable issue load keep the risk controlled.
AI Agent
Multiple
Model
Multiple
Fastest way to find out if agent-memory-kit belongs in your setup.
Copy the install command, run a real test, and back it out cleanly if it slows you down.
git clone https://github.com/awrshift/agent-memory-kit ~/.claude/skills/agent-memory-kitRun this first. You will know quickly if the workflow earns a permanent slot.
rm -rf ~/.claude/skills/agent-memory-kitNo messy cleanup loop. If it misses, remove it and keep moving.
Install Location
~/ └─ .claude/ ├─ commands/ ├─ skills/ │ └─ agent-memory-kit/ ← installs here ├─ agents/ └─ settings.json
Built-in memory decides what to remember. 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.
Source: GitHub repository
Source check: October 8, 2026
Upstream commit: October 8, 2026
Repository state: Not marked archived
Honeystax upvotes are community interest signals, not star ratings. GitHub stars and repository health are source measurements; editorial risk and trial-cost notes are Honeystax analysis.