session-recovery

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

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/Quintenps/contactswap-agents --skill session-recovery-quintenps
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-recovery
Source: https://github.com/Quintenps/contactswap-agents/tree/main/.copilot/skills/session-recovery
Command: npx skills add https://github.com/Quintenps/contactswap-agents --skill session-recovery-quintenps

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves the frustration of losing progress due to terminal crashes, network drops, or accidental window closures by identifying and restoring interrupted Copilot CLI sessions.

Core Features & Use Cases

  • Session Discovery: Query the internal session_store database to locate recent work sessions based on time, directory, or keywords.
  • Context Restoration: Inspect conversation history, checkpoint progress, and touched files to understand exactly where work was left off.
  • Orphaned Task Detection: Identify issues marked as in-progress that lack an active session to ensure no work is left behind.

Quick Start

Use the session-recovery skill to list all sessions from the last 24 hours and identify the most recent one to resume.

Frequently Asked Questions about session-recovery

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I recover an interrupted Copilot CLI session after a terminal crash?

To recover an interrupted Copilot CLI session, query the local session_store SQLite database to identify recent work sessions and inspect conversation history to resume exactly where work was left off.

Can I find orphaned tasks or in-progress issues that lack an active session?

Yes, session recovery detects orphaned tasks by querying the session_store database for issues marked as in-progress that lack an active session, ensuring no development work is left behind.

How do I list recent SQLite session history to restore lost development work?

Query the session_store SQLite database to list sessions from the last 24 hours, filtering by time, directory, or keywords to locate and restore lost development work and touched files.

Does session recovery require write access to the SQLite database?

No, session recovery requires read-only access to the local session_store SQLite database and the ability to execute SQL queries for conversation history retrieval and context restoration.

What's the best way to restore workflow persistence after an accidental window closure?

The best way to restore workflow persistence is to query the session_store database to discover recent sessions, inspect checkpoint progress, and resume continuous task execution after accidental closures.

Why does session recovery fail to find my recent debugging session history?

Session recovery may fail if the local session_store SQLite database lacks read access or if SQL query execution is blocked, preventing retrieval of recent debugging session history and checkpoints.