conversation-memory

name	conversation-memory
description	Store and retrieve conversation session context for continuity across sessions (project-level). Saves completed conversations organized by datetime (hour-level granularity) to .cursor/conversations/ and enables loading previous sessions to continue context. Use when the user wants to save a conversation, load a previous session, list past conversations, or continue work from a stored session.

Conversation Memory

Store conversation sessions for later retrieval and continuation. Sessions are organized by datetime at hour-level granularity (YYYY-MM-DD-HH format).

Storage Structure

Sessions are stored in .cursor/conversations/ (project-level) with this structure:

.cursor/conversations/
├── YYYY-MM-DD-HH-session-title.md
├── YYYY-MM-DD-HH-another-session.md
└── ...

Filename format: YYYY-MM-DD-HH-<slugified-title>.md

• Datetime: YYYY-MM-DD-HH (e.g., 2026-02-09-14)
• Title: Slugified from user-provided title or auto-generated from first message

Saving a Conversation

When the user wants to save the current conversation:

1. Generate filename:

   • Extract datetime: current hour in YYYY-MM-DD-HH format
   • Extract title: user-provided title, or generate from first user message (slugify, max 50 chars)
   • Format: YYYY-MM-DD-HH-<title>.md

2. Collect conversation data:

   • Read conversation history from current session
   • Extract all user messages and assistant responses with timestamps
   • Capture workspace context (current directory, project info)
   • Generate summary of key topics and decisions