session-recovery

Query the session_store SQLite database to resume interrupted Copilot CLI sessions.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/barichter/squad --skill session-recovery-barichter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-recovery
Source: https://github.com/barichter/squad/tree/main/.squad/skills/session-recovery
Command: npx skills add https://github.com/barichter/squad --skill session-recovery-barichter

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a mechanism for agents to recover from interrupted sessions by querying the session_store database and identifying where work was last left off.

Core Features & Use Cases

  • Session Detection: Identifies interrupted Copilot CLI sessions.
  • Checkpoint Resumption: Resumes work from the last known checkpoint.
  • Data Security: Ensures session history is only accessed for recovery purposes.

Quick Start

Use the session-recovery skill to find and resume the most recent interrupted session.

Frequently Asked Questions about session-recovery

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

FAQPage Schema
How do I resume an interrupted Copilot CLI session?

Resuming an interrupted Copilot CLI session involves querying the session_store SQLite database to identify the last known checkpoint. This allows agents to determine the prior work state and continue progress without losing work in progress.

What is the best way to recover work in progress from a crashed CLI session?

Recovering work in progress from a crashed CLI session is done by querying the session_store database to detect interrupted sessions. The mechanism identifies where work was last left off and resumes from that specific checkpoint.

How does session recovery find the last checkpoint in the session_store?

Session recovery finds the last checkpoint by querying the session_store SQLite database. It identifies interrupted Copilot CLI sessions and extracts the precise history needed to determine the exact state of work prior to the interruption.

Is my session history secure when using a session recovery mechanism?

Your session history is secure during session recovery because the mechanism ensures data is only accessed for recovery purposes. It queries the session_store database strictly to identify checkpoints and resume interrupted Copilot CLI work.

Do I need a specific database setup to restore interrupted Copilot CLI sessions?

Restoring interrupted Copilot CLI sessions requires the session_store SQLite database. The recovery mechanism queries this existing database to detect interrupted sessions and identify the last known checkpoint to resume work.