skills.rest
robpitcher
robpitcherCOMMUNITY
Explore all skills by this author →
GitHub

session-recovery

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

Updated Apr 14, 2026
Search Tags:#automation#checkpoints#sqlite#resume#copilot-cli#session-recovery#session_store
One-click install
npx skills add https://github.com/robpitcher/eShopOnWeb --skill session-recovery-robpitcher
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: session-recovery
Source: https://github.com/robpitcher/eShopOnWeb/tree/main/.copilot/skills/session-recovery
Command: npx skills add https://github.com/robpitcher/eShopOnWeb --skill session-recovery-robpitcher

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Copilot CLI sessions can be interrupted by crashes or disconnections; this skill helps you locate and resume those sessions by querying the session_store database for recent sessions and their last checkpoints.

Core Features & Use Cases

  • Find and list recent Copilot CLI sessions from the session_store with their latest checkpoint.
  • Filter out automated or non-user sessions to focus on actionable work and prepare context for resumption.
  • Retrieve full session context (turns, checkpoints, touched files) to support a seamless resume experience and reduce repetition.

Quick Start

Identify the target session ID from the recent sessions and run copilot --resume SESSION_ID to continue work.

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?▼

To resume an interrupted Copilot CLI session, query the session_store SQLite database to find the target session ID, then run `copilot --resume SESSION_ID` to continue work from the last checkpoint.

What is the best way to find recent Copilot CLI sessions after a crash?▼

Finding recent Copilot CLI sessions after a crash involves querying the session_store SQLite database with SQL to extract sessions, last_checkpoint data, and context, filtering out automated or non-user sessions.

Do I need SQLite read access to recover Copilot CLI checkpoints?▼

Yes, you need SQLite read access to recover Copilot CLI checkpoints because the skill queries the session_store database directly to extract sessions, last_checkpoint records, and context before resuming.

Can I filter out automated sessions when searching the Copilot session_store?▼

Yes, you can filter out automated or non-user sessions when searching the Copilot session_store to focus on actionable work and prepare context for a seamless resumption experience.

How does Copilot CLI session recovery handle context and touched files?▼

Copilot CLI session recovery handles context by retrieving full session context, including turns, checkpoints, and touched files, to support a seamless resume experience and reduce repetition.

Related Skills

Explore More Software Engineering Skills→
Leep-GHLeep-GH

session-recovery

Identify interrupted Copilot CLI sessions in the session_store SQLite database using SQL queries.

Community
Intermediate
lbouriezlbouriez

session-recovery

Query the session_store to identify interrupted Copilot CLI sessions and resume them.

Community
Intermediate
snow-jallensnow-jallen

session-recovery

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

Community
Advanced
fattits30-devfattits30-dev
1

database-backup-restore

Automate SQLite database backups and restore with checksum validation.

Community
Intermediate