persistent-memory
Skill0 starsChanged 4 months agoMITView on GitHub
Native local-first persistent memory for agentloop. Extract, store, supersede, contradict, and retrieve durable knowledge via .agentloop/memory and scripts/memory.sh. Use across sessions; integrate with handoff and context-surgeon. Cloud sync is reserved for later — do not call external memory APIs.
8 other projects use a version of this.
Adopted by
Most recently taken up by
- yantrikos/yantrikdb-mcptheir own version, first seen Nov 2, 2026
- mthines/agent-skillstheir own version, first seen Oct 30, 2026
- songjiun10-collab/Senior-thinking-skillstheir own version, first seen Oct 12, 2026
- aws-solutions/konductortheir own version, first seen Sep 23, 2026
- dbozic/claude-skillstheir own version, first seen Sep 18, 2026
- rainypilgrimage/persistent-memorytheir own version, first seen Aug 2, 2026
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- songjiun10-collab/Senior-thinking-skills★ 87same name
- yantrikos/yantrikdb-mcp★ 24same name
- mthines/agent-skills★ 20same name
- aws-solutions/konductor★ 11same name
- rainypilgrimage/persistent-memory★ 4same name
- NullLabTests/agentkit★ 2same name
- whaojie797-design/Novera-AI-skills★ 2same name
- dbozic/claude-skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository138 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/context-budget.mdcCursor rule
- .cursor/rules/delegation-law.mdcCursor rule
- .cursor/rules/harness-doctrine.mdcCursor rule
- .cursor/rules/verification-law.mdcCursor rule
- agent-interface-designSkill
- agentloop-coreSkill
- agent-loopSkill
- blindspot-passSkill
- brainstorm-prototypesSkill
- change-quizSkill
- conductor-planSkill
- context-auditSkill
- context-compactSkill
- context-surgeonSkill
- contrastingSkill
- deployment-auditSkill
- doctorSkill
- harness-designSkill
- humaniseSkill
- implementation-notesSkill
- implementation-planSkill
- interview-meSkill
- no-ai-slopSkill
- optional-ponytailSkill
- opus-promptingSkill
- pev-cycleSkill
- pitch-packagerSkill
- progressive-disclosureSkill
- quality-composeSkill
- reference-huntSkill
- seo-copywritingSkill
- ship-gateSkill
- subagent-swarmSkill
- ui-ux-auditSkill
- warroom-councilSkill
- writer-verifierSkill
- agent-interface-designSkill
- agentloop-coreSkill
- agent-loopSkill
- blindspot-passSkill
- brainstorm-prototypesSkill
- change-quizSkill
- conductor-planSkill
- context-auditSkill
- context-compactSkill
- context-surgeonSkill
- contrastingSkill
- deployment-auditSkill
- doctorSkill
- harness-designSkill
- humaniseSkill
- implementation-notesSkill
- implementation-planSkill
- interview-meSkill
- no-ai-slopSkill
- optional-ponytailSkill
- opus-promptingSkill
- persistent-memorySkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 48
Do not store: transcripts, secrets, ephemeral debug, green-CI fantasies.
- Distinctive: line 66
When knowledge changes, do not silently edit history.
- Distinctive: line 80
When two active memories conflict and both must remain visible:
- Distinctive: line 101
Prefer memory keys + DIGEST over chat archaeology
- Distinctive: line 103
Never drop current failing gate logs into memory as “facts”
“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Persistent Memory (native, local-first)
Session handoffs (.agentloop/handoff.md) are short-term continuity..agentloop/memory/ is durable knowledge that survives new chats.
Inspired by Supermemory’s extract → store → update → retrieve loop — implemented fully offline with files + scripts/memory.sh.
Store layout
.agentloop/memory/
index.json
DIGEST.md
entries/<key>.mdInit if missing: scripts/memory.sh init
Loop (do this explicitly)
1. Retrieve (session start / before plan)
scripts/memory.sh session-brief
# or
scripts/memory.sh session-brief "keyword"
scripts/memory.sh search "keyword"
scripts/memory.sh get some.keyCite what you loaded in one short block. Honor constraint and preference entries.
2. Extract (what is worth remembering?)
Store only if it should survive a cold start:
- Architectural decision
- User preference / constraint (“never X”, “always Y”)
- Stable system map
- Lesson from a failed approach
- Durable fact about this repo
Do not store: transcripts, secrets, ephemeral debug, green-CI fantasies.
3. Store / upsert
scripts/memory.sh upsert \
--key conductor.plan-gate \
--kind decision \
--title "Conductor approval gate" \
--summary "Multi-step work requires /plan approval before Execute." \
--tags harness,plan \
--pointers skills/conductor-plan/SKILL.md,commands/plan.mdKinds: decision | preference | constraint | map | lesson | fact
4. Update / supersede
When knowledge changes, do not silently edit history. Supersede:
scripts/memory.sh supersede old.key \
--key new.key \
--kind decision \
--summary "New truth..." \
--tags harnessOld entry → status: superseded + superseded_by. New entry → active + supersedes.
5. Contradictions
When two active memories conflict and both must remain visible:
scripts/memory.sh contradict a.key --with b.key --note "why they conflict"Both become contradicted and cross-link. Resolve later by superseding one or both with a unifying decision.
6. Handoff integration
On every meaningful run end / slice boundary:
- Refresh
.agentloop/handoff.md - Upsert durable facts discovered this run
- Set
memory_keys: [keys...]on the handoff scripts/memory.sh digest
7. Context-surgeon integration
When compacting:
- Prefer memory keys + DIGEST over chat archaeology
- Promote durable conclusions with upsert/supersede before dropping chat detail
- Never drop current failing gate logs into memory as “facts”
Cloud (future only)
Entries include cloud_sync: local_only. Do not integrate Supermemory or other cloud APIs now. A future adapter may flip pending → synced.
Agent checklist
session-briefat cold start- Upsert after durable decisions
- Supersede on knowledge updates
- List
memory_keyson handoff - No secrets in entries
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

