session-recovery

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

9|1|Updated Jul 21, 2025

Search Tags:#sqlite #sql #checkpoint #copilot-cli #session-recovery #session_store #resume-sessions

Ready to run

npx skills add https://github.com/usepowershell/PoshMcp --skill session-recovery-usepowershell

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Recover in-progress Copilot CLI work that was interrupted by crashes, network drops, or accidental closures by locating past sessions and restoring their context so work can be resumed without loss.

Core Features & Use Cases

Session Discovery: Query the read-only session_store SQLite database to find recent sessions, filter by time window, working directory, branch, or keywords.
Noise Reduction: Exclude automated high-volume sessions (keep-alive/heartbeat) to surface human-initiated work.
Full Context Inspection: Retrieve last checkpoints, conversation turns, touched files, and linked refs (issues/PRs/commits) before resuming.
Resume Workflow: Use the session ID to resume agent work or hand off context to a human operator to finalize remaining steps.

Quick Start

Query the session_store for recent human sessions about authentication, inspect the last checkpoint and conversation turns, then resume the most relevant session by its session UUID.

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

You can find interrupted Copilot CLI sessions by querying the session_store SQLite database for recent activity and last checkpoints. The tool filters out automated keep-alive noise to surface human-initiated work by time window, working directory, or keywords.

How do I filter out automated keep-alive sessions to find my actual Copilot CLI work?▼

You can inspect last checkpoints, conversation turns, and touched files from the session_store SQLite database before resuming. This full context inspection retrieves linked refs like issues, PRs, and commits to verify the exact state of interrupted Copilot CLI work.

Can I search past Copilot CLI sessions by working directory or topic?▼

Resuming an interrupted Copilot CLI session requires read-only access to the session_store SQLite database, the ability to execute parameterized SQL queries across its tables, and the capability to invoke copilot --resume with the target session UUID.

What data do I need to access to recover lost Copilot CLI session context?▼

After resuming an interrupted Copilot CLI session, you can hand off the restored context to a human operator to finalize remaining steps, or continue the agent work directly using the retrieved session UUID and last checkpoints.