session-recovery

Query the session_store database to resume interrupted Copilot CLI sessions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps agents recover from interrupted Copilot CLI sessions, ensuring that work is not lost and progress can be resumed efficiently.

Core Features & Use Cases

  • Session History Query: Retrieve and analyze past session history from the session_store database.
  • Automated Session Detection: Identify and filter out automated sessions to focus on human-initiated work.
  • Keyword Search: Find sessions using keyword search within the search_index FTS5 table.
  • Working Directory Filter: Narrow down sessions by working directory to locate specific projects.
  • Full Session Context: Inspect the full context of a session before resuming, including conversation turns, checkpoints, and files touched.
  • Orphaned Issue Work Detection: Identify sessions that were working on issues but may not have completed.
  • Session Resumption: Resume a session directly using the session ID.

Quick Start

Use the session-recovery skill to find and resume your last interrupted Copilot CLI session.

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?

To recover an interrupted Copilot CLI session, query the session_store database to retrieve history, find the specific session ID, and resume work directly using that ID. This restores your previous conversation context efficiently.

How does session recovery work with the session_store database?

Session recovery works by using SQL querying to search the session_store database. It filters out automated sessions and queries the search_index FTS5 table to find specific human-initiated sessions based on keywords and working directory.

Can I search past Copilot CLI sessions by working directory?

Yes, you can narrow down past Copilot CLI sessions by working directory to locate specific projects. This filter helps isolate the exact project context needed before resuming interrupted work.

Do I need SQL querying capabilities to find lost Copilot CLI session history?

Yes, understanding SQL querying and the session_store database schema is required. This knowledge allows you to effectively query the database, filter automated sessions, and inspect full session contexts like conversation turns and files touched.

How do I find orphaned issues from incomplete Copilot CLI sessions?

To find orphaned issues from incomplete Copilot CLI sessions, use session recovery to identify sessions that were working on issues but may not have completed. This detects unfinished work so you can resume the session directly.