synaptic-labs-ai/pact-memory

<!-- planning-artifact-exempt-file: skill body demonstrates memory-entry shape via fictional examples that intentionally include PR/issue refs and version markers; these are example data, not real planning artifacts -->

PACT Memory Skill

Persistent memory system for PACT framework agents. Store and retrieve context, goals, lessons learned, decisions, and entities across sessions with semantic search.

Overview

The PACT Memory skill provides:

• Rich Memory Objects: Store context, goals, tasks, lessons, decisions, and entities
• Semantic Search: Find relevant memories using natural language queries
• Graph-Enhanced Retrieval: Memories linked to files are boosted when working on related files
• Session Tracking: Automatic file tracking and session context
• Cross-Session Learning: Memories persist across sessions for cumulative knowledge

Quick Start

All commands use the CLI entry point via ${CLAUDE_SKILL_DIR}:

# Save a memory
python3 "${CLAUDE_SKILL_DIR}/scripts/cli.py" save '{
  "context": "Implementing user authentication",
  "goal": "Add JWT refresh token support",
  "lessons_learned": [
    "Redis INCR is atomic - perfect for rate limiting",
    "Always validate refresh token rotation"
  ],
  "decisions": [
    {
      "decision": "Use Redis for token blacklist",
      "rationale": "Fast TTL support, distributed access"
    }
  ],
  "reasoning_chains": [
    "Redis chosen because TTL support → needed for token expiry → simpler than DB cleanup"
  ],
  "entities": [
    {"name": "AuthService", "type": "component"},
    {"name": "TokenManager", "type": "class"}
  ]
}'
# See Memory Structure table below for all available fields
# including agreements_reached and disagreements_resolved

# Search memories
python3 "${CLAUDE_SKILL_DIR}/scripts/cli.py" search "rate limiting tokens"

# Search with graph-enhanced boosting for current file
python3 "${CLAUDE_SKILL_DIR}/scripts/cli.py" search "auth tokens" --current-file src/auth/refresh.ts

# List recent memories
python3 "${CLAUDE_SKILL_DIR}/scripts/cli.py" list --limit 10

# Get a specific memory by full ID or unique prefix (>= 7 chars, case-insensitive)
python3 "${CLAUDE_SKILL_DIR}/scripts/cli.py" get <memory_id_or_prefix>

# Update an existing memory by full ID or unique prefix (scalar fields replace;
# list fields merge additively). Ambiguous prefix is refused.
python3 "${CLAUDE_SKILL_DIR}/scripts/cli.py" update <memory_id_or_prefix> '{"goal": "Updated goal"}'

# Delete a memory by full ID or unique prefix. Ambiguous prefix is refused.
python3 "${CLAUDE_SKILL_DIR}/scripts/cli.py" delete <memory_id_or_prefix>

# Check system status
python3 "${CLAUDE_SKILL_DIR}/scripts/cli.py" status

# Initialize/verify the memory system
python3 "${CLAUDE_SKILL_DIR}/scripts/cli.py" setup

All commands output JSON to stdout: {"ok": true, "result": ...}. Errors output JSON to stderr: {"ok": false, "error": "...", "message": "..."}.

For large JSON payloads (to avoid shell escaping issues), use --stdin:

echo '{"context": "...", "goal": "..."}' | python3 "${CLAUDE_SKILL_DIR}/scripts/cli.py" save --stdin

Memory Structure

Each memory can contain:

| Field | Type | Description | |-------|------|-------------| | context | string | Current working context description | | goal | string | What you're trying to achieve | | active_tasks | list | Tasks with status and priority | | lessons_learned | list | What worked or didn't work | | decisions | list | Decisions with rationale and alternatives | | entities | list | Referenced components, services, modules | | reasoning_chains | list | How key decisions connect — "X because Y, which required Z" | | agreements_reached | list | What was verified via teachback or agreement check | | disagreements_resolved | list | Where agents disagreed and how it was settled | | files | list | Associated file paths (auto-linked) | | project_id | string | Auto-detected from environment | | session_id | string | Auto-detected from environment |

Task Format

