session-recovery

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps you locate and resume Copilot CLI sessions that were interrupted by crashes, network disconnects, or accidental window closures, ensuring work is not lost.

Core Features & Use Cases

  • Find Recent Sessions: Identify the most recently updated sessions from the session_store database.
  • Filter Out Automated Sessions: Exclude bot-like or heartbeat sessions to focus on human work.
  • Get Full Session Context: Retrieve checkpoints, branch, and working directory to determine where to resume.
  • Resume Workflows: Use the Copilot resume command with a session ID to continue where you left off.

Quick Start

Identify the most recently interrupted session and resume it with its SESSION_ID using Copilot.

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 after a crash?

To resume an interrupted Copilot CLI session, query the session_store SQLite database to find recent checkpoints, then run copilot --resume SESSION_ID to continue your workflow from where it left off.

How can I find recent Copilot sessions in the session_store database?

You can find recent Copilot sessions by querying the session_store SQLite database to identify the most recently updated records and retrieving their checkpoints, branch, and working directory context.

Does session recovery filter out automated Copilot sessions?

Yes, session recovery filters out automated or bot-like heartbeat sessions from the session_store database so you can focus exclusively on recovering human-driven work.

Can I inspect a Copilot session checkpoint before resuming it?

Yes, you can inspect Copilot session checkpoints by retrieving the branch and working directory details from the session_store database to determine if resuming that specific workflow is appropriate.

Do I need SQLite access to recover Copilot CLI sessions?

Yes, you need access to the session_store SQLite database via the sql tool to locate interrupted sessions, filter automated processes, and retrieve the session ID required for resuming.

What should I do if my Copilot session was lost after a network disconnect?

If a Copilot session was lost after a network disconnect, query the session_store SQLite database to locate the interrupted session, inspect its checkpoint, and resume it using the session ID.