skills.rest
quaid-app
quaid-appOFFICIAL
Explore all skills by this author →
WebsiteGitHub

session-recovery

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Copilot CLI sessions can be interrupted by crashes, network issues, or accidental window closures, leaving work partially complete. This skill provides targeted queries against the session_store to detect interrupted sessions and resume work seamlessly.

Core Features & Use Cases

  • Detect recently interrupted Copilot CLI sessions by querying the session_store database.
  • Retrieve last checkpoint, working directory, and session summary to resume exactly where you left off.
  • Filter out automated or heartbeat sessions to focus on human-driven work.
  • Use within automated agents to quickly rehydrate a user context after a disconnect.

Quick Start

Run the recovery to locate and resume the most recent interrupted Copilot CLI session.

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 recover a dropped Copilot CLI session by querying the session_store database to retrieve the session ID, last checkpoint, and working directory. This rehydrates your context and filters out automated heartbeat sessions to focus on human-driven work.

What information do I need to restore a Copilot session from the session_store?▼

Restoring a Copilot session requires querying the session_store database to surface the session ID, last checkpoint, and current working directory (cwd). These three data points allow you to rehydrate the exact context of the interrupted work.

Can I filter out automated heartbeat sessions when recovering Copilot CLI history?▼

Yes, when querying the session_store database to detect interrupted Copilot CLI sessions, you can filter out automated or heartbeat sessions to ensure the recovery process focuses only on retrieving human-driven work.

Does the session recovery process require SQLite to query the session_store?▼

Yes, locating and resuming interrupted Copilot CLI sessions relies on an SQL tool to query the session_store SQLite database, extracting the session ID, last checkpoint, and working directory needed to rehydrate the context.

When should I use automated session recovery for Copilot CLI?▼

Use session recovery when terminal crashes, network drops, or accidental window closures leave Copilot CLI sessions in progress. It can also be used within automated agents to quickly rehydrate user context after a sudden disconnect.

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
jperezdelrealjperezdelreal

session-recovery

Find and resume interrupted Copilot CLI sessions from the session_store SQLite database.

Community
Intermediate
dotnetdotnet
209

session-recovery

Recover interrupted Copilot CLI sessions from the session_store SQLite database.

Official
Intermediate
QuintenpsQuintenps

session-recovery

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

Community
Intermediate