session-recovery

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

Updated Nov 11, 2025
One-click install
npx skills add https://github.com/acmeleme/Conversation-Knowledge-Mining-Solution-Accelerator --skill session-recovery-acmeleme
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-recovery
Source: https://github.com/acmeleme/Conversation-Knowledge-Mining-Solution-Accelerator/tree/main/.copilot/skills/session-recovery
Command: npx skills add https://github.com/acmeleme/Conversation-Knowledge-Mining-Solution-Accelerator --skill session-recovery-acmeleme

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Find and resume interrupted Copilot CLI sessions by querying the session_store SQLite database, enabling quick recovery of in-progress work after crashes or disconnects.

Core Features & Use Cases

  • Query recent sessions and pull the last checkpoint to determine where the session stopped.
  • Filter out automated or heartbeat sessions to focus on human-initiated work.
  • Inspect full session context (turns, checkpoints, touched files, and linked references) to enable precise resumption.

Quick Start

Identify the target session in session_store and run copilot --resume SESSION_ID to continue.

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 the target session ID, then run the copilot --resume SESSION_ID command to continue your work.

Can I retrieve the last checkpoint from a disconnected Copilot CLI task?

Yes, you can retrieve the last checkpoint from a disconnected Copilot CLI task by inspecting the session context, including turns, touched files, and linked references stored in the session_store SQLite database.

How do I filter automated heartbeat sessions from human-initiated Copilot CLI work?

You can filter automated or heartbeat sessions from human-initiated Copilot CLI work by applying filters during the session_store SQLite database query to focus on actual interactive sessions.

Does session recovery work with the session_store SQLite database for window-close events?

Yes, session recovery works with the session_store SQLite database for window-close events, enabling you to find the interrupted session, fetch its last checkpoint, and resume via the copilot --resume command.

What is the best way to recover in-progress work after a Copilot CLI disconnect?

The best way to recover in-progress work after a Copilot CLI disconnect is to query the session_store SQLite database to identify the stopped session, inspect its full context, and resume it directly.