{"task": "Implement token refresh", "status": "in_progress", "priority": "high"}

Decision Format

{
    "decision": "Use Redis for caching",
    "rationale": "Fast, supports TTL natively",
    "alternatives": ["Memcached", "In-memory LRU"]
}

Entity Format

{"name": "AuthService", "type": "component", "notes": "Handles all auth flows"}

CLI Reference

Commands

| Command | Description | Output | |---------|-------------|--------| | save <json> | Save a memory object | {"memory_id": "<hex>"} | | save --stdin | Save from piped JSON | {"memory_id": "<hex>"} | | search <query> | Semantic search | [{"id": "...", "context": "...", ...}, ...] | | search <query> --limit N | Search with limit | [...] (default: 5) | | search <query> --current-file <path> | Search with graph boosting | [...] (boosts file-related memories) | | list | List recent memories | [{"id": "...", "context": "...", ...}, ...] | | list --limit N | List with limit | [...] (default: 20) | | get <id\|prefix> | Get memory by full ID or unique prefix (>= 7 chars, case-insensitive). Ambiguous prefix returns AMBIGUOUS_PREFIX with matches: [...], matches_capped, total_matches; too-short returns PREFIX_TOO_SHORT | {"id": "...", "context": "...", ...} | | update <id\|prefix> <json> | Update memory fields (list fields merge additively). Same prefix-resolution rules as get; ambiguous prefix is refused | {"memory_id": "<hex>"} | | update <id\|prefix> --stdin | Update from piped JSON | {"memory_id": "<hex>"} | | update <id\|prefix> <json> --replace | Replace list fields wholesale instead of merging | {"memory_id": "<hex>"} | | delete <id\|prefix> | Delete a memory. Same prefix-resolution rules as get; ambiguous prefix is refused | {"deleted": true, "memory_id": "<hex>"} | | status | System status | {"memory_count": N, "db_path": "...", ...} | | setup | Initialize system | {"status": "ready", "message": "..."} |

Exit Codes

| Code | Meaning | |------|---------| | 0 | Success | | 1 | User error (bad args, invalid JSON, not found) | | 2 | Validation error (unknown field name, unknown sub-object key) — the error envelope includes an allowed_fields list |

Update Semantics

update uses additive merge with content-hash dedup for list-valued fields (lessons_learned, reasoning_chains, agreements_reached, disagreements_resolved, active_tasks, decisions, entities). Scalar fields (context, goal, etc.) still replace on update.

• Passing {"lessons_learned": ["new lesson"]} appends to the existing list; duplicate items (by content hash) are silently deduplicated, so repeated saves are idempotent.
• Pass --replace when you intentionally want to remove items from a list by overwriting it wholesale.
• Unknown top-level fields (e.g. {"foo": 1}) raise ValueError with exit code 2 instead of silently disappearing. Likewise, unknown sub-object keys (e.g. {"entities": [{"description": "…"}]} — the field is notes, not description) raise ValueError.

This prevents partial-list updates from silently clobbering the entire column.

Examples

# Save a memory
python3 "${CLAUDE_SKILL_DIR}/scripts/cli.py" save '{"context": "Bug fix", "lessons_learned": ["Check null values first"]}'

# Search memories
python3 "${CLAUDE_SKILL_DIR}/scripts/cli.py" search "authentication"

# Search with file context for graph-enhanced results
python3 "${CLAUDE_SKILL_DIR}/scripts/cli.py" search "auth patterns" --current-file src/auth/service.py

# List recent memories
python3 "${CLAUDE_SKILL_DIR}/scripts/cli.py" list --limit 5

# Update an existing memory — additive list merge (default)
# This APPENDS "New lesson" to the existing lessons_learned list; any
# existing lessons are preserved. Scalar fields like "goal" still replace.
python3 "${CLAUDE_SKILL_DIR}/scripts/cli.py" update abc123 \
  '{"goal": "Updated goal", "lessons_learned": ["New lesson"]}'

