session-tracker

Track cross-session context and persist memory across Claude Code conversations.

4|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/Kit4Some/Oh-my-ClaudeClaw --skill session-tracker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-tracker
Source: https://github.com/Kit4Some/Oh-my-ClaudeClaw/tree/main/skills/session-tracker
Command: npx skills add https://github.com/Kit4Some/Oh-my-ClaudeClaw --skill session-tracker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Session continuity across Claude Code conversations and multi-session projects by bridging OMC state and persistent memory.

Core Features & Use Cases

  • Cross-session context loading and continuation
  • Automated memory persistence and checkpointing
  • Proactive session status checks and logging

Quick Start

Start the session-tracker to load previous context, initialize the current session, and auto-save progress across memory layers.

Frequently Asked Questions about session-tracker

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

FAQPage Schema
How do I maintain cross-session context in Claude Code conversations?

Cross-session context is maintained by loading previous progress, initializing the current session, and auto-saving updates across a three-layer memory system with proactive state checks.

What's the best way to automate memory persistence across multiple coding sessions?

Automated memory persistence is handled through auto-save hooks triggered by the session-manager agent, which checkpoints progress across memory layers without requiring manual intervention.

When do I need session continuity tracking for multi-session projects?

Session continuity tracking is needed for multi-session workflows where users require memory recall, progress tracking, and seamless continuation across separate Claude Code conversations.

Does session-tracker require any external dependencies or components to function?

No external dependencies or components are required. The session-tracker operates independently using its internal three-layer memory system and session-manager agent for state checks.

How does the three-layer memory system work for logging conversation continuity?

The three-layer memory system bridges OMC state and persistent memory by applying proactive session status checks and automated checkpointing to log continuity across conversations.

Can I use automated checkpointing to recover lost progress from previous sessions?

Automated checkpointing persists session state across memory layers, allowing you to load previous context and resume multi-session workflows from the last saved progress point.