session-recovery

Query the session_store database to identify interrupted Copilot CLI sessions.

Updated Mar 18, 2022
One-click install
npx skills add https://github.com/mpaulosky/dotfiles --skill session-recovery-mpaulosky
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-recovery
Source: https://github.com/mpaulosky/dotfiles/tree/main/.copilot/skills/session-recovery
Command: npx skills add https://github.com/mpaulosky/dotfiles --skill session-recovery-mpaulosky

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Copilot CLI sessions can be interrupted by crashes, network issues, or accidental window closures, leaving work unfinished. This skill helps identify those sessions and resume work by querying the session_store.

Core Features & Use Cases

  • Identify interrupted Copilot CLI sessions by querying the session_store database for recent activity.
  • Filter automated sessions and find the most relevant session by working directory, last checkpoint, or summary.
  • Retrieve full session context before resuming, including turns, checkpoints, and touched files, to ensure a seamless continuation.

Quick Start

Resume a chosen interrupted session by running copilot --resume SESSION_ID after identifying it in the session_store.

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 session from the session_store?

To resume an interrupted Copilot session, query the session_store database to locate the session by working directory or last checkpoint, then run copilot --resume SESSION_ID to continue.

What data does Copilot session recovery need from the session_store database?

Copilot session recovery queries the session_store database for sessions, turns, and checkpoints to identify interrupted sessions. It requires the sql tool configured with database session_store to access recent activity.

Does Copilot session recovery work with automated sessions?

Copilot session recovery filters out automated sessions and focuses on interactive sessions interrupted by crashes, network issues, or accidental closures, identifying the most relevant session by working directory or last checkpoint.

What context is retrieved before resuming an interrupted Copilot session?

Before resuming an interrupted Copilot session, the recovery process retrieves full session context including turns, checkpoints, and touched files from the session_store database to ensure a seamless continuation.

Why does Copilot session recovery require the sql tool?

Copilot session recovery requires the sql tool configured with database session_store to query sessions, turns, and checkpoints directly from the database, enabling it to identify interrupted activity and locate the most relevant session.