# Update with wholesale list replacement (--replace)
# Use this ONLY when you intentionally want to remove items from a list.
# After this call, lessons_learned contains exactly ["Only lesson that matters"]
# and nothing else.
python3 "${CLAUDE_SKILL_DIR}/scripts/cli.py" update abc123 \
  '{"lessons_learned": ["Only lesson that matters"]}' --replace

# Delete a memory
python3 "${CLAUDE_SKILL_DIR}/scripts/cli.py" delete abc123

Search Capabilities

Semantic Search

Uses embeddings to find semantically similar memories. Requires either:

• sqlite-lembed with GGUF model (preferred)
• sentence-transformers (fallback)

Graph-Enhanced Search

When searching while working on a file, memories linked to:

• The current file
• Files imported by/importing the current file
• Files modified in the same session

...are boosted in ranking.

Keyword Fallback

If embeddings are unavailable, falls back to substring matching across context, goal, lessons_learned, and decisions fields.

Setup

Dependencies

# Required for database
pip install sqlite-vec

# For local embeddings (recommended)
pip install sqlite-lembed

# Alternative embedding backend
pip install sentence-transformers

Initialize and Check Status

# Initialize the memory system (creates directories, database schema)
python3 "${CLAUDE_SKILL_DIR}/scripts/cli.py" setup

# Check system status (memory count, capabilities, db path)
python3 "${CLAUDE_SKILL_DIR}/scripts/cli.py" status

Storage

Memories are stored in ~/.claude/pact-memory/memory.db using SQLite with:

• WAL mode for crash safety
• Vector extensions for semantic search
• Graph tables for file relationships

Command Line Usage

When invoked via /pact-memory <command> "<args>":

Save Command

python3 "${CLAUDE_SKILL_DIR}/scripts/cli.py" save '<json>'

IMPORTANT: The argument is just a hint. You MUST construct a comprehensive memory object with ALL relevant fields. Never just save the raw string. Think of each memory as a detailed journal entry that your future self (or another agent) needs to fully understand what happened, why it mattered, and what was learned.

Required fields for every save:

| Field | Minimum Length | What to Include | |-------|----------------|-----------------| | context | 3-5 sentences (paragraph) | Full background: what you were working on, why, what led to this point, relevant history, the state of things when this memory was created | | goal | 1-2 sentences | The specific objective, including success criteria if applicable | | lessons_learned | 3-5 items | Specific, actionable insights with enough detail to be useful months later. Each lesson should explain the "why" not just the "what" |

Recommended fields:

• decisions: Key decisions made with full rationale, alternatives considered, and why they were rejected
• entities: Components, files, services, APIs involved (enables graph-based retrieval)

Writing comprehensive context:

BAD (too sparse):

"Debugging auth bug"

STILL BAD (single sentence):

"Debugging authentication failure in the login flow where users were getting 401 errors."

GOOD (comprehensive):

"Working on the fix/auth-refresh branch to resolve issue #234 where users reported intermittent 401 errors after being logged in for extended periods. The bug was reported by 3 enterprise customers last week and is blocking the v2.1 release. Initial investigation pointed to the token refresh mechanism, specifically a race condition between concurrent API requests. The authentication system uses JWT tokens with 15-minute expiry and a refresh token rotation pattern. This session focused on reproducing the bug locally by simulating high-latency conditions."

Example transformation:

# Agent is asked to save "figured out the auth bug"

