name: clankie-memory description: A persistent memory for your personal agent
Memory
You have persistent memory stored as Markdown files in the workspace. This memory persists across sessions and allows you to recall facts, preferences, decisions, and context from previous conversations.
By default, semantic search uses a local embedding model (Transformers.js) so no API key is required. The first embedding call in a session may be slower while the model is loaded/downloaded and cached.
Memory Structure
MEMORY.md- Long-term memory for durable facts, preferences, and decisionsmemory/YYYY-MM-DD.md- Daily notes for each day's context and running notes
Tools
memory_search
Semantic search over all memory. Use this before making assumptions about:
- User preferences or habits
- Previous decisions or agreements
- Past context that might be relevant
- Facts the user has told you before
When to search:
- Before answering questions about past context
- When the user references something "you should know"
- At the start of complex tasks (check for relevant past decisions)
- When you're unsure about user preferences
memory_write
Write to memory.
type="daily" - Use for:
- Running notes about today's work
- Temporary context that might be useful later today
- Summaries of what was accomplished
type="longterm" - Use for:
- User explicitly says "remember this"
- Decisions, preferences, facts that should persist
- Important context that applies across sessions
Guidelines
When to write to memory
Always write (type="longterm") when:
- User says "remember this", "don't forget", "make a note"
- A decision is made that affects future work
- You learn a user preference (coding style, tools they prefer, etc.)
- Important facts about the project or codebase are discussed
Write (type="daily") when:
- Tracking progress on a multi-step task
- Noting context that might be needed later today
- Summarizing what was discussed or done
When to search memory
Always search before:
- Answering "what did we decide about..." questions
- Making assumptions about user preferences
- Starting work on a task that might have prior context
- The user references something from a previous session
Memory etiquette
- Be selective - don't store trivial information
- Write clearly - future you (and the user) will read this
- Include context - a note without context may not make sense later
- Search first - don't assume you remember correctly, verify
- Update when things change - if a decision is reversed, note it