skills.rest
DeDuva
DeDuvaCOMMUNITY
Explore all skills by this author →
GitHub

session-recovery

Query the session_store to locate and resume interrupted Copilot CLI sessions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Finds and resumes interrupted Copilot CLI sessions by querying the session_store for past work and restoring progress from the last checkpoint.

Core Features & Use Cases

  • Session discovery: locate interrupted sessions using the session_store.
  • Progress restoration: resume from the most recent checkpoint and continue work without losing context.
  • Safety and filtering: exclude automated sessions (e.g., monitors/heartbeats) to focus on human-initiated work.

Quick Start

Query the session_store for interrupted Copilot CLI sessions and resume the most recent one from its last checkpoint.

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 locate past work and restoring progress from the last checkpoint using the copilot --resume command.

Can I recover Copilot CLI workflow context if my terminal window closes accidentally?▼

Yes, recovering Copilot CLI workflow context after an accidental window close is possible by querying the session_store to find the lost session and restoring its previous checkpoint.

How do I find human-initiated Copilot CLI sessions and exclude automated monitor sessions?▼

Finding human-initiated Copilot CLI sessions involves applying safety filters during your session_store queries to exclude automated monitors or heartbeats, ensuring you only resume actual work.

Does session recovery work by querying SQLite to locate past Copilot CLI checkpoints?▼

Yes, session recovery works by executing SQL queries directly against the SQLite session_store to locate interrupted Copilot CLI sessions and restore progress from the last checkpoint.

What is the best way to restore Copilot CLI progress after a network drop?▼

The best way to restore Copilot CLI progress after a network drop is to query the session_store for the interrupted session and resume from its last saved checkpoint.

When should I not use session_store queries to recover Copilot CLI sessions?▼

You should not use session_store queries to recover Copilot CLI sessions if the work was automated by a monitor or heartbeat, as the safety filtering specifically excludes these non-human sessions.

Related Skills

Explore More Software Engineering Skills→
snow-jallensnow-jallen

session-recovery

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

Community
Advanced
MINT-IAMINT-IA

gsd-resume-work

Restore project session context from STATE.md and checkpoint files.

Official
Advanced
Golnaz89Golnaz89

session-recovery

Query the session_store database to identify interrupted Copilot CLI sessions.

Community
Intermediate
webmaxruwebmaxru
49

session-recovery

Resume interrupted Copilot CLI sessions from the session_store SQLite database.

Community
Intermediate