session-recovery

Recover interrupted Copilot CLI sessions by querying the session_store SQLite database.

2|Updated Apr 21, 2026
One-click install
npx skills add https://github.com/elbruno/md-to-slides --skill session-recovery-elbruno
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-recovery
Source: https://github.com/elbruno/md-to-slides/tree/main/.copilot/skills/session-recovery
Command: npx skills add https://github.com/elbruno/md-to-slides --skill session-recovery-elbruno

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of losing progress when Copilot CLI sessions are interrupted, leaving work partially completed with unclear last known state.

Core Features & Use Cases

  • Session History Recovery via SQLite: Locates recent interrupted sessions by querying the session_store database for session metadata and checkpoints.
  • Noise Reduction with Automated-Session Filtering: Excludes high-volume automated sessions (keep-alive/heartbeat) so you can focus on human-initiated work.
  • Targeted Resumption with Context Inspection: Retrieves turns, checkpoints, touched files, and linked issues/PRs to safely decide whether to resume and what to do next.

Quick Start

Ask the AI to recover a specific interrupted Copilot CLI session by querying session_store, identifying the relevant latest checkpoint, and then resuming that session by ID.

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 read-only `session_store` SQLite database to locate the unfinished session and its last checkpoint, then execute `copilot --resume` using the full session UUID.

How does Copilot CLI session recovery work with SQLite?

Copilot CLI session recovery works by querying the `session_store` SQLite database, which stores session metadata, checkpoints, turns, and touched files in tables like `session_files` and `search_index` FTS5, to determine where progress stopped.

Can I filter out automated Copilot CLI sessions when searching for my work?

Yes, you can filter out automated Copilot CLI sessions. The recovery process excludes high-volume automated sessions, such as keep-alive or heartbeat tasks, ensuring you only focus on human-initiated work for resumption.

What is the best way to find the last checkpoint of a workflow recovery session?

The best way to find the last checkpoint during workflow recovery is by running SQL queries against the `session_store` database to retrieve session metadata, turns, and linked issues or PRs before safely deciding to resume.

Does Copilot CLI session recovery inspect what files were touched before resuming?

Yes, Copilot CLI session recovery inspects what files were touched. It retrieves turns, checkpoints, touched files, and linked issues from the SQLite database so you can safely decide whether to resume and what to do next.

Can I use SQL queries to recover a Copilot CLI session after a terminal closure?

Yes, you can use SQL queries to recover a Copilot CLI session after terminal or window closures. Query the `session_store` SQLite database to find the interrupted session UUID and apply `copilot --resume`.