total-recall

Preserve Claude Code session context across resets and compactions.

Updated Nov 22, 2025
One-click install
npx skills add https://github.com/plinde/total-recall --skill total-recall
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: total-recall
Source: https://github.com/plinde/total-recall/tree/main/.
Command: npx skills add https://github.com/plinde/total-recall --skill total-recall

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This Skill solves the critical problem of losing context in long or complex Claude Code sessions. When you hit token limits, need to /reset or /compact, or switch between tasks, Claude's memory can fade, forcing you to waste time re-establishing your work state. Total Recall ensures your session's "memory" is preserved, so you can pick up exactly where you left off.

Core Features & Use Cases

  • Comprehensive Context Capture: Automatically creates a detailed "memory dump" of your current work state, key decisions, generated files (with paths), next steps, and important technical notes.
  • Seamless Session Resumption: Easily restore your session's context after a /reset or /compact, or when returning to a project, eliminating the need to manually re-explain everything to Claude.
  • Use Case: Imagine you're deep into a complex AWS infrastructure project with Claude, generating multiple Terraform files and making critical design decisions. Before you hit the token limit and need to /compact, invoke total-recall. Your entire session's state is saved. Later, after clearing your session, simply instruct Claude to read the saved dump, and it's instantly up to speed, ready to continue.

Quick Start

To save your current session's context:

/total-recall

This will create a comprehensive memory dump at /tmp/total-recall. To restore your session later, simply instruct Claude to read this file:

read /tmp/total-recall to resume

Claude will then be up to speed on your previous work.

Frequently Asked Questions about total-recall

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I preserve Claude Code session context when hitting token limits?

Preserve Claude Code session context by running `/total-recall` before token limits or `/compact` operations. This creates a comprehensive memory dump at `/tmp/total-recall` containing your current work state, key decisions, generated files, and next steps, allowing you to resume exactly where you left off after context compaction or session reset.

Can I automatically save my Claude session state before context compaction?

Yes. Total Recall integrates via optional PreCompact hooks that automatically trigger memory dump preservation before context compaction occurs. This eliminates manual intervention and ensures your session state is captured without losing work during automatic memory management.

What information does a session memory dump contain?

A session memory dump captures current state, key decisions made, data and inventory summaries, generated files with their paths, next steps with completion statuses, and important technical notes. This comprehensive snapshot enables seamless resumption of complex multi-file projects without manual re-explanation.

How do I restore my Claude session after a reset or context switch?

Restore your session by instructing Claude to read the saved memory dump at `/tmp/total-recall`. Claude instantly recovers your previous work state, decisions, generated artifacts, and progress, eliminating the need to re-establish context manually when returning to a project.

Is session memory preservation needed for short tasks or only complex projects?

Session memory preservation is most valuable for long or complex tasks involving multiple generated files, critical design decisions, or infrastructure code. It prevents context loss during token limit approaches, `/reset` operations, or task switching, but isn't required for straightforward single-session work.