ingesting-agent-history

Generate timestamped agent ingest summaries when chat history is cleared.

Updated Mar 1, 2026
One-click install
npx skills add https://github.com/pelchers/SessionSaver --skill ingesting-agent-history
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ingesting-agent-history
Source: https://github.com/pelchers/SessionSaver/tree/main/.codex/skills/ingesting-agent-history
Command: npx skills add https://github.com/pelchers/SessionSaver --skill ingesting-agent-history

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates a structured, timestamped ingest summary whenever chat history is cleared or memory is compacted, ensuring context, app state, and next steps are preserved across sessions.

Core Features & Use Cases

  • Creates a timestamped ingest file in .adr/agent_ingest/ using the standard template.
  • Automatically captures branch, commit, ADR phase, app state, and last user interaction.
  • Supports end-of-session closures, memory resets, and handoffs to a new agent to maintain continuity.

Quick Start

Trigger the ingest process at session end to generate a timestamped entry using the agent-ingest template.

Frequently Asked Questions about ingesting-agent-history

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

FAQPage Schema
How do I preserve session context when chat history is cleared?

To preserve session context when chat history is cleared, generate a timestamped ingest summary that captures branch, commit, app state, and last interactions. This structured entry ensures context and next steps survive memory resets.

What is the best way to maintain agent continuity during memory compaction?

The best way to maintain agent continuity during memory compaction is to apply an ingest summary template at end-of-session closures. This records the ADR phase and app state, allowing seamless handoffs to a new agent.

How do I create a timestamped ingest file for agent handoffs?

Create a timestamped ingest file for agent handoffs by triggering the ingest process at session end. The system automatically fills the agent-ingest template with branch, commit, and last user interaction details.

When do I need to generate an ingest summary for my agent session?

You need to generate an ingest summary during end-of-session closures, memory resets, and agent handoffs. This prevents context loss when chat history is compacted or cleared between working sessions.

Can I capture app state and ADR phase details during a memory reset?

Yes, you can capture app state and ADR phase details during a memory reset. The ingest summary template automatically records these fields alongside branch and commit information to preserve working context.

Does ingesting agent history work without external dependencies?

Ingesting agent history works without external dependencies, relying solely on the standard agent-ingest template. It generates timestamped entries in the agent_ingest directory to structure your session context independently.