skills.rest
olivomarco
olivomarcoCOMMUNITY
Explore all skills by this author →
Website𝕏@olivomarcoGitHub

session-recovery

Query the session_store database to identify interrupted Copilot CLI sessions for resumption.

66|41|Updated Mar 4, 2026
Search Tags:#cli#sql#resume#copilot#session-recovery#session_store
One-click install
npx skills add https://github.com/olivomarco/vbd-copilot --skill session-recovery-olivomarco
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: session-recovery
Source: https://github.com/olivomarco/vbd-copilot/tree/main/.copilot/skills/session-recovery
Command: npx skills add https://github.com/olivomarco/vbd-copilot --skill session-recovery-olivomarco

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sessions in Copilot CLI can be interrupted by terminal crashes, network drops, or accidental closes, leaving work unfinished. This skill helps locate and resume those interrupted sessions by querying the session_store database and presenting a resume path.

Core Features & Use Cases

  • Find recent or in-progress sessions by inspecting the session_store and identifying the latest checkpoint.
  • Filter out automated or idle sessions to surface human-initiated work.
  • Resume a selected session with the Copilot CLI while restoring checkpoints and context for seamless continuation.

Quick Start

Identify the interrupted session and instruct Copilot to resume it using the 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?▼

To resume an interrupted Copilot CLI session, query the session_store database to identify the latest checkpoint and instruct Copilot to resume using the recovered session ID. This restores your previous context and in-progress work seamlessly.

What's the best way to find unfinished work from a dropped Copilot CLI session?▼

Finding unfinished work from a dropped Copilot CLI session involves inspecting the session_store database to surface human-initiated sessions. The recovery process filters out automated or idle sessions to locate the latest valid checkpoint for continuation.

Does Copilot CLI session recovery require SQL access to the session_store?▼

Yes, Copilot CLI session recovery requires SQL access to the session_store database to locate and extract interrupted session data. This access enables the tool to identify checkpoints and filter out automated background processes.

How do I restore Copilot CLI checkpoints and context after a network drop?▼

Restoring Copilot CLI checkpoints after a network drop requires identifying the interrupted session in the session_store. Once located, instruct Copilot to resume the session ID to preserve your existing context and continue development seamlessly.

Can I filter out automated background sessions when recovering Copilot CLI work?▼

Yes, you can filter out automated or idle sessions when recovering Copilot CLI work. The session_store inspection process specifically surfaces human-initiated sessions, ensuring you only see relevant interrupted development workflows.

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
quaid-appquaid-app
3

session-recovery

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

Official
Intermediate
snow-jallensnow-jallen

session-recovery

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

Community
Advanced