save_conversation
Persist complete conversation transcripts as searchable memory, auto-extracting project context, titles, and status while routing updates to a single memory per topic.
Instructions
Save complete conversations as memory. REQUIRED: Send COMPLETE conversation in 'conversationContent' parameter (minimum 100 chars, should be thousands). Include EVERY message verbatim - NO summaries or partial content.
Intelligently tracks context, extracts project details, and routes to a single memory per conversation topic.
HOW SAVES TARGET MEMORIES:
- conversationId is auto-generated from title slug (e.g., "MCP Tools" → "mcp-tools")
- Same title (or explicit conversationId) → targets the existing memory
- The 'mode' parameter controls what happens to that existing memory:
• mode='replace' (default): overwrites the existing content with what you send
• mode='append': concatenates new content below existing with a timestamped separator
(\n\n--- UPDATE <ISO8601> ---\n\n) — preserves all prior history in the live row
- The /save skill sets mode='append' automatically for living-document use
- For one-shot snapshots, ad-hoc captures, or explicit overwrite: pass mode='replace'
PRIOR CONTENT IS NEVER LOST:
- Even with mode='replace', prior content is snapshotted to memory_events audit log on every update
- Recovery from overwrites requires a one-off script (out-of-band)
- Use mode='append' if you want history to remain visible inline in the live memory
INTELLIGENT EXTRACTION (independent of mode):
- Auto-extracts project context (name, component, feature being discussed)
- Detects work iteration and status (planning/in_progress/completed/blocked)
- Generates smart titles like "Purmemo - Timeline View - Implementation"
- Tracks technologies, tools used, identifies relationships/dependencies
SERVER AUTO-CHUNKING:
- Large conversations (>15K chars) automatically split into linked chunks
- Small conversations (<15K chars) saved directly as single memory
- You always send complete content — server handles chunking
- APPEND + CHUNKING: append mode works only for content <15K chars. Saves >15K
with mode='append' are rejected with a clear error — appending to chunked
storage would double each chunk's content on re-save. For long-running living
docs, send only the new delta since the last save (keep it <15K) or use
mode='replace' for full re-saves.
- KNOWN CAVEAT: a doc that is saved small (single memory) and later grows past 15K
transitions to chunked storage at a new conversation_id space — the original
single memory becomes orphaned. Tracked under ADR-038 (uniform namespace).
EXAMPLES:
User: "Save progress" via /save skill
→ /save sets mode='append'; new content is appended below prior content
User: "Save this snapshot" (one-shot capture)
→ mode='replace' default; current content overwrites any existing memory at this title
User: "Save as conversation react-hooks-guide" with explicit append
→ save_conversation(conversationId="react-hooks-guide", mode="append")
→ Appends to existing memory at that ID (or creates if new)
WHAT TO INCLUDE (COMPLETE CONVERSATION REQUIRED):
- EVERY user message (verbatim, not paraphrased)
- EVERY assistant response (complete, not summarized)
- ALL code blocks with full syntax
- ALL artifacts with complete content (not just titles/descriptions)
- ALL file paths, URLs, and references mentioned
- ALL system messages and tool outputs
- EXACT conversation flow and context
- Minimum 500 characters expected - should be THOUSANDS of characters
FORMAT REQUIRED:
=== CONVERSATION START ===
[timestamp] USER: [complete user message 1]
[timestamp] ASSISTANT: [complete assistant response 1]
[timestamp] USER: [complete user message 2]
[timestamp] ASSISTANT: [complete assistant response 2]
... [continue for ALL exchanges]
=== ARTIFACTS ===
[Include ALL artifacts with full content]
=== CODE BLOCKS ===
[Include ALL code with syntax highlighting]
=== END ===
IMPORTANT: Do NOT send just "save this conversation" or summaries. If you send less than 500 chars, you're doing it wrong. Include the COMPLETE conversation with all details.
ARTIFACT PRESERVATION (ADR-025):
If this conversation produced artifacts (research reports, tables, frameworks, specs, design documents),
save them SEPARATELY using save_artifact after this call.
Flow: save_conversation first, then save_artifact for each artifact.
This ensures artifacts are preserved in full — do not try to embed large artifacts in conversationContent.Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| mode | No | How to handle a save that targets an existing memory (same title or conversationId). "replace" (default) overwrites the existing content with what you send. "append" concatenates new content below the existing content with a timestamped separator (\n\n--- UPDATE <ISO8601> ---\n\n). Use "append" for living documents you genuinely want to grow over time; use "replace" for one-shot snapshots and ad-hoc captures. The /save skill defaults to "append" automatically — you only need to pass this for explicit overrides. | replace |
| tags | No | Tags for categorization | |
| title | No | Title for this conversation memory | Conversation 2026-08-03T19:20:47.417Z |
| priority | No | Priority level for this memory | medium |
| conversationId | No | Optional unique identifier for living document pattern. If provided and memory exists with this conversationId, UPDATES that memory instead of creating new one. Use for maintaining single memory per conversation that updates over time. | |
| conversationContent | Yes | COMPLETE conversation transcript - minimum 500 characters expected. Include EVERYTHING discussed. |