session-recovery

Name: session-recovery
Availability: InStock
Author: waynewalterberry

Query the session_store to locate interrupted Copilot CLI sessions and retrieve latest checkpoints.

Updated Mar 19, 2026

Search Tags:#cli #sql #resume #recovery #session #copilot #session_store

Ready to run

npx skills add https://github.com/WayneWalterBerry/MMO --skill session-recovery-waynewalterberry

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: session-recovery
Source: https://github.com/WayneWalterBerry/MMO/tree/main/.copilot/skills/session-recovery
Command: npx skills add https://github.com/WayneWalterBerry/MMO --skill session-recovery-waynewalterberry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps you locate and resume Copilot CLI sessions that were interrupted by crashes, network drops, or accidental window closures, restoring work without starting over.

Core Features & Use Cases

Query the session_store to locate recent sessions and retrieve the latest checkpoint
Filter out automated monitors to focus on human work
Provide a safe resume command to continue work from the last checkpoint in the correct context

Quick Start

Resume the most recent interrupted Copilot CLI session by supplying its session_id to the resume command.

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 crash?▼

To resume an interrupted Copilot CLI session, query the read-only session_store database to locate the session_id, then pass it to the resume workflow using the copilot --resume command. This restores your work from the latest checkpoint.

Can I recover Copilot CLI work lost from a network drop or accidental window closure?▼

Yes, you can recover work lost from a network drop or window closure by recovering the session context. The skill queries the session_store for the latest checkpoint and safely resumes your in-progress work without needing to start over.

How do I find the session_id for a recent Copilot CLI session?▼

You find the session_id by querying the session_store database for recent activity. The query filters out automated monitors to focus on human work, allowing you to identify the correct session_id needed to trigger the resume command.

Does session recovery require write access to the Copilot session_store database?▼

No, session recovery requires only read-only access to the session_store database. It safely locates the latest checkpoints and restores the session context using the copilot --resume workflow without modifying the underlying database.

What's the best way to filter out automated monitors when locating Copilot sessions?▼

The best way to filter out automated monitors is to query the session_store specifically for recent human work activity. This ensures the recovery process focuses only on locating the latest checkpoint for sessions disrupted by crashes or closures.

Can I restore Copilot CLI session context without starting over?▼

Yes, you can restore Copilot CLI session context without starting over by supplying the recovered session_id to the resume workflow. This safely applies the latest checkpoint and revives the in-progress work in the correct context.