pūrmemo

Showing 25 of 28 from the live probe.

• Save Conversation

  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)

• Save Artifact

  Save a single artifact (research report, table, framework, spec, code) linked to a conversation memory. WHEN TO USE: After calling save_conversation for a session that produced artifacts. Call this ONCE PER ARTIFACT with the full verbatim content — do NOT summarize or truncate. WHY: Artifacts are the highest-value output of research sessions. Saving them separately ensures complete preservation. Each artifact becomes a first-class searchable object linked to its parent conversation. FLOW: 1.

• Commit

  Persist a commitment-shaped artifact (PRD, ADR, spec, OKR) as a memory with intent='commitment'. WHEN TO USE: This is the write primitive for /prd, /decide, /spec, /commit slash commands. Call after the artifact is fully drafted in the conversation. Send the COMPLETE artifact verbatim — do NOT summarize. INSERT-only. Each call creates a new memory; supersede prior versions by recency, never overwrite. No conversationId parameter (intentional — see ADR-034). QUERYABLE: GET /api/v1/commitments/

• Snapshot

  Generate a state-shaped artifact for a topic from your saved memories. WHEN TO USE: When you want a current-state document derived from saved conversations — architecture map, glossary, runbook, manifesto, project state. The slash command /snapshot calls this. HOW IT WORKS: 1. Queries memories matching the topic (fuzzy match against tags + title), recency-weighted. 2. Builds a draft snapshot via the deterministic baseline generator (concatenates source memories — Phase 1 baseline; Gemini integ

• Snapshot Sources

  Fetch citation bundle + conflict detection for a topic so YOU can synthesize the snapshot in-context. Step 1 of the MCP snapshot path (ADR-032 Amendment A). WHEN TO USE: When you want to generate a snapshot from inside Claude. Returns source memories + conflicts so you synthesize, then call save_snapshot() to persist. FLOW: 1. snapshot_sources(topic) → sources returned to you 2. You synthesize a current-state document from the sources 3. save_snapshot(topic, content, cited_ids) → persists your

• Save Snapshot

  Persist your synthesized snapshot content as a draft. Step 3 of the MCP snapshot path (ADR-032 Amendment A). Call this after synthesizing from snapshot_sources(). Backend derives evidence_tier from cited_ids — not caller-controlled. Runs claim verification on your content.

• Get Snapshot

  Read an existing canonical snapshot into context. Fast — no LLM calls. WHEN TO USE: When you need the current canonical state document for a topic (e.g. architecture, auth, glossary) without generating a new one.

• Accept Snapshot

  Promote a draft snapshot to canonical. Supersedes the prior canonical for this topic. If gate blockers exist (conflicts detected, tier downgrade, or first canonical), returns them for review. Pass force: true to approve and promote anyway.

• Recall Memories

  Search and retrieve saved memories with intelligent semantic ranking. 🎯 BASIC SEARCH: recall_memories(query="authentication") → Returns all memories about authentication, ranked by semantic relevance 🔍 FILTERED SEARCH (Phase 2 Knowledge Graph Intelligence): Use filters when you need PRECISION over semantic similarity: ✓ entity="name" - Find memories mentioning specific people/projects/technologies Example: entity="purmemo" → Only memories discussing purmemo ✓ has_observations=t

• List Clusters

  Browse the memory map. With NO arguments, returns the user's PROJECT -> THEME hierarchy with member counts (the "galaxy" as text) — use this to show "what projects/topics do I have?". With cluster="<title or UUID>", OPENS that cluster and lists its member memories (a project title pulls every memory across all its themes; a theme title pulls that theme). Pair with recall_memories(cluster=...) to then semantically search inside a cluster. Read-only.

• Get Memory Details

  Get complete details of a specific memory, including all linked parts if chunked

• Discover Related Conversations

  CROSS-PLATFORM DISCOVERY: Find related conversations across ALL AI platforms. Uses Purmemo's semantic clustering to automatically discover conversations about similar topics, regardless of which AI platform was used (ChatGPT, Claude Desktop, Gemini, etc). WHAT THIS DOES: - Searches for memories matching your query - Uses AI-organized semantic clusters to find related conversations - Groups results by topic cluster with platform indicators - Shows conversations you m

• Get User Context

  Get the current user's cognitive identity and active session context. Call this at the START of a conversation to understand who you're talking to — their role, expertise, current project, and recent memory themes. This is the core of Purmemo's identity layer: once set in the dashboard, your identity travels silently to every AI session so you're never explaining yourself from scratch again. WHAT IT RETURNS: - identity: role, expertise areas, primary domain, work style, preferred tools - curr

• Run Workflow

  Run a Purmemo workflow — structured, memory-powered processes for product, engineering, business, and operations tasks. Your relevant memories and identity are automatically loaded to personalize every workflow. WHEN TO USE THIS TOOL: - User wants to write a PRD, debug an issue, plan a sprint, review code, or any structured task - User describes a goal but doesn't know the exact process ("I want to ship a feature") - User asks for strategic advice, design guidance, or operational help - User sa

• List Workflows

  List all available Purmemo workflows — structured, memory-powered processes you can run. WHEN TO USE THIS TOOL: - User asks "what can you help me with?" or "what workflows do you have?" - User wants to see available capabilities before choosing one - User says "show me what's available" or "list workflows" Returns the full catalog of workflows organized by category with descriptions.

• Share Memory

  Set the visibility of a memory you own. VISIBILITY LEVELS: - private: Only you can see it (default) - unlisted: Anyone with the direct link can view it - public: Discoverable in the community tab by all users WHEN TO USE: - User says "share this memory" or "make this public" - User wants to share knowledge with the community - User wants to generate a shareable link QUOTA: - Free tier: 5 shares/month - Pro/Teams: Unlimited EXAMPLE: share_memory({ memory_id: "abc-123", visibility: "public" })

• Recall Public

  Search public memories shared by all Purmemo users. This is the community knowledge base. WHEN TO USE: - User asks "what have other people saved about X?" - User wants to explore community knowledge - User asks to search public/shared memories - Looking for solutions others have found DOES NOT COUNT AGAINST RECALL QUOTA — public knowledge is free. FILTERS: - query: Semantic search query (uses vector similarity) - tag: Filter by tag - platform: Filter by source platform - sort: "recent" or "po

• Get Public Memory

  Retrieve the FULL content of a public or unlisted memory by ID. WHEN TO USE: - After recall_public returns a preview and you need the complete content - When a user wants to read or implement from a shared community memory - When you have a public memory ID and need the full text This is the tool that closes the loop: recall_public finds memories, this tool retrieves them in full. No authentication required — public knowledge is free. EXAMPLE: get_public_memory({ memory_id: "abc-123-def-456"

• Report Memory

  Report a public memory for inappropriate content. WHEN TO USE: - User encounters spam, misleading, or inappropriate public content - User wants to flag content that contains personal information REASONS: spam, inappropriate, misleading, personal_info, other After 3 reports, a memory is automatically hidden from public view pending admin review. EXAMPLE: report_memory({ memory_id: "abc-123", reason: "spam", description: "Promotional content" })

• Get Acknowledged Errors

  Fetch open and acknowledged errors waiting for AI investigation. Returns errors with status 'open' or 'acknowledged' — all errors needing attention. Each error includes recent_occurrences[] with per-request context (user_id, path, method) for investigation. USAGE: - Call this when user says "investigate errors" or "/investigate-errors" - Errors are sorted by occurrence count (most frequent first) - Each result includes recent_occurrences[] for per-request investigat

• Save Investigation Result

  Save AI investigation results for an error incident. Used to store investigation results for audit trail and learning from past fixes. Call this after investigating an error and proposing/deploying a fix. USAGE: - Call after completing investigation and deploying fix - Stores root cause analysis, research sources, proposed changes - Creates audit trail for learning from past investigations REQUEST FIELDS: - incident_id: UUID of the error incident (from get_ackn

• Generate Handoff Brief

  Generate a surgical context brief for a new AI session. Instead of re-explaining your context, the AI already knows where you left off. Uses a 5-layer compaction hierarchy to maximize signal in ~2,000 tokens: 1. Intent — What you were trying to accomplish (never cut) 2. Decisions — What was decided and completed 3. Open Loops — Blockers, unresolved items, active todos 4. Context — Technologies, entities, project details 5. Content — Brief excerpts (trimmed to fit budget) Call this at the start

• Save Test Result

  Save a test result memory for a project, linked to the current active task. Call this after running tests — pass or fail — to record the outcome. Saves a memory with category='test_result' and links it to the most recent active task. Re-running with the same test_suite name updates the existing memory (living document). USAGE: - After a passing test run: save_test_result({ project_name, passed: true, test_suite }) - After a failing run: save_test_result({ ..., passed: false, failure_details: "

• Get Test Results

  List recent test results for a project, newest first. Pairs with save_test_result — use this to recall past test outcomes without having to query the conversational memory layer. USAGE: - Latest 50 results: get_test_results({ project_name: "polymathematics" }) - Only failures: get_test_results({ project_name, passed: false }) - Custom limit: get_test_results({ project_name, limit: 10 }) RETURNS: - results[] — each with id, test_suite, passed, failure_details, updated_at

• Get Artifacts

  List artifacts linked to a parent conversation. Pairs with save_artifact.