session-recovery

Query the local SQLite session_store database to recover interrupted Copilot CLI sessions.

1|Updated Dec 23, 2025

Search Tags:#workflow #cli #sqlite #persistence #recovery #session

Ready to run

npx skills add https://github.com/jonnymuir/Umbraco.Prism --skill session-recovery-jonnymuir

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves the frustration of losing progress during terminal crashes, network drops, or accidental window closures by allowing you to identify and resume partially completed work sessions.

Core Features & Use Cases

Session Discovery: Query the local session_store database to find recent work history based on time, directory, or keywords.
Context Restoration: Inspect past conversation turns, checkpoints, and modified files to understand exactly where a session was interrupted.
Use Case: If your terminal crashes while you are in the middle of a complex refactoring task, use this skill to find the specific session ID and resume your work exactly where you left off.

Quick Start

Use the session-recovery skill to list all active sessions from the last 24 hours and identify the one you need to resume.

Frequently Asked Questions about session-recovery

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I recover an interrupted Copilot CLI session after a terminal crash?▼

To recover an interrupted Copilot CLI session, query the local SQLite session_store database to identify recent work history, retrieve session metadata, and restore the exact file context where the crash occurred.

Can I find past Copilot CLI work history based on the directory I was working in?▼

Yes, you can discover past Copilot CLI work history by querying the SQLite session_store database to filter recent sessions based on time, directory, or keywords to pinpoint the exact session ID needed.

What information is available when restoring a partially completed Copilot CLI session?▼

Restoring a partially completed Copilot CLI session provides access to past conversation turns, checkpoint progress, and modified file context, allowing developers to understand exactly where the work was interrupted.

How do I list active Copilot CLI sessions from the last 24 hours to resume work?▼

You can list active Copilot CLI sessions from the last 24 hours by querying the local SQLite session_store database to retrieve session history and state analysis for the specific timeframe.

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

No, session recovery requires read-only access to the SQLite session_store database to execute SQL queries for retrieving session metadata, checkpoint progress, and file context without modifying the underlying data.

Why does my Copilot CLI session disappear when the network drops unexpectedly?▼

When a network drop or accidental window closure interrupts your session, the session state remains stored in the local SQLite session_store database, allowing you to identify the specific session ID and resume your work exactly where you left off.