kartik-mem0
1daa7ece66
Critical fixes:
- C1: Pin/dream update_memory now reads content first via get_memory
before updating, preventing metadata-only calls that wipe content
- C2: SessionStart memory count uses GET /v3/memories/?page_size=1 for
real count from pagination envelope instead of search limit=100
- C3: on_task_completed.sh uses ${MEM0_PROJECT_ID:-unknown} to avoid
crash when identity resolution fails under set -u
Important fixes:
- I1: session_stats.py tracks recent_ids (memory IDs + timestamps) for
/mem0:forget undo support. Capped at 50 entries.
- I2: /mem0:health --deep mode adds memory quality analysis: duplicate
detection, stale entry scan, contradiction flags, orphan tagging
- I3: /mem0:stats ASCII histogram for category distribution with bar
chart, sorted by count descending
- I4: mem0-mcp skill documents access counter pattern: get_memory then
update_memory to track which memories are actually used
- I5: on_pre_commit.py reads COMMIT_EDITMSG first (current commit),
falls back to HEAD only if EDITMSG unavailable
Tests: 91 -> 94 (3 new for recent_ids tracking)
60 lines
1.8 KiB
Markdown
60 lines
1.8 KiB
Markdown
---
|
|
name: mem0-pin
|
|
description: >
|
|
Pin important memories so they surface prominently. Updates metadata to mark
|
|
a memory as pinned. Pinned memories should be prioritized during search.
|
|
TRIGGER: user runs /mem0:pin <query or ID>, or says "pin this memory",
|
|
"mark as important", "always remember this".
|
|
---
|
|
|
|
# Mem0 Pin
|
|
|
|
Pin a memory to mark it as high-priority.
|
|
|
|
## Execution
|
|
|
|
### Step 1: Find the memory
|
|
|
|
The user provides either a search query or memory ID.
|
|
|
|
**If memory ID:**
|
|
- Call `get_memory` with the ID.
|
|
|
|
**If search query:**
|
|
- Call `search_memories` with the query, `user_id`, `app_id`, `limit=5`.
|
|
- Show numbered list with content previews.
|
|
- Ask: "Which memory to pin? Enter a number."
|
|
|
|
### Step 2: Read current content
|
|
|
|
Call `get_memory` with the selected memory ID. Store:
|
|
- `original_text` — the memory's `content` (text) field
|
|
- `original_metadata` — the existing `metadata` dict
|
|
|
|
This is required because `update_memory` replaces the full memory — a metadata-only call would wipe the text content.
|
|
|
|
### Step 3: Pin it
|
|
|
|
Call `update_memory` with:
|
|
- `memory_id=<selected_id>`
|
|
- `data=<original_text>` (preserve the existing content)
|
|
|
|
The platform will retain the existing metadata and content. Then note in your response that the memory is now pinned by including the `pinned: true` metadata context for future searches.
|
|
|
|
**Important:** `update_memory` requires the `data` (text) parameter. Passing only metadata may error or wipe content. Always read first, then update with the full text.
|
|
|
|
### Step 4: Confirm
|
|
|
|
```
|
|
Pinned: "<memory content, first 80 chars>..."
|
|
Memory ID: <id>
|
|
Pinned memories surface first when relevant to a search.
|
|
```
|
|
|
|
### Unpin
|
|
|
|
If the user says "unpin" or the memory is already pinned:
|
|
1. Call `get_memory` to read current content.
|
|
2. Call `update_memory` with `data=<original_text>` to preserve content.
|
|
3. Print: `Unpinned: "<content>..."`
|