skills.rest
Leep-GH
Leep-GHCOMMUNITY
Explore all skills by this author →
GitHub

session-recovery

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

Updated Apr 16, 2026
Search Tags:#sqlite#resume#recovery#session-history#copilot-cli#session_store
One-click install
npx skills add https://github.com/Leep-GH/Lee-s-squad --skill session-recovery-leep-gh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: session-recovery
Source: https://github.com/Leep-GH/Lee-s-squad/tree/main/.squad/skills/session-recovery
Command: npx skills add https://github.com/Leep-GH/Lee-s-squad --skill session-recovery-leep-gh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Copilot CLI sessions can be interrupted by terminal crashes, network drops, or accidental window closes, leaving work in progress and checkpoints unfinished.

Core Features & Use Cases

  • Query the session_store to locate recently interrupted sessions and identify the last checkpoint for resumption.
  • Filter out automated or heartbeat sessions to avoid resuming non-user tasks.
  • Resume a chosen session with a single action while preserving the working directory, branch, and checkpoint state.

Quick Start

Resume an interrupted Copilot CLI session by supplying the session UUID.

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

Locate interrupted Copilot CLI sessions by querying the session_store SQLite database to find the last checkpoint. You can resume the chosen session using its UUID, which restores the working directory, branch, and checkpoint state after a terminal crash or network drop.

How does Copilot CLI session recovery work with SQLite?▼

Session recovery uses a read-only connection to the session_store SQLite database to locate interrupted Copilot CLI sessions. It queries the last checkpoint to resume in-progress work while filtering out automated or heartbeat sessions to avoid resuming non-user tasks.

Can I recover Copilot CLI session history after an accidental window close?▼

Yes, you can recover session history after an accidental window close by querying the session_store SQLite database. The recovery process locates the last checkpoint of the interrupted Copilot CLI session and restores the exact working directory and branch state.

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

You need a read-only connection to the session_store SQLite database to restore Copilot CLI sessions. No additional dependencies are required, as the recovery process uses standard SQL queries to locate the last checkpoint and resume the workflow.

What is the best way to filter out automated tasks when resuming Copilot CLI sessions?▼

The best way to filter out automated tasks during Copilot CLI session recovery is to query the session_store while excluding automated or heartbeat sessions. This ensures you only locate and resume actual user tasks interrupted by crashes or network drops.

Related Skills

Explore More Software Engineering Skills→
elbrunoelbruno
2

session-recovery

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

Community
Intermediate
lbouriezlbouriez

session-recovery

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

Community
Intermediate
Golnaz89Golnaz89

session-recovery

Query the session_store database to identify interrupted Copilot CLI sessions.

Community
Intermediate
fattits30-devfattits30-dev
1

database-backup-restore

Automate SQLite database backups and restore with checksum validation.

Community
Intermediate