Memanchor — Development skill for Claude Code

⚓ memanchor

[](https://github.com/AfridaMehanaz/memanchor/actions/workflows/ci.yml)

**Persistent memory for coding agents that knows when it's out of date.**

Claude Code, Cursor and Codex forget everything between sessions. memanchor is a local [MCP](https://modelcontextprotocol.io) server that lets them save what they learn (decisions, conventions, gotchas) and recall it next time.

The difference: every memory is **anchored to the files it describes**. When those files change, recall flags the memory as **STALE**, so the agent re-checks before acting on outdated knowledge.

> recall "jwt signing"

1 memory, 1 stale (verify before relying on them)

#4 [decision] (STALE: src/auth/keys.ts changed; tags: auth, jwt)
JWTs are signed with RS256 so other services can verify them with the public key only.

Why

A wrong memory is worse than no memory. Most agent-memory tools store text and return it forever, even after the code it describes has been rewritten. memanchor treats memory like a cache that can be invalidated:

	Plain notes / CLAUDE.md	Typical memory server	memanchor
Persists across sessions	✅	✅	✅
Searchable	grep	✅	✅ BM25 + stemming
Knows when a memory may be outdated	❌	❌	✅ file anchors
Scrubs secrets before saving	❌	rarely	✅
Bounded context cost	❌ whole file	varies	✅ token budget
Local, no cloud, no API key	✅	varies	✅

Features

• Staleness detection. remember(files: [...]) stores a content hash of each file. recall re-hashes and marks memories whose files changed or were deleted. confirm_memory re-anchors after the agent re-checks. list_memories(stale_only) finds memories to clean up.
• Secret redaction. API keys (Anthropic, OpenAI, GitHub, AWS, Slack, Stripe, Google), JWTs, private keys, password= style assignments and credentials in connection s