# Construct the full memory object and save:
{
    "context": "Working on the fix/auth-refresh branch to resolve issue #234 where users reported intermittent 401 errors after being logged in for extended periods. The bug was reported by 3 enterprise customers last week and is blocking the v2.1 release. Initial investigation pointed to the token refresh mechanism, specifically a race condition between concurrent API requests. The authentication system uses JWT tokens with 15-minute expiry and a refresh token rotation pattern. This session focused on reproducing the bug locally by simulating high-latency conditions and tracing through the token refresh flow.",
    "goal": "Identify and fix the root cause of intermittent authentication failures that occur after extended user sessions, ensuring the fix doesn't introduce performance regressions.",
    "lessons_learned": [
        "The token refresh mechanism had a race condition: when multiple API requests detected an expired token simultaneously, each would trigger its own refresh, causing token rotation conflicts where subsequent requests used invalidated tokens",
        "Adding a mutex/lock around the token refresh operation prevents concurrent refresh attempts - the first request refreshes while others wait and then use the new token",
        "The bug only manifests under high latency conditions (>500ms API response time) because faster responses complete before the token expiry window, making it hard to reproduce in development",
        "Our existing retry logic actually made the problem worse by immediately retrying with the same stale token instead of waiting for the refresh to complete",
        "Integration tests should include latency simulation to catch timing-dependent bugs like this"
    ],
    "decisions": [
        {
            "decision": "Use mutex pattern for token refresh instead of request queuing",
            "rationale": "Simpler implementation with less state to manage. A mutex ensures only one refresh happens at a time while other requests wait. Our concurrency level (typically <10 concurrent requests) doesn't warrant the complexity of a full request queue.",
            "alternatives": ["Request queue with single refresh - more complex, better for high concurrency", "Optimistic token prefetch - would require predicting refresh timing", "Retry with backoff - doesn't solve the root cause, just masks it"]
        }
    ],
    "entities": [
        {"name": "AuthService", "type": "service", "notes": "Central authentication service handling login, logout, and token management"},
        {"name": "TokenManager", "type": "class", "notes": "Manages JWT token lifecycle including refresh logic"},
        {"name": "src/auth/refresh.ts", "type": "file", "notes": "Contains the token refresh implementation where the bug was fixed"}
    ]
}

Search Command

python3 "${CLAUDE_SKILL_DIR}/scripts/cli.py" search "<query>"

Returns semantically similar memories. Use natural language queries.

List Command

python3 "${CLAUDE_SKILL_DIR}/scripts/cli.py" list --limit 10

Shows recent memories (default: 20).

Best Practices

1. Save at Phase Completion: Save memories after completing PACT phases
2. Include Lessons: Always capture what worked and what didn't
3. Document Decisions: Record rationale and alternatives considered
4. Link Entities: Reference components for better graph connectivity
5. Search Before Acting: Check for relevant past context before starting work
6. Write Complete Sentences: Context should be a full description, not a fragment
7. Be Specific in Lessons: "X didn't work because Y" is better than "X didn't work"
8. Check Save Results: The save command verifies persistence by reading back the saved memory. If verification fails (exit code 2, error type SYSTEM_ERROR), the save silently failed — retry or check system status

Memory Layers: pact-memory vs Auto-Memory

The PACT framework operates with multiple memory layers. Understanding their distinct roles prevents duplication and ensures the right tool is used for the right purpose.

| Layer | Storage | Content | Who Writes | Auto-Loaded | |-------|---------|---------|------------|-------------| | Auto-memory (MEMORY.md) | ~/.claude/projects/{hash}/memory/ | Free-form session learnings, user preferences, general patterns | Platform (automatic) | Yes (first 200 lines) | | pact-memory (SQLite) | ~/.claude/pact-memory/memory.db | Structured institutional knowledge: context, goals, decisions, lessons, entities | Agents via this skill | Via Working Memory sync to CLAUDE.md | | Agent persistent memory | ~/.claude/agent-memory/<name>/ | Per-agent domain expertise accumulated across sessions | Individual agents (automatic) | Yes (first 200 lines, per agent) |

pact-memory's unique value: Structured fields (context, goal, decisions, lessons_learned, entities) enable semantic search, graph-enhanced retrieval, and cross-agent knowledge sharing -- capabilities that auto-memory's free-form markdown does not provide.

Coexistence model: Auto-memory captures broad session context automatically. pact-memory captures deliberate, structured knowledge at PACT phase boundaries. The Working Memory section in CLAUDE.md shows the 3 most recent pact-memory entries, providing structured context that complements auto-memory's general learnings.

Integration with PACT

The memory skill integrates with PACT phases:

• Prepare: Search for relevant past context before starting
• Architect: Record design decisions with rationale
• Code: Save lessons learned during implementation
• Test: Document test strategies and findings

See references/memory-patterns.md for detailed usage patterns.