Skip to content
ExoVault

Search Documentation

Search across all documentation pages

Prompt Templates

This page provides ready-to-use system prompt snippets that configure AI agents to use ExoVault effectively. Copy these into your agent's configuration file (CLAUDE.md, .cursorrules, etc.).

Claude Code (CLAUDE.md)#

Minimal Setup#

markdown
## ExoVault Memory

This project uses ExoVault for persistent memory. The ExoVault MCP server is connected.

### Key Rules
- Search memories before writing to avoid duplicates
- Always use `dedup: true` when writing memories
- Write preferences with importance 4-5, facts with 3-4
- Include entities (technology names, project names, concepts)
- Write a context_checkpoint at session end with a session summary

Full Setup#

markdown
## ExoVault Memory

This project uses ExoVault for persistent encrypted memory. The ExoVault MCP server
is connected and provides 37+ tools for memory management, notes, tasks, and
agent-to-agent messaging.

### Memory Protocol
- **Search before write**: Always call search_memories before writing to avoid duplicates
- **Deduplication**: Set `dedup: true` on all write_memory and context_checkpoint calls
- **Entity extraction**: Extract 2-5 entities per memory (technology names, project names, concepts)
- **Summaries**: Include a `summary` field for token-efficient retrieval

### When to Write Memories
- **preference** (4-5): User states a preference ("I prefer X over Y")
- **constraint** (4-5): User sets a rule ("Never do X", "Always do Y")
- **correction** (4-5): User corrects the agent
- **fact** (3-4): Important project/environment facts
- **skill** (3-4): Learned patterns or project-specific techniques
- **task** (3-5): Action items (prefer create_task tool)

### Session Lifecycle
1. session_start loads context (called by hooks automatically, or explicitly at session start)
2. During session: search and write memories as triggers occur
3. On session end: context_checkpoint with memories[] and sessionSummary

### Anti-Patterns (Do NOT)
- Write every message as a memory
- Set all importance to 5
- Skip entity extraction
- Write memories for information already found via search
- Forget dedup:true

Cursor (.cursorrules)#

# ExoVault Memory Integration

ExoVault MCP tools are available for persistent memory across sessions.

Rules:
1. Call search_memories before write_memory to check for existing knowledge
2. Use dedup:true on all writes
3. Memory types: fact, skill, preference, constraint, task, episodic, correction
4. Importance: 1-5 (preferences/constraints=4-5, facts=3-4, episodic=2-3)
5. Always extract entities when writing memories
6. End sessions with context_checkpoint including a session summary

Memory triggers:
- User states preference → write preference (importance 4-5)
- User sets constraint → write constraint (importance 4-5)
- User corrects agent → write correction (importance 4-5)
- Important fact discovered → write fact (importance 3-4)
- Pattern/technique learned → write skill (importance 3-4)
- Task assigned → use create_task tool

Windsurf (.windsurfrules)#

# ExoVault Persistent Memory

This workspace is connected to ExoVault for cross-session memory.

## Core Protocol
- search_memories before writing (avoid duplicates)
- Always set dedup:true when writing
- Extract entities: technology names, project components, environment names
- Write session summaries at end via context_checkpoint

## Memory Types & Importance
- preference (4-5): User likes/dislikes/choices
- constraint (4-5): Rules, restrictions, mandatory practices
- correction (4-5): Fixes to previous agent errors
- fact (3-4): Objective project/environment information
- skill (3-4): Techniques, patterns, how-to knowledge
- task (3-5): Work items (use create_task for task-specific features)
- episodic (2-3): Session summaries (auto-created by context_checkpoint)

Generic MCP Agent#

For any agent that supports MCP tools:

You have access to ExoVault, an encrypted memory system. Use these tools to
remember information across conversations.

ALWAYS:
- Search memories before writing (search_memories tool)
- Use dedup:true when writing memories
- Include entities (proper nouns, tech names, concepts)
- Write a context_checkpoint at the end of each session

MEMORY TYPES (use the correct type):
- fact: Objective information (importance 3-4)
- preference: User preferences (importance 4-5)
- constraint: Rules and restrictions (importance 4-5)
- correction: When the user corrects you (importance 4-5)
- skill: Patterns and techniques (importance 3-4)
- task: Action items — prefer create_task tool

TRIGGERS TO WRITE:
- User states a preference → preference
- User sets a rule/restriction → constraint
- User corrects you → correction
- You discover project facts → fact
- You learn a technique → skill

NEVER:
- Write trivial/ephemeral information
- Skip entity extraction
- Set all importance to 5
- Write duplicates of search results

Multi-Agent Snippet#

For agents participating in multi-agent workflows:

markdown
## ExoVault Multi-Agent

You are part of a multi-agent system sharing an ExoVault vault.

### Coordination Protocol
- Check recentAgents in session_start to see who else is active
- Review changesSinceLastSession for updates from other agents
- Use send_message to communicate with other agents
- Check pending_messages for messages from other agents
- Acknowledge messages with ack_message

### Message Categories
- directive: Instructions for another agent
- question: Asking another agent for information
- info: Sharing updates
- task: Assigning work (use with create_task)
- alert: Urgent notifications (set priority 4-5)

### Shared Memory Etiquette
- Include your agent ID in entities for attribution
- Use metadata to tag memories with ownership
- Search before writing to avoid conflicting with other agents' memories