skills.rest
sytone
sytoneCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

session-recovery

Query the session_store database to recover interrupted Copilot CLI sessions.

2|3|Updated Apr 1, 2026
Search Tags:#cli#sql#resume#recovery#session#copilot#session_store
One-click install
npx skills add https://github.com/sytone/botnexus --skill session-recovery-sytone
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: session-recovery
Source: https://github.com/sytone/botnexus/tree/main/.copilot/skills/session-recovery
Command: npx skills add https://github.com/sytone/botnexus --skill session-recovery-sytone

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Copilot CLI sessions can be interrupted by crashes, network drops, or terminal closures, leaving work in progress stranded. This Skill provides a structured approach to find and resume those sessions from the session_store.

Core Features & Use Cases

  • SQL-based discovery: Locate recently active sessions and their last checkpoints using the session_store database.
  • Context extraction: Retrieve the latest checkpoint, current working directory, and session metadata to inform resumption.
  • Resume workflow: Reattach and continue work quickly with the copilot --resume command using the session ID.

Quick Start

Identify interrupted Copilot CLI sessions, select the target SESSION_ID, and resume with 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?▼

To resume an interrupted Copilot CLI session, query the session_store database to identify the active session and extract its ID, then execute the copilot --resume command with that SESSION_ID to restore your previous context and checkpoint.

What is the best way to find a lost Copilot CLI session after a crash?▼

The best way to find a lost Copilot CLI session is to perform SQL-based discovery directly on the session_store database to locate recently active sessions and extract their latest checkpoints across different branches and projects.

How does Copilot CLI session recovery work?▼

Copilot CLI session recovery works by querying the session_store database to filter out automated activity, extract the last checkpoint and working directory metadata, and pass the target session ID to the copilot --resume command.

Can I recover Copilot CLI session progress across different git branches?▼

Yes, you can recover Copilot CLI session progress across different git branches. The recovery process queries recent sessions across multiple projects and branches to locate your stranded working context before resuming.

How do I exclude automated activity when searching for a Copilot CLI session?▼

To exclude automated activity when searching for a Copilot CLI session, the recovery workflow applies specific filters during the SQL-based discovery process on the session_store database to isolate genuine interactive sessions.

Related Skills

Explore More Software Engineering Skills→
fattits30-devfattits30-dev
1

database-backup-restore

Automate SQLite database backups and restore with checksum validation.

Community
Intermediate
lbouriezlbouriez

session-recovery

Query the session_store to identify interrupted Copilot CLI sessions and resume them.

Community
Intermediate
CommunityToolkitCommunityToolkit
619

session-recovery

Resumes interrupted Copilot CLI sessions by querying the session store.

Official
Intermediate
webmaxruwebmaxru
49

session-recovery

Resume interrupted Copilot CLI sessions from the session_store SQLite database.

Community
Intermediate