session-recovery

Name: session-recovery
Availability: InStock
Author: sudhakrms

Query the session_store database to identify interrupted Copilot CLI sessions.

1|Updated Apr 17, 2026

Search Tags:#workflow #cli #sqlite #resume #copilot #recover #session_store

Ready to run

npx skills add https://github.com/sudhakrms/CalendarControl --skill session-recovery-sudhakrms

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: session-recovery
Source: https://github.com/sudhakrms/CalendarControl/tree/main/coffee/.copilot/skills/session-recovery
Command: npx skills add https://github.com/sudhakrms/CalendarControl --skill session-recovery-sudhakrms

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps Copilot CLI users recover interrupted sessions by querying the session_store to identify and resume work after crashes or disconnects.

Core Features & Use Cases

Find recent interrupted sessions by querying the sessions table and retrieving the last checkpoint to determine where the session stopped.
Filter out automated or heartbeat-driven sessions to surface human work and prevent noise.
Resume a selected session with copilot --resume SESSION_ID and inspect context to ensure continuity.

Quick Start

Identify the target session from the results 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 database to find the session ID, then run copilot --resume SESSION_ID to continue work from the last checkpoint.

Can I recover a Copilot CLI session if the terminal window was closed unexpectedly?▼

Yes, you can recover a Copilot CLI session after an unexpected window closure by querying the session_store database to locate the disrupted session and executing the resume command with the identified session ID.

How do I filter out automated Copilot sessions to find my actual work?▼

Filtering automated sessions requires querying the sessions table in the session_store database to exclude heartbeat-driven or automated sessions, surfacing only human work for accurate session recovery.

Do I need access to the SQLite database to find previous Copilot checkpoints?▼

Yes, accessing the SQLite session_store database is required to query the sessions table, retrieve the last checkpoint, and identify the correct resumption path for interrupted Copilot CLI sessions.

What is the best way to locate the session ID for a disconnected Copilot CLI workflow?▼

The best way to locate a disconnected Copilot CLI workflow session ID is to query the session_store database using SQL to filter automated sessions and retrieve the last checkpoint data.

How does querying the session_store database help with CLI session recovery?▼

Querying the session_store database helps with CLI session recovery by using SQL queries to locate last checkpoints, filter out automated noise, and provide an exact resumption path for disrupted work.