Overview
Thememory sessions command lists recent session files stored in the vault. Session files are markdown documents that capture agent interactions and can be automatically generated by integrations.
Syntax
Options
Maximum number of sessions to show.
Filter by project name.
Examples
List recent sessions
Show more sessions
Filter by project
Show all sessions for a project
Session Files
File naming
Session files follow this pattern:2026-03-03-session.md
Location
Stored in the vault under project directories:Content
Session files typically contain:- Timestamp and agent info
- Conversation history
- Commands run
- Files modified
- Decisions made
- TODOs and follow-ups
Use Cases
Review recent work
Check what was done in recent sessions:Find sessions by project
When switching contexts:Audit trail
Review all activity over time:Extract learnings
Mine session files for memories to save:Viewing Session Content
Direct file access
With pagination
Search within sessions
Session Creation
Session files are typically created by:- Agent integrations: Cursor, Claude Code, Codex hooks
- MCP server: EchoVault MCP automatically logs sessions
- Manual creation: You can create them yourself
Manual session file
Create a session file manually:Output Format
The command outputs a simple table:- Date: YYYY-MM-DD format
- Project: Project directory name
- Sorted by date (most recent first)
When No Sessions Found
- No
*-session.mdfiles exist in the vault - Or the project filter didn’t match any sessions
Related Commands
memory save- Save memories from session notesmemory search- Find specific memoriesmemory context- Get memory context for new sessions
Session files are separate from memories. They’re raw logs, while memories are structured, searchable records. Use sessions for historical review and extract key points into memories.