Session Memory Protocol gives your AI collaborator persistent memory across conversations inside 📝Augmentation, using your daily memo instead of a CLAUDE.md file you maintain by hand. It exists because context-window compression drops instructions, switching clients loses the thread, and a file nobody's forced to update goes stale — a protocol beats a convention. It's for anyone who currently maintains session-logging instructions manually and wants that discipline handled automatically instead.
Key Capabilities
- One prompt, full protocol — invoking
session_memoryreads today's daily memo so your AI knows what happened earlier and what's pending - Live logging — decisions and milestones land in the daily memo's Timeline via
add_daily_entry; new action items become tasks viaadd_daily_task - Session-end handoff — a closing summary is logged, unfinished work becomes tomorrow's tasks, and durable learnings get saved to your Mythos Memory augmentation memo
- Cross-client — works identically on claude.ai, Claude mobile, Claude Code, Claude Desktop, Cursor, and Windsurf
- Permission-aware — daily memos stay private by default, separate from your public memo library
Getting Started
- Connect 📝MythOS MCP to your client — OAuth on claude.ai/mobile, or an API key for Claude Code/Desktop/Cursor/Windsurf
- Start a session and say "use the session_memory prompt for today's date"
- Work normally — your AI logs as it goes
FAQ
- Does this replace my augmentation context? No — your Soul/Style/Human/Memory context loads separately, through the required 📝Implicit Loading gate; session_memory specifically adds the daily-memo continuity layer on top.
- What's wrong with a CLAUDE.md file? Nothing, until it drifts — manual instructions get dropped by context compression, don't follow you across clients, and require discipline to keep current. This protocol is built into MCP instead of relying on a maintained file.
- Do I need a paid plan? Generating an API key for Claude Code, Desktop, Cursor, or Windsurf requires Scholar or Oracle; the OAuth connector path on claude.ai/mobile has no separate tier requirement documented here.
- What gets logged versus what gets forgotten? Everything goes to today's Timeline; only what you or your AI judge durable gets promoted into Mythos Memory, so tomorrow's context doesn't bloat with yesterday's noise.
Related
- 📝Augmentation System — the Mythos Memory memo this protocol feeds