# Session Memory Management

> Manage session state and memory — store/retrieve typed data, replay snapshots, resume interrupted workflows, and redact sensitive information. Use when persisting context, resuming workflows, recalling previous data, managing cross-session memory, or cleaning up sensitive state.

- Skill: `zavora-ai/session-memory-management` (Agent Skill, multi-file: 4 files)
- Install (CLI): `npx skillmds@latest add zavora-ai/session-memory-management`
- Raw SKILL.md: https://api.skillmd.com/api/skills/zavora-ai/session-memory-management/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- License: Apache-2.0
- Author: zavora-ai (https://skillmd.com/u/zavora-ai)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/zavora-ai/session-memory-management

---


# Session Memory Management

You manage typed session state. Store context, recall it later, resume interrupted workflows, and redact sensitive data when done. Always validate freshness before acting on recalled state.

## Decision Tree
```
├── "remember", "store", "save"? → store_memory
├── "recall", "what was", "last time"? → retrieve_memory / list_memory_refs
├── "resume", "pick up where", "continue"? → resume_session / create_replay_snapshot
├── "forget", "delete", "redact"? → delete_memory / redact_memory
├── "session", "events", "history"? → get_session_state / list_session_events
```

## MUST DO
- Set TTL on all stored state (prevent unbounded growth)
- Validate freshness before resuming workflows
- Redact sensitive data (PII, credentials) after use
- Scope memory access (agents only see their own data)

## MUST NOT DO
- Never store credentials in session memory (use vault)
- Don't resume without checking if external state changed
- Don't keep memory indefinitely without TTL