session-recovery

Query the session_store database to detect and resume interrupted Copilot CLI sessions.

Updated May 10, 2026
One-click install
npx skills add https://github.com/AshleyHollis/agentic-identity-lab --skill session-recovery-ashleyhollis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-recovery
Source: https://github.com/AshleyHollis/agentic-identity-lab/tree/main/.copilot/skills/session-recovery
Command: npx skills add https://github.com/AshleyHollis/agentic-identity-lab --skill session-recovery-ashleyhollis

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses the issue of resuming interrupted Copilot CLI sessions due to terminal crashes, network issues, or accidental closures, enabling agents to pick up where they left off.

Core Features & Use Cases

  • Session History: Query the session_store database for past session history to detect interrupted sessions.
  • Session Management: Execute commands to find recent sessions, filter out automated sessions, search by topic, working directory, and more.
  • Context Retrieval: Retrieve full session context, including conversation turns, checkpoint progress, files touched, and linked PRs/issues/commits.
  • Session Detection: Identify sessions working on issues and ensure they are not orphaned.
  • Session Resumption: Resume a session using the session ID to continue work from where it was interrupted.

Quick Start

To resume a Copilot CLI session, run the command: 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?

You can resume an interrupted Copilot CLI session by querying the session_store database to find the session ID, then executing the command `copilot --resume SESSION_ID` to pick up where you left off.

What session context can I retrieve from the Copilot session_store database?

Querying the session_store database retrieves full session context, including past conversation turns, checkpoint progress, files touched, and linked PRs, issues, or commits associated with the interrupted Copilot CLI session.

How do I find specific Copilot CLI sessions by working directory or topic?

You can find specific Copilot CLI sessions by executing database queries against the session_store to filter session history by topic, working directory, or other criteria, while also filtering out automated sessions.

Do I need database access to recover Copilot CLI session history?

Yes, recovering Copilot CLI session history requires database access to the session_store for SQL querying, as the Skill relies on direct data retrieval to detect interrupted sessions and identify orphaned work.

How does session detection identify orphaned Copilot CLI sessions working on issues?

Session detection identifies Copilot CLI sessions working on issues by querying the session_store database, checking session history and context to ensure active work on issues is not left orphaned after interruptions.

What's the best way to manage Copilot CLI sessions after accidental terminal closures?

The best way to manage Copilot CLI sessions after accidental closures is to query the session_store database to detect interrupted sessions, retrieve their context, and resume them using their specific session ID.