session-recovery

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

7|Updated Oct 24, 2020
One-click install
npx skills add https://github.com/snow-jallen/HomeSpeaker --skill session-recovery-snow-jallen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: session-recovery
Source: https://github.com/snow-jallen/HomeSpeaker/tree/main/.copilot/skills/session-recovery
Command: npx skills add https://github.com/snow-jallen/HomeSpeaker --skill session-recovery-snow-jallen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Intermittent Copilot CLI sessions can derail work; this skill enables quickly locating interrupted sessions and resuming from the last checkpoint using session_store queries.

Core Features & Use Cases

  • Discover interrupted Copilot CLI sessions by querying the session_store database.
  • Preview the last checkpoint, context, and touched files to determine the next steps.
  • Resume the session with copilot --resume SESSION_ID to continue work seamlessly.

Quick Start

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

To resume an interrupted Copilot CLI session, query the session_store SQLite database to locate the session ID, then execute copilot --resume SESSION_ID to restore the last checkpoint and context.

Can I recover Copilot CLI context after a terminal crash or network drop?▼

Yes, you can recover Copilot CLI context after a crash or network drop by querying the session_store database to find the interrupted session and previewing its last touched files before resuming.

How do I find interrupted Copilot sessions in the session_store database?▼

You find interrupted Copilot sessions by querying the session_store SQLite database using the sql tool with database "session_store" to retrieve session IDs, checkpoints, and context data.

Do I need SQLite access to recover a Copilot CLI session checkpoint?▼

Yes, you need SQLite access to query the session_store database via the sql tool with database "session_store", which is required to identify the interrupted session ID before using the copilot resume command.

What does Copilot CLI session recovery preview before resuming work?▼

Copilot CLI session recovery previews the last checkpoint, saved context, and touched files from the session_store database, allowing you to determine the next steps before executing the copilot resume command.