session-recovery

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

Updated Mar 27, 2026

Search Tags:#sql #resume #checkpoint #copilot-cli #session-store #session-recovery

Ready to run

npx skills add https://github.com/lbouriez/Squad-Templates --skill session-recovery-lbouriez

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: session-recovery
Source: https://github.com/lbouriez/Squad-Templates/tree/main/Nectari-Devops-Squad/.copilot/skills/session-recovery
Command: npx skills add https://github.com/lbouriez/Squad-Templates --skill session-recovery-lbouriez

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Copilot CLI sessions can be interrupted by terminal crashes or network drops, leading to incomplete work.

Core Features & Use Cases

Finds recently interrupted Copilot CLI sessions by querying the session_store database.
Resumes progress from the last checkpoint using copilot --resume with the correct SESSION_ID.
Supports filtering out automated sessions to focus on human-initiated work.

Quick Start

Use the Copilot CLI to resume a specific session by first locating the interrupted session in the session_store and then running copilot --resume SESSION_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 terminal crash?▼

To resume an interrupted Copilot CLI session, query the session_store database to find the last checkpoint, identify the correct SESSION_ID, and run the command copilot --resume SESSION_ID to restore context and in-progress tasks.

What is a Copilot CLI session checkpoint and how does it work?▼

A Copilot CLI session checkpoint is a saved progress state within the session_store database that captures context and in-progress tasks, allowing the copilot --resume command to restore work exactly where it was interrupted.

How do I find the correct SESSION_ID for a dropped Copilot session?▼

You can find the correct SESSION_ID by querying the session_store database to identify recently interrupted Copilot CLI sessions and retrieving the ID associated with the last checkpoint.

Can I filter out automated Copilot CLI sessions and only recover human-initiated work?▼

Yes, you can filter out automated sessions when querying the session_store database to focus on human-initiated Copilot CLI work, ensuring you only resume relevant interrupted tasks using the copilot --resume command.

What's the best way to restore context on a target session after a network drop?▼

The best way to restore context is to query the session_store for the last checkpoint, determine the correct SESSION_ID, and use copilot --resume SESSION_ID to fully restore the interrupted Copilot CLI session context.